Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keys management #117

Open
Dahlgren opened this issue Aug 18, 2018 · 4 comments · May be fixed by #156
Open

Keys management #117

Dahlgren opened this issue Aug 18, 2018 · 4 comments · May be fixed by #156

Comments

@Dahlgren
Copy link
Owner

  • Show all current keys in keys directory
  • Copy (all) keys from mod to keys directory
@Varrkan82
Copy link

Varrkan82 commented Aug 25, 2018

It would be better to create orremove the symbolic links on all keys in mod's "key" directory to server's "keys" directory at mod switching ON or OFF

@Dahlgren
Copy link
Owner Author

Dahlgren commented Aug 26, 2018

I agree, that is probably how it has to work for it to support different keys on multiple different configurations

@Freddo3000
Copy link

Perhaps this could be of use? https://gist.github.com/Freddo3000/a5cd0494f649db75e43611122c9c3f15

I manage keys and mods using that script, where it symlinks the keys in order to keep them up to date.

@Dahlgren
Copy link
Owner Author

Implementing keys management is quite easy. Maintaining virtual server folders across Windows and Linux is not so much fun.

If you want to try it out you can use the git branch feature/virtual-server-folder. I've only tested it on Windows (as it's the annoying platform in terms of symlinks) and it currently requires Node 10+.

It adds an extra burden on Windows as the server binary gets a new path which triggers a new entry in Windows Firewall that must be permitted.

@Dahlgren Dahlgren linked a pull request Apr 13, 2020 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants