Running extension inside a VSCode devcontainer

[Bidski]

Question

When using und inside a docker container (or a devcontainer with VSCode) it is needed to call -setlicensecode and then, eventually, -deregisterlicensecode before exiting the container. Is it possible to provide the license code to this extension (or to userver) so that the license code can be registered and deregistered appropriately?

[RobbyCBennett]

That's a great idea. Yes, this is possible. I would implement this as a setting in the VS Code extension which is sent to userver.

[Bidski]

Is there any documentation for userver that explains how to set the license code?

[RobbyCBennett]

I have just added it into the README.md file.

[Bidski]

I was more referring to documentation on how to set the licence code via userver. I'm interested in getting this issue resolved quickly so I can start using this extension

[RobbyCBennett]

That hasn't been implemented yet. For Docker, I would use und. Perhaps a good automated solution to run the und would be with .bash_logout and .bash_login files if you are using Bash in your Docker image. Another alternative is a Docker compose service entrypoint that runs an entrypoint script which can execute a command at startup and shutdown.

[Bidski]

Is there any progress on this?

[RobbyCBennett]

There is not progress on this issue. I will comment here if there is progress on updating the plugin for license codes.

In the meantime, please try automating und -setlicensecode and und -deregisterlicensecode.

• Automating it with .bash_logout and .bash_login files or...
• Try automating it with docker-compose.yml

[Bidski]

While the workaround you suggest should work in general I already have other workflows setup where this will potentially clash and result in me attempting to checkout my license multiple times. Also, the workarounds you suggest are not fool-proof, it is possible for the container to quit without it deregistering the license code and this is something that I am specifically trying to avoid. My ideal solution would be for this extension (or userver) registering the license code, performing its actions, then deregistering the license code to prevent the possibility of the license code being left registered

[RobbyCBennett]

Okay. I understand that my proposed workaround doesn't seem to be a valid solution.