Hacker News Reader

Comment by yuvadam | Hacker News Reader

Yeah, deployment scenarios where you have no application layer, and can only deploy static assets (S3, GitHub pages and the likes).

View on HN

That's interesting. So basically it's for rendering pages and then pushing them on to S3/Other-static-storage and serving them from there ?

I don't see any particular gains however since high traffic pages (static or otherwise..) served off S3 will end up costing way more than on a shared host/dedicated server.

What would be an exact use case where this would really be important and help out ? I'm just trying to understand what need it solves and under what circumstances hosting static pages on S3 is beneficial in cost/performance.

Our last 2 clients have asked for static solutions because they don't have the capacity to maintain django apps down the line and don't want to hire new staff or continue paying us for maintenance.

We ended up developing both sites in django, which made it easy for them to add copy during development and see how it would actually look on the site. Once finished, we got the HTML output and sent it over for them to put up on their servers.

We were pretty happy with how it turned out, and I think django-medusa being able to automate the whole rendering to html files would be nice if we have to do it again.

I see, that makes perfect sense! So it's an interesting thing for website development businesses. Especially the part where you allow the client to modify 'static' content.

Well, in that case I can see how this tool could be really handy! Thanks for the input :)

I'm imagining a setup now where we host their staging environment as it would effectively just be disk space, and when they want to publish changes it could render using this and publish to wherever the static files are hosted (S3, their own service, provide them as a zipped download, etc.).

Small site for which app server is overkill and s3 charges will be minimal.

Reply on news.ycombinator.com