4 ms·
It's cool, it's trendy, but no. It's not more practical, or quicker to load, or... Maybe more secure, but to make a blog simple dynamic blog secure is easier th
by baby 12y ago
It's cool, it's trendy, but no. It's not more practical, or quicker to load, or... Maybe more secure, but to make a blog simple dynamic blog secure is easier than to understand how to generate a static blog with something like Pelican.
I actually only see downsides:
* I can't write from another computer easily, or a tablet, or a phone...
* I can't easily add options like a search engine, comments (disqus is pretty bad for SEO I presume), most read post, etc...
* I have to use a setup everytime I want to write. I have to open a text editor, I have to launch a terminal and go through command lines to generate the blog again and I have to upload/commit,push the new generated files.
- icebraining 12y agoI can't write from another computer easily, or a tablet, or a phone... Login to Github, edit file?
- chc 12y agoAnd then nothing happens, since "static site" ≠ "hosted on Github"?
- icebraining 12y agoCronjob polling the Github repo, pulling new commits and rebuilding the static pages.
- deleted 12y ago[deleted]
- chc 12y agoAnd you can statically cache pages from a proper blog engine. In fact, that's actually built into some of them, unlike the functionality you describe here for static site engines, which AFAIK all of them require you to write yourself.
- icebraining 12y agoAnd you can statically cache pages from a proper blog engine. That still requires the blog engine to handle potentially malicious requests, prevents hosting on static services like S3 and increases load time for any non-cached page. In fact, that's actually built into some of them, unlike the functionality you describe here for static site engines, which AFAIK all of them require you to write yourself. There are modules like jekyll-hook, which can do it for you.
- baby 12y agoI mean at this point you'd be in much less trouble making a dynamic website.
- icebraining 12y agoIn my experience, these solutions are like passive income; you spend more effort upfront, but save in the long run. I've managed dynamic blogs in the past (first using Dotclear, then Wordpress), and I had to be constantly installing security updates and making sure the backups were being correctly made. Backups on Pelican come for free, since it's all on git and on your machine(s) in the first place.
- 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.
- copperx 12y agoThis only works if you're hosting your static site on GitHub.
- icebraining 12y agoOr if you have some way of pulling the changes (e.g. jekyll-hook, CI server, third-party deployment tool like dploy.io, etc).
- nacs 12y ago> or quicker to load It could certainly be faster to load since a server can push out static files far faster and at a higher rate than compared to say Wordpress/PHP (even with heavy-caching of pages).
- baby 12y agoIf the code is not bloated, and better, if it's cached, I don't think you'll see a notable difference (milliseconds don't count for user experience). I think that feeling of speed is because most static blogs don't have a lot of images, javascript, etc...