Where Does Juicity Store Its Config?
Juicity server reads a JSON config you pass with -c, conventionally kept at /etc/juicity/server.json.
Last updated
Juicity takes its config as a JSON file on the command line. There is no fixed registry or database. You run juicity-server with -c pointing at your file. Docker setups conventionally mount it at /etc/juicity/server.json.
The file holds listen address, users, certificates and congestion control. Treat certs as part of the config. Moving the JSON without the key pair leaves a server that starts and accepts nothing.
Where Juicity stores this, by platform
/etc/juicity/server.json (path passed with -c)
Users, certs, keys and congestion control in JSON. Pass with juicity-server run -c. Docker convention mounts host config to /etc/juicity/server.json.
Frequently asked questions
How do I move a Juicity server?
Copy the JSON plus certificate and key to the new host, keeping the same paths or updating the fields. Restart the service and re-export a share link to confirm. Keep permissions tight on the key.
Juicity ignores my config. What is wrong?
Run the server with an explicit -c path and check the file is valid JSON. Docker users must mount the file into the container. Mismatched cert paths are the usual culprit.
Notice an outdated path? Let us know.