Selfhosted

Thank you for the reply. I really enjoyed reading all of the blog posts you have on the site. I really enjoy what you're doing with the project and look forward to becoming a contributing patron soon. I'm genuinely surprised at the polish and well thought out development with so very little support given so far. I had a question regarding performance in Trivalent, but didn't know if I should field that here or in github or possibly somewhere else. If you can let me know, I'd really appreciate it.

Thanks for the details - I'm sure it's intentional that Daylio makes it quite the circus to go through. I'm excited about Journiv in general, so I might switch over once mood tracking is all set. However, it'd still be great to be able to import Daylio as I have around 2,000 entries :)

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!

Amazing, thanks.

ok thanks for the reply. I understand that this would take very much work but I wouldn't be comfortable hosting something with potentially very sensitive data on a remote server where the admins could see the files. Unfortunately hosting on my Raspberry Pi at home isn't possible because of this error when starting the docker containers (which seems to be a Raspberry issue).

What is the difference between your encryption at rest and disk/file system encryption? Would the use case be that someone stealing the server couldn't access the files?