I was just asked how you would split your Rails routes file into multiple files for instance in the case of having an application frontend and a set of routes serving your application's API.
Now, I have a number of applications which work this way and utilize routing constraints to determine which routes should be used but splitting them into more manageable individual files is a nice idea so, my first thought...
We're currently utilising rsync to take daily snapshots of our servers and backup to remote locations, lately this has been trigger high load notifications quite frequently. In order to reduce the load caused by these scripts I have gone with three small changes...
I see a lot of posts recently about how pathetic GoDaddy are, and why you should leave them. There was their fickle SOAP support, their general marketing attitude - you know, how they try and sell you 50 other products between you selecting a domain and paying for it, even their support emails have marketing in them... you're trying to get some help and they're just trying to sell you more stuff. They are without a doubt a marketing monster, and to them this is far more important than customer support.
If you find you're having a hard time keeping a connection, your SSH sessions are locking up or disconnecting after short periods of inactivity and it's driving you slightly insane you can set the SSH keep-alive interval in your .ssh/config:
Open or create your ssh/config file in your editor of choice e.g.
And add the following line to your file:
This indicates the number of seconds after which a message will be sent to the server to keep the connection alive, only if no data is received from the server in that period. The default value for this is 0 (never). Check the man page for more information.