Migrate BaseCamp devcontainer into EVerest devcontainer

[florinmihut]

• Add devrd script
  • This introduces a couple of features like managing multiple containers, nodered flows and allowing devcontainer usage without vscode
• Add bash/zsh completion

[andistorm]

The general layout looks really good to me! Unfortunately I wasn't able to test it yet, I plan to do so in next feedback loop

• I made a lot of comments regarding naming and inline comments. I think this is quite important especially in a bash script environenment that is hard to read and error-prone.
• A lot of things should be moved to the dev-env-base image instead of being duplicated here.

• Discuss: What happens when the nodered service is running and someone uses a run nodered script? I would vote for removing one of those options sop it is clear how to use nodered as service for everest sil

• Documentation: The README.md is way to big. It's contents + REQUIREMENTS.md should be moved to the main documentation. The README should only include hints about what is inside this repository and roughly how to work with the repos contents and a link to the main documentation. So the usage of devcontainer tooling belongs to main documentation. I would suggest to split the devcontainer docs into the following chunks in the new upcoming docs structure:

  • Tutorial: How to setup first devcontainer/dev environment and start sil or so
  • How to guide: A bit advanced features as starting/stopping services using other profiles, using environemt variables, all the available commands
  • Explanation: How does the devcontainer works: devcontainer vs docker compose, ports, all the stuff in the background which a developer would need to work on the tooling
  • Reference: The Requirements could be protocol

led here as reference, but could also be omitted in my opinion. We only talked about F1-F7

• The old documentation should be removed/adapted
• Documentation should fit to the general getting started guide. Either it should replace it, extend it or link against each other
• Are there already related PRs in the corresping repositories I have overseen?

If you have any questions on my comments we also can set up a call to discuss it

[andistorm]

The general layout looks really good to me! Unfortunately I wasn't able to test it yet, I plan to do so in next feedback loop

• I made a lot of comments regarding naming and inline comments. I think this is quite important especially in a bash script environenment that is hard to read and error-prone.
• A lot of things should be moved to the dev-env-base image instead of being duplicated here.
• What happens when the nodered service is running and someone uses a run nodered script? I would vote for removing one of those options sop it is clear how to use nodered as service for everest sil
• Documentation: The README.md is way to big. It's contents + REQUIREMENTS.md should be moved to the main documentation. The README should only include hints about what is inside this repository and roughly how to work with the repos contents and a link to the main documentation. So the usage of devcontainer tooling belongs to main documentation. I would suggest to split the devcontainer docs into the following chunks in the new upcoming docs structure:
  • Tutorial: How to setup first devcontainer/dev environment and start sil or so
  • How to guide: A bit advanced features as starting/stopping services using other profiles, using environemt variables, all the available commands
  • Explanation: How does the devcontainer works: devcontainer vs docker compose, ports, all the stuff in the background which a developer would need to work on the tooling
  • Reference: The Requirements could be protocolled here as reference, but could also be omitted in my opinion. We only talked about F1-F7
• The old documentation should be removed/adapted
• Documentation should fit to the general getting started guide. Either it should replace it, extend it or link against each other
• Are there already related PRs in the corresping repositories I have overseen?

If you have any questions on my comments we also can set up a call to discuss it

[andistorm]

Please add proper title and description to this PR

[andistorm]

🐧 While still some aspects need a bit of rework this PR can be merged and further changes can be done in the monorepo