Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
1–10 of 23 posts
Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#2Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#3I'm not much into this thing of just uploading pictures, but I guess I would like to work into turning your Tumbless into a more full-featured static-website solution for non-devs, that works from the browser.
Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#4Do you know of any other approaches to managing a site directly from browser to S3? Because this is awesome. I'm not much into this thing of just uploading pictures, but I guess I would like to work into turning your Tumbless into a more full-featured static-website solution for non-devs, that works from the browser.
https://github.com/ChrisZieba/dodgercms
Regardless, I think this is something that would be awesome to have. You can even throw in some AWS Lambda if you want to move some stuff out of the browser(like generating thumbnails/index pages/etc). Or just use Lambda to run a complete static site generator(like jekyll or pelican) every time the content in an S3 bucket changes.
Note: I've never actually used either of these, but I did spend a fair amount of time researching this type of stuff.
Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#5Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#6Might I interest you in a CDN rather than serving static files out of S3 in a single region?
Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#7Might I interest you in a CDN rather than serving static files out of S3 in a single region?
You can use cross-region replication. But CDN might be a cheaper solution if you have a high volume traffic. Imagine HN runs entirely on S3, then using CDN will likely be cheaper and more responsive. I haven't done the calculation though.
This is meant for backing up S3 data for DR, not for HA in the traditional sense (EDIT: it can be used for HA, but you're going to need health checks for your origin DNS record so your CDN is always pointed at an available origin). Always, always, always use a CDN in front of S3 if you're serving static content for public consumption from that bucket.
Data out of S3 is more expensive than data out of a CDN (even Cloudfront), and S3 has orders of magnitude higher latency than a CDN (occasionally hundreds of milliseconds).
Disclaimer: Devops who works with S3 and several CDNs day in and day out.
Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#8Do you know of any other approaches to managing a site directly from browser to S3? Because this is awesome. I'm not much into this thing of just uploading pictures, but I guess I would like to work into turning your Tumbless into a more full-featured static-website solution for non-devs, that works from the browser.
Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#9Do you know of any other approaches to managing a site directly from browser to S3? Because this is awesome. I'm not much into this thing of just uploading pictures, but I guess I would like to work into turning your Tumbless into a more full-featured static-website solution for non-devs, that works from the browser.
You could look into adding a few lambda functions behind API gateway for functionality that you can't get natively from HTML5. It would be about the same difficulty of installation and have the same management profile (ie. upload and basically be done with it).
Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3
#10Earlier quoted context omitted.
You could look into adding a few lambda functions behind API gateway for functionality that you can't get natively from HTML5. It would be about the same difficulty of installation and have the same management profile (ie. upload and basically be done with it).
I guess one cold wrap a video transcoding engine into a lambda to keep traffic costs down.