> you could fairly easily host most things on a old fashioned lamp host (I am talking decades ago) and all you had to know was basic file transferring
Setting up and maintaining a server is easier today than it was decades ago, A LAMP at this time meant a lot of manual setup, IaC wasn't a thing, reproducibility wasn't a goal, versioning was confidential, documentation was scarce and often outdated, out of the box security was lower, ties to the OS were higher. Managing virtual hosts was clunky, updating OS/PHP was risky. I would not go back for anything.
> having to setup docker properly (rootless and all that)
Rootless being the proper way to setup Docker is a highly controversial take. You will mostly get added complexity and a false sentiment of security from it.
> A LAMP at this time meant a lot of manual setup, IaC wasn't a thing,
I'm sorry but this is just nonsense. LAMP is called that because it was a very standardized thing. Pop in a Debian CD and select a ready made profile for it. There were even ready made installers for Windows and Mac if you weren't on an Internet native operating system.
A lot more people got by using custom bash scripts, but cfengine exited in the 90s. It's still not honest to say things were more manual. Take a look at /r/homelab or somewhere selfhosters hang out today and look at the Compose or self hosted K8s stacks people set up today. That's orders of magnitude more manual work than just popping in a CD and selecting LAMP.
Yes, those are not the same thing. Yes, a self hosted stack today consists of so much more than running PHP in a web server. But for self hosters, the amount of work required has objectively gone through the roof. That's a problem if your goal is data sovereignty.
> op in a Debian CD and select a ready made profile for it.
At the time in question here tasksel wasn't a thing, I think merely a concept. It made its way in Debian installer around 20005 IIRC, right along "one-click installs" from hosting services mentioned in the other reply. The whole decade before that, indeed manual set up was needed.
> at /r/homelab or somewhere selfhosters hang out today [...] That's orders of magnitude more manual work
There is two kinds of self-hosters, those who aim at reproducibility and those who don't. The latter is more fun, the former gets quickly mandatory when you _rely_ on your homelab.
> Setting up and maintaining a server is easier today than it was decades ago, A LAMP at this time meant a lot of manual setup, IaC wasn't a thing, reproducibility wasn't a goal, versioning was confidential, documentation was scarce and often outdated, out of the box security was lower, ties to the OS were higher. Managing virtual hosts was clunky, updating OS/PHP was risky. I would not go back for anything.
You are speeding past my point by a mile or two. With a shared webhost you get a ready lamp stack. In the late 90s early 2000s you could fairly easily get a wide array of software running that way. All you had to do is create a database in the hosters control panel, upload the package and you'd be on your way. Later in the 2000s one click installers came along for popular packages making it even easier. In fact, they are still around these days making it extremely easy to install a wide array of lamp based applications to these days.
There are very few options these days to get started as easily these days with modern non lamp tech stacks. The only thing I am familiar with (other than the product presented to us in this post) is pikapods, [which only offers a limited selection of available applications](https://www.pikapods.com/apps). There are a few others, also catalog based, though they more seem to focus on deploying on other platforms for you. Other than that you start to quickly move to more complex hosting solutions aimed at business and scaling. Or platforms that are cloud platforms with all the added complexity to navigate and figure out before you can deploy docker containers. Not to mention ridiculous situation that a few of the ones I know about have pivoted to being "agentic compute providers" whatever that means and certainly will confuse a novice.
Which means that the "practical" advice given is often to "just" set up a VPS. And yes, many VPS providers will provide an image with docker enabled, but that is just the start.
> Rootless being the proper way to setup Docker is a highly controversial take. You will mostly get added complexity and a false sentiment of security from it.
That, in fact, is another layer of complexity people will then have to figure out. Most information I am aware of these days does claim that it is better to run containers rootless or at the very least make sure the user in the container is non root. The fact that we are both convinced of the opposite tells you how confusing it must be for a novice.
The overall point I am trying to make isn't even about the exact details. It is that for hosting something these days there is much more required surrounding knowledge required before you can get started in most cases.
Sounds like a marketing service had the idea to "simplify git", the presentation sounds like they haven't heard of git flows, and no offline mode is total no-go for me.
> Think about this: if your Internet connection went down, could you continue to do your job
Reads like "don't you guys have phones". My bet is it will be forgotten in a year.
After two years of using Teams daily I still cruelly Slack for a ridiculously long list of reasons. Teams is a casual chat product as best it doesn't belong to enterprise world.
I've used many frameworks and in my opinion Svelte+Sveltekit has the very best simplcity over power ratio. If you don't mind job offers being quite scarce for this stack right now that's about the best choice. You can do the Svelte tutorial for a sneak peek of this.
> Unfortunately, [the ruling] means we have no other choice than to extend the temporary suspension of activity in our French distribution centers while we assess the best way to operate with regards to the court of appeal’s decision
So I'm not sure how it's related to what you say. There are a lot of similar businesses that can continue shipping as usual and I would be very surprised if the Law has checked all of them for safety measures respect. It is highly probable that many of them don't do things correctly yet nobody cares. In the end this is typical of the French government hypocrisy that is going for the big (foreign) one just for the sake of symbolism. Cdiscount is a huge French Amazon clone that can still operate as usual, I can bet some of their employees are also at risk.
> The company said the closure would affect “millions of
clients who use our services to have products delivered to
their homes during this confinement period” as well as
"employees and small and medium sized businesses" that use
the company.
Regarding inspection of other companies, please refer to my answer to js4ever in the same thread.
EDIT : also, "others do just as bad" is never a good defense.
Setting up and maintaining a server is easier today than it was decades ago, A LAMP at this time meant a lot of manual setup, IaC wasn't a thing, reproducibility wasn't a goal, versioning was confidential, documentation was scarce and often outdated, out of the box security was lower, ties to the OS were higher. Managing virtual hosts was clunky, updating OS/PHP was risky. I would not go back for anything.
> having to setup docker properly (rootless and all that)
Rootless being the proper way to setup Docker is a highly controversial take. You will mostly get added complexity and a false sentiment of security from it.
reply