3 ms·

I do agree. I migrated my personal server after the RAM increase at Linode and all of my company's servers as well. I can't think of any other new features Sli

I do agree. I migrated my personal server after the RAM increase at Linode and all of my company's servers as well. I can't think of any other new features SliceHost has rolled out in the last 6 months.

StavrosK 16y ago
Hmm, how did you migrate? I have so many sites and old cruft that anything short of a clone of the VM will fail horribly...
- tasaro 16y ago
  This is a good starting point: http://bit.ly/WdezH http://bit.ly/WdezH
  - StavrosK 16y ago
    Thanks, I read that but it sounds like a hassle, I guess I'll have to bite the bullet. Thanks!
- askedrelic 16y ago
  Short answer: Build scripts + standard layout. (I'm a Debian guy) I used 'dpkg -l' to check what all I had currently installed and narrowed down what packages I was still using. Check /etc/init.d for start up scripts. Hard files on disk are easy to migrate, live migrating MySQL data is more tricky, but my personal sites don't really have that much going on. I always keep a .tar.gz of the entire server for future reference. Move over as much as possible and try to get things running. Save your .bash_history and get a build script going. Pull any /etc/ config files you are missing. Reinstall your required packages. Test your new site via editing /etc/hosts, then move the DNS. Watch your logs and look for 404 erors for files you didn't copy over correctly. It takes time, but if you use an organized and repeatable process, it can take less time in the future.
  - akira410 16y ago
    Same here. I also hacked up (with Linode) a Linode Stack Script (for those that do not know, it's basically a fancy bash script that gets run upon deployment.) It goes through the trouble of installing all of my various dpkg dependencies, setting up mysql, downloading and compiling rails and nginx w/ passenger, as well as setting up my bash prompt.

3 ms·

I do agree. I migrated my personal server after the RAM increase at Linode and all of my company's servers as well. I can't think of any other new features Sli

by askedrelic 16y ago

StavrosK 16y ago
Hmm, how did you migrate? I have so many sites and old cruft that anything short of a clone of the VM will fail horribly...
- tasaro 16y ago
  This is a good starting point: http://bit.ly/WdezH http://bit.ly/WdezH
  - StavrosK 16y ago
    Thanks, I read that but it sounds like a hassle, I guess I'll have to bite the bullet. Thanks!
- askedrelic 16y ago
  Short answer: Build scripts + standard layout. (I'm a Debian guy) I used 'dpkg -l' to check what all I had currently installed and narrowed down what packages I was still using. Check /etc/init.d for start up scripts. Hard files on disk are easy to migrate, live migrating MySQL data is more tricky, but my personal sites don't really have that much going on. I always keep a .tar.gz of the entire server for future reference. Move over as much as possible and try to get things running. Save your .bash_history and get a build script going. Pull any /etc/ config files you are missing. Reinstall your required packages. Test your new site via editing /etc/hosts, then move the DNS. Watch your logs and look for 404 erors for files you didn't copy over correctly. It takes time, but if you use an organized and repeatable process, it can take less time in the future.
  - akira410 16y ago
    Same here. I also hacked up (with Linode) a Linode Stack Script (for those that do not know, it's basically a fancy bash script that gets run upon deployment.) It goes through the trouble of installing all of my various dpkg dependencies, setting up mysql, downloading and compiling rails and nginx w/ passenger, as well as setting up my bash prompt.