Re: [Radiant] How can I have a foolproof backup?
On Wed, Jun 29, 2011 at 5:56 PM, Paul Noden wrote: > Would it be beneficial to have a dreamhost-radiant best practices > discussion? Do you use virtual or private servers? What are your findings in > terms of resourcing/load etc. > I ended up going with a VPS at 380Mb of memory for $19/month. I use 2-300 normal, and 3-400 when updating/creating pages. I was just getting too many failed to start phusion pages. I do still on occasion get a blank page when updating or creating pages. Very rarely I still get a 500 server error. So far it's just me as admin, about 150 pages on the site, only 10-30 unique visitors / day. I do have several extension: copy move and reorder, paperclipped, ray, tags, settings, sns, dashboard, and 2 quote-du-jours per page. > Looking forward to hearing your experiences, perhaps one day radiant could > become a dreamhost one-click or scripted install (I've found that memory > usage currently runs a little high for the limitations on a standard plan), > but there is a healthy niche for it since developer/design teams quite like > dreamhost... > > Paul > When I asked about getting it as a one-click, they said to put in a request where people vote on it. No luck. -- God Bless WizarDave Akins Webmaster http://jabi.com Just Another Bright Idea
Re: [Radiant] How can I have a foolproof backup?
Would it be beneficial to have a dreamhost-radiant best practices discussion? Do you use virtual or private servers? What are your findings in terms of resourcing/load etc. I've found the current default passenger configuration is much more radiant friendly than the radiant wiki suggests (one server's settings may not apply more generally however), the only modification I had to make to my environment.rb - once all the gems were installed (a user gems directory was enabled for me by default) - was adding config.gem "rack", :version => '1.1.0' to the top of the config block since I currently have radiant:: cache disabled... Looking into fragment cache. Looking forward to hearing your experiences, perhaps one day radiant could become a dreamhost one-click or scripted install (I've found that memory usage currently runs a little high for the limitations on a standard plan), but there is a healthy niche for it since developer/design teams quite like dreamhost... Paul
Re: [Radiant] How can I have a foolproof backup?
Dave Akins said the following on 06/29/2011 01:08 PM:
> I am using Dreamhost for my site if that makes a difference. (Runs on
> phusion)
:-) So am I
> Am anxious to try 1.0. Thanks to everyone making that happen.
>
> My question is what is the best way to have a fool proof backup before
> upgrading?
The sole purpose of a backup is to be able to a restore.
Many people forget that, not least of all some of the managers I've
worked for - but those Horror Stories, and they are 'Horrible', are not
the point here.
The only reason for a backup is to be able to restore to the prior state.
> I tried the backup extension, but it would not install for me. I was a
> bit concerned anyway since if I break my installation, the extension
> couldn't reinstall my prior working site, could it?
No, but that's beside the point.
You want to _restore_ two things: code and data.
Code: Copy your code to a backup directory and make a note what gems
were used. I have this bad habit of trying to include the gems :-/
Data: back up the database
... read on ...
> I've been keeping regular mysql backups made through phpMyAdmin.
> * Could there be any gotchas there? You can download CSV, SQL, tons of
> other options.
The only issue is 'can you restore it?'
Dreamhost take backups of the SQL database as a matter of course.
I've hosed a (Wordpress) upgrade and restored from the previous days
backup using their on-line tools. Scary ("OMG! I've hosed my DB!!") but
not difficult.
> ** What is the best way to back it up. I'm guessing I need structure and
> data to recreate a corrupted dB if that should happen.
The automatic backups are quite sufficient.
You can take a datadump (CSV etc...) if you want but there is no need.
The only time I've done anything like that is when I've developed and
populated an application on my laptop and moved it to Dreamhost.
> *** Or can I recreate the site and dB through radiant then upload my data?
That sounds like a lot of unnecessary detailed hard work to me.
> ** I also download my gems directory.
You mean ~/.gems
That is prudent.
Dreamhost are not aggressive about updating /usr/lib/ruby//gems/...
so you are very dependent on your local repository.
--
Flying is not dangerous; crashing is dangerous.
