Backing up website
Permalink
Hi,
I'm new to Concrete5.
I'm developing a website on a Dreamhost server with Concrete5 v5.5.2.1. I'm doing the actual editing on a Windows 7 box with Firefox 9.0.1.
I decided it would be a good idea to make daily backups of my work in progress, so I wrote a script on my local Linux box to SSH into the Dreamhost server, tar up my entire website directory tree (including Concrete subdirs), and FTP it back to the local box. The script runs every day at midnight as a cron job.
So far, so good. Today, I made a change to the site and hosed a few things up, so I decided to restore last night's backup. I FTP'd the newest tarball back up to Dreamhost, renamed my existing site directory to *.old, and unzipped the backup archive. When I went back into the Concrete editor, my new changes were still there.
What am I missing? I have caching turned off, and the tar achive looks fine.
Thanks in advance for your help,
Mike
I'm new to Concrete5.
I'm developing a website on a Dreamhost server with Concrete5 v5.5.2.1. I'm doing the actual editing on a Windows 7 box with Firefox 9.0.1.
I decided it would be a good idea to make daily backups of my work in progress, so I wrote a script on my local Linux box to SSH into the Dreamhost server, tar up my entire website directory tree (including Concrete subdirs), and FTP it back to the local box. The script runs every day at midnight as a cron job.
So far, so good. Today, I made a change to the site and hosed a few things up, so I decided to restore last night's backup. I FTP'd the newest tarball back up to Dreamhost, renamed my existing site directory to *.old, and unzipped the backup archive. When I went back into the Concrete editor, my new changes were still there.
What am I missing? I have caching turned off, and the tar achive looks fine.
Thanks in advance for your help,
Mike
This might be a stupid question but: did you also restore the database? That's were all the changes are saved.
Ah, no. (embarrassed grin)
Can you point me to instructions for backing up the database? I assume it's not as simple as what I've been doing with my little cron circus.
What is the relationship between the site design and the database? I thought that the DB was just for user stuff like blog entries, site statistics, etc. It would appear that I was wrong.
Thanks for responding.
Mike
P.S. If you feel like telling me to RTFM, feel free. Just point me to the FM. :-)
Can you point me to instructions for backing up the database? I assume it's not as simple as what I've been doing with my little cron circus.
What is the relationship between the site design and the database? I thought that the DB was just for user stuff like blog entries, site statistics, etc. It would appear that I was wrong.
Thanks for responding.
Mike
P.S. If you feel like telling me to RTFM, feel free. Just point me to the FM. :-)
The DB saves any kind of change you make to the site that isn't hardcoded in your HTML / PHP / CSS files.
You can backup and export your database within C5. Just search for "Backup" in the search bar, backup the DB, download the SQL file and then import it via phpMyAdmin (or the mySQL tool of your choice) into another DB (you might have to edit the SQL file to match the database names if you import it into another DB than the one you made the backup from, no big deal though).
Of course you can also set up a cron job to make scheduled backups of your DB. This has to be done outside C5 though as there is no automated process as far as I know.
But maybe you can save yourself all the trouble and just revert a given page back to an earlier stage in the development. C5 has built in versioning for everything you change on the site. For further information:http://www.concrete5.org/documentation/general-topics/versions/...
You can backup and export your database within C5. Just search for "Backup" in the search bar, backup the DB, download the SQL file and then import it via phpMyAdmin (or the mySQL tool of your choice) into another DB (you might have to edit the SQL file to match the database names if you import it into another DB than the one you made the backup from, no big deal though).
Of course you can also set up a cron job to make scheduled backups of your DB. This has to be done outside C5 though as there is no automated process as far as I know.
But maybe you can save yourself all the trouble and just revert a given page back to an earlier stage in the development. C5 has built in versioning for everything you change on the site. For further information:http://www.concrete5.org/documentation/general-topics/versions/...
Thanks for your response.
I'd like to talk about the C5 versioning system for a moment. In addition to the fact that its behavior is extremely squirrely, it's also true that there are separate versioning systems for the site and for the stacks, and there apparently isn't any version history at all for custom theme changes.
Ideally, I would like a have a method of backing up the entire site all at once, and being able to restore *everything* to exactly the state it was in when the backup was made. It would be great if I could do this without having to wrestle with multiple version histories, or, on the server side, without having to synchronize separate DB and code archives.
Am I wishing for too much?
Thanks again for your help,
Mike
I'd like to talk about the C5 versioning system for a moment. In addition to the fact that its behavior is extremely squirrely, it's also true that there are separate versioning systems for the site and for the stacks, and there apparently isn't any version history at all for custom theme changes.
Ideally, I would like a have a method of backing up the entire site all at once, and being able to restore *everything* to exactly the state it was in when the backup was made. It would be great if I could do this without having to wrestle with multiple version histories, or, on the server side, without having to synchronize separate DB and code archives.
Am I wishing for too much?
Thanks again for your help,
Mike
The only way I see for that to come true ist to make a 100% file and DB backup and store it away. This way you can restore the state you saved some time later by uploading it to the server and restoring the DB.
