-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlitefs.yml
62 lines (54 loc) · 2.16 KB
/
litefs.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
# The fuse section describes settings for the FUSE file system. This file system
# is used as a thin layer between the SQLite client in your application and the
# storage on disk. It intercepts disk writes to determine transaction boundaries
# so that those transactions can be saved and shipped to replicas.
fuse:
dir: "/litefs"
# The data section describes settings for the internal LiteFS storage. We'll
# mount a volume to the data directory so it can be persisted across restarts.
# However, this data should not be accessed directly by the user application.
data:
dir: "/var/lib/litefs"
# This flag ensure that LiteFS continues to run if there is an issue on starup.
# It makes it easy to ssh in and debug any issues you might be having rather
# than continually restarting on initialization failure.
exit-on-error: false
# This section defines settings for the option HTTP proxy.
# This proxy can handle primary forwarding & replica consistency
# for applications that use a single SQLite database.
# proxy:
# addr: ":8080"
# target: "localhost:8081"
# db: "clickr.sqlite3"
# passthrough:
# - "/assets/*"
# - "/fonts/*"
# - "/images/*"
# - "/favicon.ico"
# - "/robots.txt"
# - "/live/websocket"
# This section defines a list of commands to run after LiteFS has connected
# and sync'd with the cluster. You can run multiple commands but LiteFS expects
# the last command to be long-running (e.g. an application server). When the
# last command exits, LiteFS is shut down.
exec:
- cmd: "/app/bin/migrate"
if-candidate: true
- cmd: "/app/bin/server"
# The lease section specifies how the cluster will be managed. We're using the
# "consul" lease type so that our application can dynamically change the primary.
#
# These environment variables will be available in your Fly.io application.
# lease:
# type: "consul"
# advertise-url: "http://${HOSTNAME}.vm.${FLY_APP_NAME}.internal:20202"
# candidate: ${FLY_REGION == PRIMARY_REGION}
# promote: true
# consul:
# url: "${FLY_CONSUL_URL}"
# key: "litefs/${FLY_APP_NAME}-v16"
# Static for now (single node)
lease:
type: "static"
advertise-url: "http://primary:20202"
candidate: true