Docs for docker not quite alright about actual-server HOT 8 CLOSED

Hi!

• Here’s an updated docker-compose.yml file that unfortunately hasn’t been merged yet but does have the correct setup for pulling down the prebuilt container and mounting in a volume for data: https://github.com/actualbudget/actual-server/blob/jed/update-docker-compose/docker-compose.yml
• The docs in activating HTTPS should work for Docker too. Specifically, you should be able to generate the .key and .crt files using the methods suggested in the doc page. Then, put those files in the Actual data directory. Then you can set up either a config.json or the environment variables to point to those files. (Now that I write this up, I agree that there are some steps in there that should be added to the docs)

from actual-server.

I have offline and online backups already configured for a different directory for personal important files, so I thought I'd link the user-files directory to one in that folder.

I don’t think that would work well with Docker — Actual would see the symlink, but would not be able to access the directory it points to, I believe. Your best bet would be to directly mount the backed-up directory to /data (e.g. /path/to/backed-up/actual:/data). (It‘s worth backing up the server-files directory since it has your server password and important information about the list of files)

from actual-server.

Backing up those should be enough! (But I’d recommend double-checking before you delete anything that things are working ok)

Also, if you have your budget downloaded in your browser you can log into the server again and reupload the budget if it gets lost somehow.

from actual-server.

right, I had forgotten about simply exporting the budget also 🤣

(edit) and done! \o/

from actual-server.

nice! Thank you very much, @j-f1 <3

Generated and put the selfhosted keys on server-data:

Modified the docker-compose.yml:

version: "3"
services:
  actual_server:
    container_name: actual_server
    #build:
    #  context: ./
    #  dockerfile: Dockerfile
    image: jlongster/actual-server:latest-alpine
    ports:
      - "5006:5006"
    environment:
      - ACTUAL_SERVER_FILES=/data/server-files
      - ACTUAL_USER_FILES=/data/user-files
      - ACTUAL_HTTPS_KEY=/data/selfhost.key
      - ACTUAL_HTTPS_CERT=/data/selfhost.crt
    volumes:
      - ./server-data:/data
    restart: unless-stopped

One bad thing I noticed is that I can't create/link user-files directory. If I do that, docker-compose up will exit in error:

$ sudo docker-compose --env-file .env up
Creating actual_server ... done
Attaching to actual_server
actual_server    | Error starting app: Error: EEXIST: file already exists, mkdir '/data/user-files'
actual_server    |     at Object.mkdirSync (node:fs:1395:3)
actual_server    |     at run (file:///app/src/app.js:56:8)
actual_server    |     at file:///app/app.js:3:1
actual_server    |     at ModuleJob.run (node:internal/modules/esm/module_job:194:25) {
actual_server    |   errno: -17,
actual_server    |   syscall: 'mkdir',
actual_server    |   code: 'EEXIST',
actual_server    |   path: '/data/user-files'
actual_server    | }

But, other than that little hiccup, it's up and running <3

(edit)
next step, for tomorrow, is make it come up on boot (this old thing reboots sometimes) and start using it to get a feel of the land! gnight!

from actual-server.

One bad thing I noticed is that I can't create/link user-files directory.

Looking at the error message and underlying code, it seems like the server doesn’t see the user-files directory and tries to create it. What specifically were you trying to do there that didn’t work?

But, other than that little hiccup, it's up and running <3

🎉

next step, for tomorrow, is make it come up on boot (this old thing reboots sometimes) and start using it to get a feel of the land! gnight!

Have fun! Good night from my end too!

from actual-server.

One bad thing I noticed is that I can't create/link user-files directory.

Looking at the error message and underlying code, it seems like the server doesn’t see the user-files directory and tries to create it. What specifically were you trying to do there that didn’t work?

I have offline and online backups already configured for a different directory for personal important files, so I thought I'd link the user-files directory to one in that folder.

from actual-server.

I think I may have thought of just testing Actual, and then started using it for real... But back then I started the container back then as ...

and forgotten to map the volume. Now, the update release note says about moving from jlongster/actual-server to actualbudget/actual-server and when I run docker ps I see I'm running the old one...

backing up /data/server-files and /data/user-files is enough, or is there something else I need to backup before killing the old container and running the new one with the backed up files mapped to it?

from actual-server.