3 ms·
> you spend more effort upfront, but save in the long run. Not storing data in a database and not having a inside comment system is not what I call saving in t
by baby 12y ago
> you spend more effort upfront, but save in the long run.
Not storing data in a database and not having a inside comment system is not what I call saving in the long run.
> and I had to be constantly installing security updates
Why use Dotclear or Wordpress then? If you can do what you said you do with Pelican and cronjobs/pulls on the github to automate the task. You should be able to code the blog yourself.
> making sure the backups were being correctly made.
It's really not that hard to automate backups.
> Backups on Pelican come for free, since it's all on git
You're relying on github for backups where I rely on my server for backups.
And as you said somewhere else, if you want something as practical as a dynamic blog you need to be able to add new post through other devices. Since things have to be (re)generated everytime you post you need a server to watch the changes on your github.
The more I think about it the more I feel like it's complicating things for no upsides at all.
- icebraining 12y agoNot storing data in a database and not having a inside comment system is not what I call saving in the long run. The data is in a hierarchical versioned database called a git repository. As for comments, fair enough. I don't happen to use them; if I did, I might choose a different option. Why use Dotclear or Wordpress then? If you can do what you said you do with Pelican and cronjobs/pulls on the github to automate the task. You should be able to code the blog yourself. I thought dynamic engines were supposed to save time? Setting up Pelican was a matter of a couple of hours, if that, and running a command that periodically does git pull and calls the rebuild command takes 5 minutes. It's really not that hard to automate backups. Oh, they're automated. But you still have to test the regularly. Having blind faith in a backup procedure is the surest way to lose data when you need it. http://www.taobackup.com/testing_info.html http://www.taobackup.com/testing_info.html You're relying on github for backups where I rely on my server for backups. Well, no. Git is distributed, so I have a copy on my laptop (which then gets backed up along with all my disk), one on my tablet, etc. Every device where I edit posts is another backup. The more I think about it the more I feel like it's complicating things for no upsides at all. As I said, the advantage are mostly not having to worry about security and backups. Since you consider writing your own blog engine a less complicated solution than installing a Python package and writing a simple cronjob, I think we won't reach a consensus.