Privacy-first password manager with built-in email aliasing. Fully encrypted and self-hostable.
Update install docs (#2234)
Leendert de Borstfdd1818eb13f
diff --git a/docs/docs/installation/docker-compose/index.md b/docs/docs/installation/docker-compose/index.mdindex 9658a96a9..1fe64a56b 100644--- a/docs/docs/installation/docker-compose/index.md+++ b/docs/docs/installation/docker-compose/index.md@@ -37,18 +37,18 @@ services:volumes:- ./database:/database- ./logs:/logs- - ./secrets:/secrets+ - ./secrets:${SECRETS_PATH:-/secrets}- ./certificates:/certificatesenvironment:- HOSTNAME: "localhost"- PUBLIC_REGISTRATION_ENABLED: "true"- IP_LOGGING_ENABLED: "true"FORCE_HTTPS_REDIRECT: "false"- SUPPORT_EMAIL: ""- PRIVATE_EMAIL_DOMAINS: ""- SMTP_TLS_ENABLED: "false"+ PUBLIC_REGISTRATION_ENABLED: "true"```++:::tip+For a full overview of all available environment variables and what they do, see [.env.example](https://github.com/aliasvault/aliasvault/blob/main/.env.example) in the AliasVault repository.+:::+3. Run `docker compose up -d` to start the container.4. After the container has started, AliasVault should now be running. You can access it at:diff --git a/install.sh b/install.shindex 16180e8f6..2facc4ca2 100755--- a/install.sh+++ b/install.sh@@ -2361,7 +2361,6 @@ configure_letsencrypt() {fi# Get contact email for Let's Encrypt- SUPPORT_EMAIL=$(grep "^SUPPORT_EMAIL=" "$ENV_FILE" | cut -d '=' -f2)LETSENCRYPT_EMAIL=""while true; do@@ -3575,12 +3574,6 @@ handle_trusted_proxies_configuration() {check_and_populate_env() {printf "${CYAN}ℹ Checking .env values...${NC} ${GREEN}✓${NC}\n"- # SUPPORT_EMAIL- if ! grep -q "^SUPPORT_EMAIL=" "$ENV_FILE"; then- read -p "Enter server admin support email address that is shown on contact page (optional, press Enter to skip): " SUPPORT_EMAIL- update_env_var "SUPPORT_EMAIL" "$SUPPORT_EMAIL"- fi-# JWT_KEYif [ ! -f "${SECRETS_DIR}/jwt_key" ] || [ -z "$(cat "${SECRETS_DIR}/jwt_key" 2>/dev/null)" ]; thenJWT_KEY=$(openssl rand -base64 32)