Thanks to Clay and Ike, I'm a Wordpress user as well. I revamped my site earlier this year (thanks, Ike!), but it's still not complete. I've had other priorities come up in the mean time...
It's not just CMS's that do that though. Separating content from styling has been a hot thing to do since the early 2000's. I forget the exact date, but it was definitely pre-2004. Once we got past layout with tables, and turned to layout with CSS, good things happened.
EDIT: I'm not trying to be argumentative, just trying to help those out making their sites for the first time in a long time. If you haven't played around with CSS yet, you can do quite a lot of things with it.
Originally Posted by Tim Gray
It's not just CMS's that do that though. Separating content from styling has been a hot thing to do since the early 2000's. I forget the exact date, but it was definitely pre-2004. Once we got past layout with tables, and turned to layout with CSS, good things happened.
EDIT: I'm not trying to be argumentative, just trying to help those out making their sites for the first time in a long time. If you haven't played around with CSS yet, you can do quite a lot of things with it.
I have done a couple of simple sites in the past using CSS so can cope with a degree of scripting but have started to explore the Wordpress option in terms of providing a framework that may result in an easier to update website.
UNIX geeky stuff to follow: I use a shell script that runs twice a week via cron to run mysqldump and copy/email/rsync/whatever you want. To rsync the rest of the site, the non-database content, I run rsync from the command line. That is not automated yet, but again, it could easily be automated by adding the appropriate line in as a cronjob.
As long as both your source and target computers have rsync installed, and the remote computer has ssh open, you should be able to rsync data with no problems. I believe OS X, at least since 10.5, has rsync built in. Most hosting services also give you ssh and rsync access, so you should be fine. If you want to catch the database component at the same time, you'd need to make sure to dump your database to a file in an appropriate location (a backups subdirectory maybe?) and then rsync the whole website.
There are of course other options than rsync. I like it because it can be automated easily. Many FTP/SFTP programs have 'sync' features that let you sync up a local copy of a remote directory.
#! /bin/sh -
EXCLUDE='--exclude **.svn --exclude .DS_Store --exclude cache --exclude error_log'
OPTIONS='-av'
DELETE="--delete-after"
DEST='/Users/me/localdir/'
SOURCE='user@host.com:/path/tosite/onserver/'
rsync -e "ssh -p 22" $OPTIONS $DELETE $EXCLUDE $SOURCE $DEST
Here's my rsync script:
I run this from my *local* computer. It rsyncs from the remote server to the local destination. You obviously need to set DEST and SOURCE appropriately. You also might want to take a look at the options. I have it set up to delete files locally that no longer exist remotely - it's a mirror. Obviously, this can be playing with fire if you don't know what you are doing.
You could also have a version that runs remotely on the server, but the destination would have to have a port exposed to the internet and always be on with a known address. Since that's not true of my laptop, I 'pull' stuff from the server instead of 'pushing' it from the server.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?