Thanks. I took another look at your documentation and decided to re-install everything. You’re right, I’d used the simple “test” compose script from your site. After a little trial and error, I got everything working properly with this:
services: redis: image: redis:7-alpine container_name: journiv-redis restart: unless-stopped volumes: - /mnt/dietpi_userdata/docker-data/journiv/redis-data:/data command: redis-server --appendonly yes journiv: image: swalabtech/journiv-app:latest container_name: journiv ports: - "8111:8000" environment: - SECRET_KEY=XXX - DOMAIN_NAME=XXX - CELERY_BROKER_URL=redis://redis:6379/0 - CELERY_RESULT_BACKEND=redis://redis:6379/0 - REDIS_URL=redis://redis:6379/0 volumes: - /mnt/dietpi_userdata/docker-data/journiv/data:/data restart: unless-stopped depends_on: - redis celery-worker: image: swalabtech/journiv-app:latest container_name: journiv-celery-worker entrypoint: [] command: ["celery", "-A", "app.core.celery_app", "worker", "--loglevel=info"] environment: - SECRET_KEY=XXX - DOMAIN_NAME=XXX - CELERY_BROKER_URL=redis://redis:6379/0 - CELERY_RESULT_BACKEND=redis://redis:6379/0 - REDIS_URL=redis://redis:6379/0 volumes: - /mnt/dietpi_userdata/docker-data/journiv/data:/data restart: unless-stopped depends_on: - redis - journiv
Exports are working!
rockstar1215@lemmy.world 3 days ago
Nice. You can just follow this doc and it will be smoother. www.journiv.com/docs/installation/docker Celery beat is still missing from the compose. Journiv uses that for scheduled tasks. Also if you like Journiv and plan to use it I will recommend moving to Postgres because that is preferred DB and many upcoming features will utilize pg vector etc.