Live data from Hacker News

Ask HN: Optimal cloud service to run tiny website with back end Python + SQLite?

news.ycombinator.com

11–20 of 79 posts

Re: Ask HN: Optimal cloud service to run tiny website with back end Python + SQLite?

#11
I suggest aws (probably elasticbeanstalk, maybe a raw box) simply because it's a very well trodden path. Lots of helpdocs, tutorials, instructions, etc etc etc.

Assuming you're a professional in the US / west europe, etc, the diff between $20 or $30/mo and $5 or $0 per month is negligible, while the time savings just from staying on a standard path can be huge.

My default suggestion would be:

Elastic Load Balancer, to talk to the internet and terminate SSL;

Elastic Beanstalk or something similar to host a box;

Certificate Manager for your SSL cert;

Route53 to serve your DNS.

All of the above should be cheap and, again, a very well trodden path with tons of help docs and people familiar with configuration.

Re: Ask HN: Optimal cloud service to run tiny website with back end Python + SQLite?

#12
post #10

Dokku + your favorite VPS: http://dokku.viewdocs.io/dokku/ Installation is a breeze and there are plugins. If you're at all familiar with Heroku's deploy, you'll love this. It's the closest thing I've found to `git push` without any thinking.

Glad to see that dokku is still alive. Definitely recommend this.

Re: Ask HN: Optimal cloud service to run tiny website with back end Python + SQLite?

#15
post #5

how about a raspberry pi and dyndns?

I would worry about being DoS'ed, and having my home network compromised because of a vulnerability in raspberry pi software stack. Other than that, I think it's a good idea. I do the same for a personal use server, but don't expose the port on the public internet.

Re: Ask HN: Optimal cloud service to run tiny website with back end Python + SQLite?

#19
post #5

how about a raspberry pi and dyndns?

I would worry about being DoS'ed, and having my home network compromised because of a vulnerability in raspberry pi software stack. Other than that, I think it's a good idea. I do the same for a personal use server, but don't expose the port on the public internet.

If you put Pi in a segmented network this is a good solution. That's what I do now anyway with python + sqlite and Netgate sg-1100 as a firewall
Post reply on HN