app-engine-cloud-run- VS LetsShip

If you haven't checked out App Engine in a while, you really should. Especially check out the App Engine "Flexible" editions, which make it really easy to run on App Engine withOUT getting locked in.

I run a NodeJS GraphQL server in App Engine Flexible, and it is basically just like running it in a Docker container. It's also pretty trivial to run in Google Cloud Run if I so desired, there is even a tool to assist: https://github.com/GoogleCloudPlatform/app-engine-cloud-run-...

I have two DigitalOcean sites on the same VPS just serving from kestrel behind an nginx reverse proxy and then one site on a Hetzner VPS where I was playing around with k3s.

For digitalocean I followed this post which is probably way out of date now https://www.hanselman.com/blog/publishing-an-aspnet-core-web...

For the k3s site the source is here https://github.com/EliotJones/LetsShip/blob/main/kubernetes/... though worth noting I have set up LetsEncrypt incorrectly but that's my lack of k3s understanding.

This - https://github.com/EliotJones/LetsShip - hopefully gets you some of the way, it uses VS on Windows for development but I can't imagine the experience in Rider or VS Code for Linux is too disimilar. Individual steps here https://github.com/EliotJones/LetsShip/tree/main/docs/posts

I need to complete the full guide at some point but the end result is an application deployed on Linux with both a web app and independently scalable crawling services with zero downtime deployments. Hosted site here: https://pricefalcon.me/

For a simpler deployment without k3s, this guide is the one I originally followed for my trends site and should still work for .NET 6. https://www.hanselman.com/blog/publishing-an-aspnet-core-web...

One example here https://github.com/EliotJones/LetsShip/blob/main/src/PriceFalcon.JobRunner/Worker.cs#L111 where I have several agent applications each of which may start up to 5 jobs, a job can take a couple of minutes to execute and while running the same request twice isn't the end of the world I'd prefer to avoid it. I use FOR UPDATE when selecting to take an update lock on the row in postgres (similar functionality hopefully exists for your DB).

I just build out a new MVP site for the purposes of a tutorial with .NET 5 and jQuery with some slightly complex front-end requirements (an interactive iFrame that validates user selections server-side on click) and though it may need to move to an SPA if it got more complex for now jQuery is fine (though assuming IE support is not needed I could have probably just used raw JS instead). https://github.com/EliotJones/LetsShip

I've done a complete 180 on this too, I realised I was reacting from my default position of hostility to new concepts rather than an honest appraisal. I am writing it up at the moment but I've been working on a 1 person SAAS MVP tutorial [0] and though I've definitely misconfigured something having the ability to go from git push to deployed to production with 0 downtime inside of 5 minutes with no manual steps is such a nice flow, versus my previous attempts of SCP and faffing around with services.

[0]: https://github.com/EliotJones/LetsShip