Adrien Monteleone <adrien.montele...@gmail.com> writes:
>> A side effect of the content being in a db rather than in git is it is no
>> longer stored in a distributed way. So it will be important to implement a
>> backup plan for the data.
>
> The site host should provide a facility for this either through
> cPanel/Plex, or you can set a cron job via SSH. Many have options to
> schedule backups to an offsite FTP server.
>
> You’d need to regularly back up both the db and the site structure.
Okay, so... what's the actual benefit of migrating www.gnucash.org to a
CMS? Right now we can easily update the website remotely, have
translations, images, etc. And it doesn't require Linas to do much
maintenance work. The content is quazi-static, so it really doesn't
need a lot of updates. It's not like the application is changing it's
look at feel every couple months!
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warl...@mit.edu PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
