Zulip via docker container on Synology NAS. Broken site and links. #493
Description
Hello
I am looking for help with Zulip ARM installation via docker container on Synology NAS.
I run a NAS in Tailscale network. No access outside VPN. We use server IP.
I have there a Gitea server, it works fine under port :3000. Now, wanted to add Zulip for communications.
I managed to install Zulip using https://github.com/zulip/docker-zulip. Changing image to immortalvision/zulip-arm:10.0-0 for ARM architecture, ports 5010 for http, no HTTPS. All installed without any errors. But when I type its adress and port in browser, it opens the website without any style/images. Once a while it changes to proper looking site with internal error message.
I appreciate any help. Thanks
PS. Passwords are there, just changed to - for posting. Added screenshots of Zulip, containers, and Gitea working on same NAS.
Here is my docker-compose.yml:
services:
database:
image: "zulip/zulip-postgresql:14"
restart: unless-stopped
environment:
POSTGRES_DB: "zulip"
POSTGRES_USER: "zulip"
## Note that you need to do a manual `ALTER ROLE` query if you
## change this on a system after booting the postgres container
## the first time on a host. Instructions are available in README.md.
POSTGRES_PASSWORD: "-"
volumes:
- "postgresql-14:/var/lib/postgresql/data:rw"
memcached:
image: "memcached:alpine"
restart: unless-stopped
command:
- "sh"
- "-euc"
- |
echo 'mech_list: plain' > "$$SASL_CONF_PATH"
echo "zulip@$$HOSTNAME:$$MEMCACHED_PASSWORD" > "$$MEMCACHED_SASL_PWDB"
echo "zulip@localhost:$$MEMCACHED_PASSWORD" >> "$$MEMCACHED_SASL_PWDB"
exec memcached -S
environment:
SASL_CONF_PATH: "/home/memcache/memcached.conf"
MEMCACHED_SASL_PWDB: "/home/memcache/memcached-sasl-db"
MEMCACHED_PASSWORD: "-"
rabbitmq:
image: "rabbitmq:4.0.7"
restart: unless-stopped
environment:
RABBITMQ_DEFAULT_USER: "zulip"
RABBITMQ_DEFAULT_PASS: "-"
volumes:
- "rabbitmq:/var/lib/rabbitmq:rw"
redis:
image: "redis:alpine"
restart: unless-stopped
command:
- "sh"
- "-euc"
- |
echo "requirepass '$$REDIS_PASSWORD'" > /etc/redis.conf
exec redis-server /etc/redis.conf
environment:
REDIS_PASSWORD: "-"
volumes:
- "redis:/data:rw"
zulip:
image: "immortalvision/zulip-arm:10.1-0"
restart: unless-stopped
build:
context: .
args:
## Change these if you want to build zulip from a different repo/branch
ZULIP_GIT_URL: https://github.com/zulip/zulip.git
ZULIP_GIT_REF: "10.1"
## Set this up if you plan to use your own CA certificate bundle for building
# CUSTOM_CA_CERTIFICATES:
ports:
- "5010:80"
- "5011:443"
environment:
## See https://github.com/zulip/docker-zulip#configuration for
## details on this section and how to discover the many
## additional settings that are supported here.
DISABLE_HTTPS: "True"
DB_HOST: "database"
DB_HOST_PORT: "5432"
DB_USER: "zulip"
SSL_CERTIFICATE_GENERATION: "self-signed"
SETTING_MEMCACHED_LOCATION: "memcached:11211"
SETTING_RABBITMQ_HOST: "rabbitmq"
SETTING_REDIS_HOST: "redis"
SECRETS_email_password: "123456789"
## These should match RABBITMQ_DEFAULT_PASS, POSTGRES_PASSWORD,
## MEMCACHED_PASSWORD, and REDIS_PASSWORD above.
SECRETS_rabbitmq_password: "-"
SECRETS_postgres_password: "-"
SECRETS_memcached_password: "-"
SECRETS_redis_password: "-"
SECRETS_secret_key: "-"
SETTING_EXTERNAL_HOST: "100.91.148.1"
SETTING_ZULIP_ADMINISTRATOR: "-"
SETTING_EMAIL_HOST: "" # e.g. smtp.example.com
SETTING_EMAIL_HOST_USER: "[email protected]"
SETTING_EMAIL_PORT: "587"
## It seems that the email server needs to use ssl or tls and can't be used without it
SETTING_EMAIL_USE_SSL: "False"
SETTING_EMAIL_USE_TLS: "True"
ZULIP_AUTH_BACKENDS: "EmailAuthBackend"
## Uncomment this when configuring the mobile push notifications service
# SETTING_ZULIP_SERVICE_PUSH_NOTIFICATIONS: "True"
# SETTING_ZULIP_SERVICE_SUBMIT_USAGE_STATISTICS: "True"
## If you're using a reverse proxy, you'll want to provide the
## comma-separated set of IP addresses to trust here.
# LOADBALANCER_IPS: "",
## By default, files uploaded by users and profile pictures are
## stored directly on the Zulip server. You can configure files
## to be stored in Amazon S3 or a compatible data store
## here. See docs at:
##
## https://zulip.readthedocs.io/en/latest/production/upload-backends.html
##
## If you want to use the S3 backend, you must set
## SETTING_LOCAL_UPLOADS_DIR to None as well as configuring the
## other fields.
# SETTING_LOCAL_UPLOADS_DIR: "None"
# SETTING_S3_AUTH_UPLOADS_BUCKET: ""
# SETTING_S3_AVATAR_BUCKET: ""
# SETTING_S3_ENDPOINT_URL: "None"
# SETTING_S3_REGION: "None"
volumes:
- "zulip:/data:rw"
ulimits:
nofile:
soft: 1000000
hard: 1048576
volumes:
zulip:
postgresql-14:
rabbitmq:
redis: