11–20 of 31 posts
Stop wasting time debating and just use .NET, don't overthink things.
I'm biased but I'd go with .NET if you actually want to get the thing built. Obviously use a new stack if you want to use it as a learning experience. With .NET Core and Postgres you can get something stood up within a few days and host on a cheap Linode, Digital Ocean or another provider's box for $6 a month or so. That should last you scalability wise until you have enough money from it to do something else and giv…
Earlier quoted context omitted.
What’s the easiest/best way to host python+flask?
Easiest? Probably heroku after you get past the initial boilerplate - but can quickly become expensive. Most cost efficient would be to Spin up a cheap droplet in digital ocean, install docker-compose with a Postgres service and python image. In the python image, just boot up a Django server on port 80. If you need https, youll need to add something in front of Django, like nginx to handle ssl termination. App engine…
Can’t really go wrong with python + Django (or flask if you want to stay minimal). Sounds like you’ll need auth, so Django should support that out of the box. Both will integrate easily with Postgres, and for flask, take a look at the peewee ORM.
Earlier quoted context omitted.
Easiest? Probably heroku after you get past the initial boilerplate - but can quickly become expensive. Most cost efficient would be to Spin up a cheap droplet in digital ocean, install docker-compose with a Postgres service and python image. In the python image, just boot up a Django server on port 80. If you need https, youll need to add something in front of Django, like nginx to handle ssl termination. App engine…
I'd use Gunicorn instead of Django dev server.
Can’t really go wrong with python + Django (or flask if you want to stay minimal). Sounds like you’ll need auth, so Django should support that out of the box. Both will integrate easily with Postgres, and for flask, take a look at the peewee ORM.
What’s the easiest/best way to host python+flask?
You can use a digital ocean or light sail instance to host Dokku for way cheaper than Heroku and you have more control of the machine. Downside is Dokku is made for one server, so you can only really scale to like 64 cores before you need something else.
Most apps will never need more than one server realistically, but you have to determine that for yourself!
I use it for a Flask app. FWIW, I believe digital ocean has tutorials and an image to use to get Dokku off the ground fast!
Can’t really go wrong with python + Django (or flask if you want to stay minimal). Sounds like you’ll need auth, so Django should support that out of the box. Both will integrate easily with Postgres, and for flask, take a look at the peewee ORM.
What’s the easiest/best way to host python+flask?
I'm biased but I'd go with .NET if you actually want to get the thing built. Obviously use a new stack if you want to use it as a learning experience. With .NET Core and Postgres you can get something stood up within a few days and host on a cheap Linode, Digital Ocean or another provider's box for $6 a month or so. That should last you scalability wise until you have enough money from it to do something else and giv…
This was my main plan, is hosting .Net Core easy to do on a bare-bones image like DO or Linode? Or is it worth to pony up for a Azure App instance?
I just logged into Digital Ocean to check, I'm running a single 512 MB memory droplet with a 20GB disk for $6 a month and apart from getting familiar with Linux (especially managing user permissions correctly), setup was easy, I run an Nginx reverse proxy in front of a Kestrel instance but I know people have said you don't even need Nginx.
I also used Let's Encrypt for a free SSL certificate and setting that up to correctly refresh on a CRON job was the hardest part of the whole thing.
I've no doubt the site [1] would fall over if it ever got anything like the HN hug of death but this would be easy to plan for assuming organic growth, I imagine there are fairly easy ways to set up load balancing for droplets on DO and moving the database onto a separate droplet etc should give you enough headroom for scaling.
The code [2] is way outdated now and awful quality but it's on GitHub.
Others who have more experience may say it's worth learning a certain cloud feature or serverless stuff but my gut feeling is it's better to get the thing out there and worry about that sort of stuff when you get there.
Edit: It's worth mentioning that [0] talks about developing the site on Linux, though I did that just to get a feel for Linux it's not at all necessary and much easier to do the development on Windows with Visual Studio then all you need to do is:
dotnet publish -c Release -r linux-x64
[0]: https://www.hanselman.com/blog/PublishingAnASPNETCoreWebsite...
As for .NET hosting prices, I don't understand why you need complex hosting. A smallish instance paired with SQL Server RDS (both of which can be hosted on Linux or Windows) should suffice.
Keep in mind that both AWS and Azure offer a free tier when you're starting up:
If you are not familiar with ruby, go with a language you are familiar with. There is a clone in every major language. It’s just that RoR is the “original”.