DevContainers Integration #9536
Unanswered
mbussolotto
asked this question in
Devel
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
During Hackweek, I worked on adding Dev Containers to both Uyuni and Uyuni Tools. For Uyuni Tools, the PR has already been merged, and you can find the wiki page here: https://github.com/uyuni-project/uyuni-tools/wiki/Working-with-the-Uyuni-Tools-Project-Using-DevContainers.
For Uyuni, the PR still needs a review: #9496. The wiki for this can be found here: https://github.com/uyuni-project/uyuni/wiki/Working-with--Uyuni-Project-Using-DevContainers.
The main difference is that the IDE configuration is now part of the code (not in the .gitignore), so most (if not all) of this wiki might become outdated: https://github.com/uyuni-project/uyuni/wiki#java-ides. Another benefit is that, by having the configuration in the code, we will all have the same working setup.
In the future, Dev Containers might become the only option for setting up a development environment. However, it is important that we don’t break current compatibility or compromise future compatibility for those who prefer not to switch to Dev Containers and want to continue using the traditional development setup.
In the future, the idea is supporting new IDEs and languages (e.g., Python, JavaScript) by adding configurations for them. I'd like to hear you opinion about dev containers and IDE configuration.
Thanks a lot in advance!
Beta Was this translation helpful? Give feedback.
All reactions