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
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.
Save the password. It is required to launch the server
Create a "settings" dataset.
This will return an UUID, that must be saved somewhere (env variable ?)
Tool to migrate the settings dataset (ActivityPods)
In the settings dataset, we will save save the WebID, the dataset UUID and the WebID document UUID (that's the only document that doesn't use a UUID)
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: