Add local development standards and guide - #140
Open
johnwatson484 wants to merge 6 commits into
Open
Conversation
johnwatson484
commented
Aug 4, 2026
|
|
||
| Teams must not constrain their local development setup to a specific device or operating system. Deployed services run on Linux, per the [container standards](container_standards.md), and local development should be consistent with that: on Windows, use Windows Subsystem for Linux rather than the native Windows filesystem and tooling; on macOS, use the native environment directly. Both give a Linux-like environment that matches how the service is built and deployed. | ||
|
|
||
| Only work directly on the Windows filesystem when it is unavoidable, for example a technology that does not work through WSL such as .NET Framework. |
Member
Author
There was a problem hiding this comment.
I'm not sure I've worded this in the best way. There are plenty of stuff that we do that will only work on Windows or works far better on Windows like Robotics, Dynamics, Power Platform etc. I could create a bullet list of examples maybe?
I don't want to mislead anyone into doing a load of extra setup work with WSL that doesn't give any value, whilst at the same time discourage using Windows when it brings "baggage" to the team.
Refocus docker_guidance.md on container craft: base images, multi-stage builds, security, and Compose reference. Remove the local development workflow and testing sections that duplicate the local development patterns guide, and drop the principles list now covered by the local development standards. Restore Compose project isolation for CI, which the rewrite had dropped. Standardise on src/ and compose.yaml, and state the env_file plus environment layering consistently in both guides.
johnwatson484
marked this pull request as ready for review
August 7, 2026 11:59
johnwatson484
added a commit
that referenced
this pull request
Aug 7, 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
1 participant
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.
No description provided.