4 ms·

I feel like there are so many of these tutorials. The problem is that a person who wants to learn React generally does not care about Debian and something like

I feel like there are so many of these tutorials. The problem is that a person who wants to learn React generally does not care about Debian and something like apt update && apt install nginx. Then depending on who's writing the tutorial, the content ranges from "create a VM and issue these commands" to gcloud commands to spawn VMs. Usually, when a student doesn't know anything about React, they won't know anything about Debian, and the whole tutorial will go over their head. Alternatively, it will be highly shallow. Or, usually, both.

mg 5y ago
The difference to the other tutorials is that this one would not have prerequisites in terms of tools and services. It would not require anything but to copy+paste lines to go along. And that the format of shell commands makes the different approaches very easily compareable. And reproducable. You can put all of the commands into a script and have your own automated template to start new projects. A single Docker container can be used like a fast, lightweight VM. And from there on it is just copy+paste. So on a Linux machine the process would be: 1: docker run -v $(pwd):/var/www --rm -it -p 80:80 debian:11-slim 2: Copy+Paste the lines 3: Enjoy the running web app
- zealsham 5y ago
  On the other hand , a tutorial like this needs to be actively maintained as packages come and go . It’s essentially a documentation
  - mg 5y ago
    Yes. I would expect the article to become an "eternal cornerstone of web development" which evolves with the stacks. After a few years, the history if it would be very interesting. It would show how much maintenance a minimal web app based on the different approaches needed.
- BossingAround 5y ago
  Docker is a tool prerequisite. For example, on a SELinux system, docker run -v $(pwd):/var/www will cause issues (because you need -v "$(pwd)":/var/www:z). Also, isn't -v deprecated? What I'm highlighting is: * The knowledge depth and time required on your part to maintain the text such that it works on all supported systems * The fact that you're depending on a number of tools that might become obsolete quite fast, which might throw a wrench into your text. ** For example, Docker stops supporting CLI due to licensing. Linux splinters off to podman, Windows creates its own tool, macOS users will generally continue working with Docker. You'll then be forced to migrate to a different tool, like Vagrant. Rather than create a text that's a "bring your own developer workstation", create a webpage that I pay $15 for monthly, you record a video explaining a concept, and then you have a button that says "spin up a lab for X". This throws me to a controlled environment, e.g. in AWS, where you tell me the exact steps that will achieve what I want to achieve.

mg 5y ago

The difference to the other tutorials is that this one would not have prerequisites in terms of tools and services. It would not require anything but to copy+paste lines to go along. And that the format of shell commands makes the different approaches very easily compareable. And reproducable. You can put all of the commands into a script and have your own automated template to start new projects. A single Docker container can be used like a fast, lightweight VM. And from there on it is just copy+paste. So on a Linux machine the process would be: 1: docker run -v $(pwd):/var/www --rm -it -p 80:80 debian:11-slim 2: Copy+Paste the lines 3: Enjoy the running web app

zealsham 5y ago
On the other hand , a tutorial like this needs to be actively maintained as packages come and go . It’s essentially a documentation
- mg 5y ago
  Yes. I would expect the article to become an "eternal cornerstone of web development" which evolves with the stacks. After a few years, the history if it would be very interesting. It would show how much maintenance a minimal web app based on the different approaches needed.
BossingAround 5y ago
Docker is a tool prerequisite. For example, on a SELinux system, docker run -v $(pwd):/var/www will cause issues (because you need -v "$(pwd)":/var/www:z). Also, isn't -v deprecated? What I'm highlighting is: * The knowledge depth and time required on your part to maintain the text such that it works on all supported systems * The fact that you're depending on a number of tools that might become obsolete quite fast, which might throw a wrench into your text. ** For example, Docker stops supporting CLI due to licensing. Linux splinters off to podman, Windows creates its own tool, macOS users will generally continue working with Docker. You'll then be forced to migrate to a different tool, like Vagrant. Rather than create a text that's a "bring your own developer workstation", create a webpage that I pay $15 for monthly, you record a video explaining a concept, and then you have a button that says "spin up a lab for X". This throws me to a controlled environment, e.g. in AWS, where you tell me the exact steps that will achieve what I want to achieve.