4 ms·
That's how Movable Type used to work. People complained how it took forever to regenerate a big site on a shared host.
by andr 17y ago
That's how Movable Type used to work. People complained how it took forever to regenerate a big site on a shared host.
- tybris 17y agoThe question is: When do you generate the files? Regenerating a large number of file every time you modify something is just bad design (much like regenerating every time a document gets requested). You're better off having a tiny script on each page that checks for modifications when requested and rebuilds if needed (to avoid scripting on the front-end you can use <img> to rebuild for the second request). Alternatives would be to have background processing or batch modifications.
- jrockway 17y agoAngerwhale basically does this. Every page has dependencies, and when the page is requested, it is served from cache unless the dependencies have changed. Otherwise, it is regenerated. Yes, this is not as efficient as static files, but you can drop a file in your directory and it will render as a blog post as soon as someone wants to read it (or a page that links to it somewhere).
- callmeed 17y agoIsn't that the whole concept behind caching+sweepers in Rails?