Linux bash script: db/web backup to remote fs
Posted: Thu Apr 08, 2010 10:23 pm
I have written a bash script for automating backups of CMSMS to a remote filesystem using Ubuntu linux, that:
-- logs the results and errors in a friendly manner
-- mounts a remote filesystem (user specified)
-- backs up the SQL and website (user specified)
-- transfers to the remote fs, making a directory per backup
-- rotates the remote fs, keeping only the last N backups (user specified)
-- retains failed backups in /tmp
-- rotates the error results in /tmp, keeping only the last N errors (user specified)
-- dismounts remote filesystem
-- emails the logged results to somewhere (user specified)
I've never written software for public distribution before, and I'm not sure what I should do with this. (I don't really consider shell scripts "software" in the proper sense anyway.)
Should I put it on sourceforge as a project by itself?
Should it be included with CMSMS in its file repository?
Just post it straight to the CMSMS wiki in raw text format?
I'm not thrilled about the idea of posting it direct on the wiki since anyone could insert changes into it without clear notice that changes were made.
-- logs the results and errors in a friendly manner
-- mounts a remote filesystem (user specified)
-- backs up the SQL and website (user specified)
-- transfers to the remote fs, making a directory per backup
-- rotates the remote fs, keeping only the last N backups (user specified)
-- retains failed backups in /tmp
-- rotates the error results in /tmp, keeping only the last N errors (user specified)
-- dismounts remote filesystem
-- emails the logged results to somewhere (user specified)
I've never written software for public distribution before, and I'm not sure what I should do with this. (I don't really consider shell scripts "software" in the proper sense anyway.)
Should I put it on sourceforge as a project by itself?
Should it be included with CMSMS in its file repository?
Just post it straight to the CMSMS wiki in raw text format?
I'm not thrilled about the idea of posting it direct on the wiki since anyone could insert changes into it without clear notice that changes were made.