5 ms·
While this is a great learning experience, it is hard to write a blog engine that will stand up to traffic spikes on the first try. If your goal is learning a
by masnick 15y ago
While this is a great learning experience, it is hard to write a blog engine that will stand up to traffic spikes on the first try.
If your goal is learning a new language or framework, this is a great idea. If your goal is to have a reliable, traffic-resistant blog I think it's best to stick with a tried and true platform.
- seunosewa 15y agoIt's not hard. Just write a blog engine that generates static html pages.
- masnick 15y agoRight, if you write something akin to Jekyll it will work fine. However, I think most people would probably be trying to learn a framework like Rails or Django if they were writing a blogging engine to learn a new language/framework.
- mapleoin 15y agoSo write your blogging engine as you normally would and then make a button which says: dump to html for each page and then figure out when you want that button to be pressed (i.e. manually or automatically). More things to learn. Yay!
- sunkencity 15y agoBuild it anyway you like but then wget --mirror before rsync to deploy.
- mike-cardwell 15y agoOr use caching. My webpages are generated using FastCGI and served by Nginx. So I configured Nginx's FastCGI module to internally cache GET requests for 1 minute.