Add Editor Integration and WSL Configuration pages - #136
Merged
Merged
Conversation
The biggest content gap versus general "Linux dev box on WSL" guides was editor integration: nothing covered VS Code Remote-WSL, PhpStorm's WSL interpreter, or Xdebug (which the playbook doesn't install). Filesystem placement/performance, .wslconfig tuning, and backup/ portability (wsl --export/--import) were similarly absent. - Add docs/book/v2/editor-integration.md: VS Code Remote-WSL (code .), PhpStorm WSL interpreter setup, Xdebug install + config for both editors, and PHPUnit runner setup. - Add docs/book/v2/wsl-configuration.md: why projects should live in the WSL filesystem rather than /mnt/c, opening a WSL project from Windows (\\wsl.localhost, explorer.exe .), .wslconfig tuning (memory/CPU/swap/vmIdleTimeout/mirrored networking), and wsl --export/--import as the non-destructive alternative to the already-documented --unregister. - Wire both into mkdocs.yml's v2 nav, between Virtualhosts and FAQ.
arhimede
reviewed
Sep 24, 2026
Signed-off-by: bidi <bidi@apidemia.com>
arhimede
approved these changes
Sep 25, 2026
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
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.
editor integration: nothing covered VS Code Remote-WSL, PhpStorm's WSL
interpreter, or Xdebug (which the playbook doesn't install). Resolves WSL: Create Ansible playbook for AlmaLinux 9 #9.
.wslconfigtuning, and backup/portability (
wsl --export/--import) were similarly absent.Resolves Enhanced file structure and added AlmaLinux8 playbooks. #10, testing Almalinux 9 Ansible #11, strange permission issue #12.
docs/book/v2/editor-integration.md: VS Code Remote-WSL (code .),PhpStorm WSL interpreter setup, Xdebug install + config for both
editors, and PHPUnit runner setup.
docs/book/v2/wsl-configuration.md: why projects should live inthe WSL filesystem rather than
/mnt/c, opening a WSL project fromWindows (
\\wsl.localhost,explorer.exe .),.wslconfigtuning(memory/CPU/swap/vmIdleTimeout/mirrored networking), and
wsl --export/--importas the non-destructive alternative to thealready-documented
--unregister.mkdocs.yml's v2 nav, between Virtualhosts and FAQ.