Where would you host a container based Node API that connects to a non-public Postgres database?
Four ways to build web apps
71–80 of 181 posts
Re: Four ways to build web apps
#72Earlier quoted context omitted.
It's not obvious but you can host an entire website or simple web app on AWS Lambda (as simple as a single function).
I host a full Web app on Lambda like so https://github.com/kaihendry/ltabus
Re: Four ways to build web apps
#73Hugo is wonderful, until a deployment bug or misconfiguration exposes all of your server settings in a page that should be serving a 404 instead. Wordpress, Hugo and others also get constant attacks from hackers who can exploit each bug found on thousands of sites all at once.
Go has fantastic server examples and plenty of starter templates you can use to build your own server, and deploy to Heroku and scale to millions of users far cheaper in engineering and financial terms.
Re: Four ways to build web apps
#74I guess the title should have been "Four Ways to Deploy Web Apps", not "build" them. Granted, option #2 (functions) is a different beast, but all others can be built the same way but deployed differently. For example - You can develop a static (Hugo) web site then deploy it on Fly.io using containers. or - You can develop a container based web site, then deploy it on a bare Linux server (k8s is not necessary for a fe…
Re: Four ways to build web apps
#75Earlier quoted context omitted.
They may cut the extent of a free offering, but I suppose they won't drop it. An ability to make a quick proof of concept, to just try something and play with it, is very important for bringing in paying customers. People tend to buy with more confidence things they already know and comfortable with. People tend to pay for things that are widely known, with tons of examples and explanations online; free services gene…
That might be true but it really depends how many can convert. Recently Heroku dropped their free tier as well as Fly.io having a credit card only free trial in order to deter scammers.
Re: Four ways to build web apps
#76I agree with this, except I would take 3 out of the list.
3 is the most attractive option to me. I have a tiny localhost server I wrote, and have been looking for a simple way to deploy
Re: Four ways to build web apps
#77Why recommend lock-in vendors when there are better options in between? There was no mention of Heroku which is easy and scalable. Hugo is wonderful, until a deployment bug or misconfiguration exposes all of your server settings in a page that should be serving a 404 instead. Wordpress, Hugo and others also get constant attacks from hackers who can exploit each bug found on thousands of sites all at once. Go has fant…
Re: Four ways to build web apps
#785th option: Webflow, airtable, whalesync. I could recreate one of his examples ( https://oldgames.win/ ) in 10-20 minutes off just a CSV file... And I could use something like https://simplescraper.io/ to scrape that data + find imagery.
Re: Four ways to build web apps
#79Why not PHP on a shared or dedicated hosted server?
I wouldn't recommend PHP to anyone who isn't already invested/emerged in the language. Wordpress for blogs or websites on a shared host with automatic updates and a few select plugins? Yes. Laravel or Symphony for applications? Ok. But just PHP has way too many footguns and doesn't provide nearly enough affordances to make them worth it IMO. Plus it's a language that breaks backwards compatibility way too often, stop…
Re: Four ways to build web apps
#80Easier way > HTML + CSS + Javascript (vanilla or framework) + Server side language of choice.
Deploying is not building.