Open SavvasMohito opened 1 week ago
I think changing devcontainer.json
to include
{ "mounts": [ "source=${localEnv:HOME}${localEnv:USERPROFILE}/.supermaven,target=/home/vscode/.supermaven,type=bind,consistency=cached" ] }
should ensure that the .supermaven
credentials are accessible inside the container
I think changing
devcontainer.json
to include{ "mounts": [ "source=${localEnv:HOME}${localEnv:USERPROFILE}/.supermaven,target=/home/vscode/.supermaven,type=bind,consistency=cached" ] }
should ensure that the.supermaven
credentials are accessible inside the container
Thanks, this seems to solve the activation issue. Now it is struggling to connect to the server inside the container. I'll investige further, I hope to find a solution.
Inside the devcontainer, I noticed that clicking on the supermaven text on the bottom right opens a menu in vs code but it does not display my email address next to the "log out" option. Doing the same on the host ssh machine (that connects normally) displays my email address.
Inside devcontainer:
On the host ssh machine:
Hello, I have just subscribed to Supermaven Pro and I am trying to get it to work with my VS Code setup. I am currently working in a remote SSH server and the activation works when I go through the process in the SSH machine.
When I launch a VS Code window inside a docker devcontainer, I cannot activate Supermaven Pro. Enabling the free tier works, but activating the pro version via the browser does nothing in vs code. I checked the .supermaven/config.json inside the container and it only includes the link_id. I tried copying the config.json from the SSH machine in the docker container, but it still does not work.
Has anyone else faced the same issue? Any ideas on how to get this working? Thanks in advance.