This setup is based on the pryv.io-1.9.0-single-node template files using backloop.dev domain and SSL certificates.
This has been tested on ubuntu 22.04 with docker running as root.
## Prerequistory
1- Docker & Docker-compose
2- Access rights and Pryv.io Entreprise edition docker container repository (look for pryv-docker-key.json)
3- Set environment var PRYV_CONF_ROOT
to match the directory with this file.
This can be done with the following command from this directory.
export PRYV_CONF_ROOT=`pwd`
4- (optional) Node.js if you want to automatically download the SSL certificates
- SSL certificates
- AUTO (with node.js installed): Go in
config-leader/data/singlenode/nginx/conf/secret
and runBACKLOOP_DEV_CERTS_DIR=./ npx -p backloop.dev backloop.dev-update
- Manualy: Download the certificates files manually from backloop.dev and place them in
config-leader/data/singlenode/nginx/conf/secret
- Renew SSL certificates when they expire after 2-3 months
- Follow the INSTALL.md or UPDATE.md files and skip steps where domain, dns .. have already been configured
config_leader
failed on first start because of a git initialization error, it started on the second boot
## What has been done
- set
DOMAIN
=>backloop.dev
- set
SINGLE_MACHINE_IP_ADDRESS
=>127.0.0.1
- set
REGISTER_ADMIN_KEY
=>UnsecureRegisterAdminKey
- set
NAME_SERVER_ENTRIES
todns1.backloop.dev
&dns2.backloop.dev
(should have no effect anyway)
-
replaced
FOLLOWER_SINGLENODE_KEY
withUnsecureFollowerKey
-
Internals:
"internals": {
"SSO_COOKIE_SIGN_SECRET": "UnsecureSSOCookieSecret",
"FILES_READ_TOKEN_SECRET": "UnsecurereadTokenSecret",
"CORE_SYSTEM_KEY": "UnsecureCoreSystemKey",
"CORE_MAIL_KEY": "UnsecureMailKey",
"REGISTER_SYSTEM_KEY_1": "UnsecureRegisterSysemKey1"
},
from: export PRYV_CONF_ROOT=/var/pryv
to: export PRYV_CONF_ROOT="${PRYV_CONF_ROOT:=/var/pryv}"
in file /Users/perki/wActiv/pryv.io-1.9.0-single-node-local/config-follower/config-follower.yml
set services / config-follower / volumes:
- /home/docker/.docker/config.json:${HOME}/.docker/config.json
added HOME
to environment
- Contribution are welcome
- It would be nice to be able to run it in the "user-space" not as "root"