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

Initiate the NextGraph server #1262

Open
srosset81 opened this issue May 29, 2024 · 2 comments
Open

Initiate the NextGraph server #1262

srosset81 opened this issue May 29, 2024 · 2 comments

Comments

@srosset81
Copy link
Contributor

srosset81 commented May 29, 2024

Ideally, create a Dockerfile that will bootstrap all NextGraph operations on launch. But this may be difficult as a lot of keys must be generated, and saved in .env variables. So this will probably be a two-step process: generate the keys, save them on the .env file, and then launch the server.

It would be great if the master key required to launch the server was not saved as an env variable, but was required on every launch. This would mean only the administrator who has this key can access the server and decrypt the content of the Pods.

@nikoPLP
Copy link
Contributor

nikoPLP commented May 29, 2024

you have the option in nextgraph to not save the master key (remove the --save-key from the command line arguments). the key will be displayed in the standard output at the first launch. Then you have to pass the key at every start with the argument --key. if ngd runs in a docker, we will have to find a way to pass the key to the docker container. I am thinking of implementing a feature that will make the ngd server that lacks a key, to listen on its port (1440) and wait for the key there. and only start the rest of the server once the key is supplied. this way, an admin can connect to the server and send the key. this feature is not implemented yet on my side but i can do it.

@srosset81
Copy link
Contributor Author

I am thinking of implementing a feature that will make the ngd server that lacks a key, to listen on its port (1440) and wait for the key there. and only start the rest of the server once the key is supplied. this way, an admin can connect to the server and send the key. this feature is not implemented yet on my side but i can do it.

That would be great !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants