You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If based on working directory, can't customise as the working directory is always the same (well, by default)
Can't use some file (e.g. "user-mrodo_devcontainer") as these have to be recreated in the devcontainer every time
This is really a bit of a mess-up, as the environment is supposed to be "standardised" and here it isn't
Possible solutions
Make settings depend on an environment variable
This will have to be set up in the Docker file
In this case, people would have to clone the repository, create a new docker file and then rechoose their directory
If they want to rechoose the directory
But depending on the project structure, they may have to.
Multiple devcontainer files would help
VSC does not seem able to make use of that yet, but it seems like it is on track to do so.
This would happen either via an extends property (that just adds keys to an existing devcontainer.json file) or a ref property (that is more sophisticated in some way).
I think we're going to call this PROJR_SYSTEM_ID. Better than PROJR_USER as this isn't about a specific user necessarily, it's actually about the system. Also better than PROJR_WORKING_DIRECTORY as this need not be a directory.
We've already made settings depend on the environment variable, so this is actually done. What we need to do is quick and just rename it to PROJR_SYSTEM_ID.
Issues
If based on working directory, can't customise as the working directory is always the same (well, by default)
Can't use some file (e.g. "user-mrodo_devcontainer") as these have to be recreated in the devcontainer every time
This is really a bit of a mess-up, as the environment is supposed to be "standardised" and here it isn't
Possible solutions
The text was updated successfully, but these errors were encountered: