3 ms·

"I'd look into more ready-built solutions like Vercel/Netlify, AWS Amplify, Google Firebase (or maybe App Engine), Shopify, etc. There's probably some vendor th

by zwnow 2y ago

"I'd look into more ready-built solutions like Vercel/Netlify, AWS Amplify, Google Firebase (or maybe App Engine), Shopify, etc. There's probably some vendor that offers what you want for very cheap (but it's not clear to me what you want... more details would help)." That's unfortuneately the issue I have. I want to learn how to actually deploy and manage a site, not how to throw some files to some vendor and let them lift it. I mean, I will have to use some kind of vendor to do it, as I wont use the project to learn. It also wont be a site with tons of traffic, so people won't scream at me if it's down for 5 minutes. To me it just feels wrong to give away management and maintanance tasks to some vendor. It just racks up bills.

solardev 2y ago
If you want to experiment on your own, you can easily spin up a simple LEMP stack with MAMP or XAMPP in a few clicks, and then configure each service to your liking. I don't think there is any business value in maintaining a site that way for a small biz (I think "you don't know what you don't know" applies here, and there are a lot of issues you'll have to solve along the way that you might not have considered upfront). There's certainly educational value. But can't you do that on your own and learn in a lower-risk environment with a side project, instead of making your company's production website reliant on it? If you really don't want to do that, sure, you can still roll your own and either just deploy the whole thing as-is (uploading files and mirroring DBs, etc.) or containerizing it with Docker. For making a reproducible LEMP stack that can be easily transferred to another host, also consider the free tool Lando: https://lando.dev/ https://lando.dev/ It is a CLI wrapper around Docker, specifically for making it easier to deploy containerized LEMP stacks reproducibly.
meiraleal 2y ago
Managing a webserver is such a simple but time consuming effort that you will soon see that using a PaaS is better. But it is worth knowing what they do to serve your website. I definitely don't miss managing apaches and nginxes.

by zwnow 2y ago

solardev 2y ago

If you want to experiment on your own, you can easily spin up a simple LEMP stack with MAMP or XAMPP in a few clicks, and then configure each service to your liking. I don't think there is any business value in maintaining a site that way for a small biz (I think "you don't know what you don't know" applies here, and there are a lot of issues you'll have to solve along the way that you might not have considered upfront). There's certainly educational value. But can't you do that on your own and learn in a lower-risk environment with a side project, instead of making your company's production website reliant on it? If you really don't want to do that, sure, you can still roll your own and either just deploy the whole thing as-is (uploading files and mirroring DBs, etc.) or containerizing it with Docker. For making a reproducible LEMP stack that can be easily transferred to another host, also consider the free tool Lando: https://lando.dev/ https://lando.dev/ It is a CLI wrapper around Docker, specifically for making it easier to deploy containerized LEMP stacks reproducibly.

meiraleal 2y ago

Managing a webserver is such a simple but time consuming effort that you will soon see that using a PaaS is better. But it is worth knowing what they do to serve your website. I definitely don't miss managing apaches and nginxes.