Updates

.dockerignore

 node_modules
+user-files
+server-files

.gitignore

@@ -7,3 +7,4 @@ supervise
 bin/large-sync-data.txt
 user-files
 server-files
+fly.toml
\ No newline at end of file

Dockerfile

@@ -10,5 +10,8 @@ ENV NODE_ENV=production
 ADD . .
 
 RUN yarn install --production
+RUN mkdir ./server-files
+RUN mkdir ./user-files
+RUN cp ./sql/default-account.sqlite ./server-files/account.sqlite
 
 CMD ["yarn", "start"]
\ No newline at end of file

README.md

@@ -28,7 +28,7 @@ You should deploy your server so it's always running. We recommend [fly.io](http
 
 Next, [install the `flyctl`](https://fly.io/docs/flyctl/installing/) utility. Run `flyctl auth login` to sign into your account.
 
-Open `fly.toml` and customize the app name on the first line of the file.
+Copy `fly.template.toml` to `fly.toml`. Open `fly.toml` and customize the app name on the first line of the file.
 
 Now, run `flyctl launch` from `actual-server`. You should have a running app now!
 
@@ -36,6 +36,28 @@ Whenever you want to update Actual, update the versions of `@actual-app/api` and
 
 **Note:** if you don't want to use fly, we still provide a `Dockerfile` to build the app so it should work anywhere that can compile a docker image.
 
+### Persisting server data
+
+One problem with the above setup is every time you deploy, it will wipe away all the data on the server. You'll need to bootstrap the instance again and upload your files.
+
+Let's move the data somewhere that persists. With [fly.io](https://fly.io) we can create a [volume](https://fly.io/docs/reference/volumes/). Run this command:
+
+```
+flyctl volumes create actual_data
+```
+
+Now we need to tell Actual to use this volume. Add this in `fly.toml`:
+
+```
+[mounts]
+  source="actual_data"
+  destination="/data"
+```
+
+That's it! Actual will automatically check if the `/data` directory exists and use it automatically.
+
+_You can also configure the data dir with the `ACTUAL_USER_FILES` environment variable._
+
 ## Configuring the server URL
 
 The Actual app is totally separate from the server. In this project, they happen to both be served by the same server, but the app doesn't know where the server lives.

fly.template.toml

+app = "%NAME%"
+
+kill_signal = "SIGINT"
+kill_timeout = 5
+processes = []
+
+[env]
+  PORT = "8080"
+
+[experimental]
+  allowed_public_ports = []
+  auto_rollback = true
+
+[[services]]
+  http_checks = []
+  internal_port = 5006
+  processes = ["app"]
+  protocol = "tcp"
+  script_checks = []
+
+  [services.concurrency]
+    hard_limit = 25
+    soft_limit = 20
+    type = "connections"
+
+  [[services.ports]]
+    force_https = true
+    handlers = ["http"]
+    port = 80
+
+  [[services.ports]]
+    handlers = ["tls", "http"]
+    port = 443
+
+  [[services.tcp_checks]]
+    grace_period = "1s"
+    interval = "15s"
+    restart_limit = 0
+    timeout = "2s"

fly.toml

-app = "%NAME%"
+app = "actual-server"
 
 kill_signal = "SIGINT"
 kill_timeout = 5
@@ -11,6 +11,10 @@ processes = []
   allowed_public_ports = []
   auto_rollback = true
 
+[mounts]
+  source="actual_data"
+  destination="/data"
+
 [[services]]
   http_checks = []
   internal_port = 5006

load-config.js

@@ -2,10 +2,12 @@ let config;
 try {
   config = require('./config');
 } catch (e) {
+  let fs = require('fs');
+
   config = {
     mode: 'development',
     port: 5006,
-    files: './user-files'
+    files: fs.existsSync('/data') ? '/data' : './user-files'
   };
 }