Feat: Dev Container configuration to simplify local setup #879
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add devcontainer setup for LibreBooking development environment: - Docker Compose configuration with PHP 8.1 and MariaDB 10.6 - Xdebug enabled for debugging support - Composer dependencies auto-installed on container creation - Automatic permission setup for uploads and tpl_c directories - Pre-configured VS Code extensions (PHP Debug, Intelephense, EditorConfig) - Database initialization with test schema This enables consistent development environment across team members and simplifies onboarding for new contributors.
- Added documentation for instructing contribution using devcontainers - Included instructions on using devcontainers without VScode
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following through on PR #876 , I have tested lucs7@03d4f43 per @lucs7 request at #876 (comment).
His code works (and is far more elegant & exhaustive) which is why I think it should be the one to be pushed.
Now I am still new to this contribution thing so I guessed his intention was to add his fork to my fork as a remote, test the code, add documentation and make a PR. Sorry if making a 2nd PR is messy if theres a better way to cooperate between 2 forks i'd be happy to learn it.