Skip to content

Conversation

@mgajek-cern
Copy link

@mgajek-cern mgajek-cern commented Dec 3, 2025

Closes #623

Launching the local development server within a VS Code devcontainer:

Screenshot 2025-12-03 at 17 46 03

@mgajek-cern mgajek-cern force-pushed the patch-623-devcontainer branch 2 times, most recently from b189623 to 83f8c60 Compare December 3, 2025 17:04
@voetberg
Copy link
Contributor

voetberg commented Dec 4, 2025

Is it possible to add more details instructions on how to set this up in the vscode dev page? Maybe just adding an extra section there with a few lines about how to set up this specific devcontainer.

@voetberg
Copy link
Contributor

voetberg commented Dec 4, 2025

Also notably, the added command failed for me so I'd probably like to debug this with you offline when you get a chance

@mgajek-cern
Copy link
Author

mgajek-cern commented Dec 5, 2025

Is it possible to add more details instructions on how to set this up in the vscode dev page? Maybe just adding an extra section there with a few lines about how to set up this specific devcontainer.

The VS Code dev page focuses solely on the main rucio/rucio repository and doesn't address other repos like documentation, containers or helm-charts. Adopting standardized development environments (devcontainers or similar) across all Rucio repositories would enable one-click setup and remove manual configuration barriers for multi-repo contributors.


We should wait for an agreed-upon approach before implementing this. Otherwise we'll need separate documentation for each repository's setup. For now, I'd suggest only keeping the note in the README.md since it's specific to this repository (rucio/documentation).

@mgajek-cern
Copy link
Author

Also notably, the added command failed for me so I'd probably like to debug this with you offline when you get a chance

Could you share:

  • Error logs/output from the failed command
  • Your system info (OS, Docker version, VS Code version)
  • Which specific command failed

This will help us troubleshoot more efficiently. Feel free to reach out offline whenever works for you.

@mgajek-cern mgajek-cern force-pushed the patch-623-devcontainer branch 2 times, most recently from 817b98a to 60f4ec4 Compare January 16, 2026 13:44
@mgajek-cern mgajek-cern changed the title enhancement: modify devcontainer with Ubuntu 24.04 and required build tools feat(Containerization): Update devcontainer to Ubuntu 24.04 with build tools Jan 16, 2026
@mgajek-cern mgajek-cern force-pushed the patch-623-devcontainer branch from 60f4ec4 to 7e8f688 Compare January 16, 2026 14:12
…d tools

Switch from Debian Bullseye to Ubuntu 24.04 for CI alignment. Install
mdl for markdown linting, Python dependencies from tools/requirements.txt,
pre-commit hooks and yarn dependencies for website build. Add VS Code
markdown linting extension to devcontainer configuration.

Configure port forwarding for Docusaurus dev server on port 3000 to
enable local browser access from host machine. Update README with quick
start information for developers using the devcontainer with IDEs
supporting the devcontainer specification.

Closes: rucio#623
@mgajek-cern mgajek-cern force-pushed the patch-623-devcontainer branch from 7e8f688 to 8d9ea10 Compare January 16, 2026 14:14
@mgajek-cern
Copy link
Author

Since when do we have the pre-commit.ci enabled? Can we address findings in a separate issue?

@voetberg
Copy link
Contributor

Since when do we have the pre-commit.ci enabled? Can we address findings in a separate issue?

As of yesterday lol. Go ahead and rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add required tools for documentation build to devcontainer

2 participants