You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/server-docs/setup/truenas-scale.md
+85-14Lines changed: 85 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,46 @@ Since the release of TrueNAS Scale version 24.10 (Electric Eel), Docker is now u
13
13
14
14
- a running TrueNAS Scale Server (version 24.10 or newer)
15
15
- an understanding of storage/users in TrueNAS Scale
16
-
- a docker-compose.yml file that you have already configured by following the [Using Docker Compose](docker-compose.md) and [Configuration](/docs/server-docs/configuration.md) pages.
16
+
- a docker-compose.yml file. See below for additional information.
17
+
18
+
### Docker-Compose.yml - what do I need to do?
19
+
20
+
In current versions of TrueNAS Scale, you can create a custom app by providing a docker-compose.yml configuration. You do this entirely within TrueNAS Scale; No additional programs are needed. However, it can be beneficial to configure everything in a text editor first, and then copy/paste it into TrueNAS during the actual App creation process. This allows you to more easily make the necessary changes as well as save a copy of your config outside of TrueNAS. Once everything is prepared, you simply copy the config into TrueNAS Scale and it does the rest! This is explained later on in the documentation.
21
+
22
+
To start, open up a text editor - anything will do, but Notepad++ is an excellent choice as it maintains proper indentation/spacing.
23
+
24
+
Next, copy this example into your text editor. You will make changes to this later on.
25
+
26
+
```yaml
27
+
services:
28
+
gamevault-backend:
29
+
image: phalcode/gamevault-backend:latest
30
+
restart: unless-stopped
31
+
environment:
32
+
DB_HOST: db
33
+
DB_USERNAME: gamevault
34
+
DB_PASSWORD: YOURPASSWORDHERE
35
+
volumes:
36
+
# Mount the folder where your games are
37
+
- /your/games/folder:/files
38
+
# Mount the folder where GameVault should store its media
39
+
- /your/media/folder:/media
40
+
ports:
41
+
- 8080:8080/tcp
42
+
db:
43
+
image: postgres:16
44
+
restart: unless-stopped
45
+
environment:
46
+
POSTGRES_USER: gamevault
47
+
POSTGRES_PASSWORD: YOURPASSWORDHERE
48
+
POSTGRES_DB: gamevault
49
+
volumes:
50
+
# Mount the folder where your PostgreSQL database files should land
51
+
- /your/database/folder:/var/lib/postgresql/data
52
+
53
+
```
54
+
55
+
You should also take a moment to read the [Configuration](/docs/server-docs/configuration.md) page, as it contains additional options that can be configured if desired. This guide will cover only the options that are needed for a basic setup, but you may want to add more for your particular needs.
17
56
18
57
## Step 1: Log in to your TrueNAS Scale Dashboard
19
58
@@ -25,14 +64,18 @@ Since the release of TrueNAS Scale version 24.10 (Electric Eel), Docker is now u
25
64
26
65
By default, GameVault will try to run as user ID 1000 and group ID 1000. However, this will not normally work in TrueNAS Scale. Instead, you will need to specify which user/group ID GameVault should use. You can create a new user, or use an existing one!
27
66
28
-
In your docker-compose.yml, file add the PUID and PGID variables to the gamevault-backend environment variables.
67
+
In your docker-compose.yml file, add the PUID and PGID variables to the gamevault-backend environment variables.
29
68
For simplicity, we will use the "apps" user/group which is built-in to TrueNAS Scale and uses ID number 568 for both PUID and PGID.
30
69
31
70
```plaintext
32
71
PUID: 568
33
72
PGID: 568
34
73
```
35
74
75
+
An example of the finished config is available below under "Step 2a".
76
+
77
+
78
+
36
79
**Configuring Storage**
37
80
38
81
GameVault expects three directories:
@@ -44,6 +87,9 @@ GameVault expects three directories:
44
87
These directories will need to be created before you can deploy GameVault on your TrueNAS Scale server.
45
88
If you have not yet done so, create the needed directories before continuing, and ensure your chosen user has read/write access to all three of the directories.
46
89
90
+
An example of the finished config is available below under "Step 2a"
91
+
92
+
47
93
## Step 2a: Setting your GameVault Admin user
48
94
49
95
You can specify a username that will be given the Admin role upon registration in GameVault. Add the following variable to your docker-compose.yml file under the gamevault-backend environment variables. Set it to your desired GameVault username, and your account will be given the Admin role once you register!
@@ -62,12 +108,12 @@ services:
62
108
image: phalcode/gamevault-backend:latest
63
109
restart: unless-stopped
64
110
environment:
65
-
PUID: 568
66
-
PGID: 568
67
-
SERVER_ADMIN_USERNAME: YourUsernameHere
111
+
PUID: 568#568 is the built in "apps" user for TrueNAS Scale
112
+
PGID: 568#568 is the built in "apps" user for TrueNAS Scale
113
+
SERVER_ADMIN_USERNAME: YourUsernameHere#You will need to register this user after everything is running.
68
114
DB_HOST: db
69
115
DB_USERNAME: gamevault
70
-
DB_PASSWORD: YOURPASSWORDHERE
116
+
DB_PASSWORD: YOURPASSWORDHERE#This is not your admin user's password - this is the database password
71
117
volumes:
72
118
# Mount the folder where your games are
73
119
- /mnt/yourgames:/files
@@ -80,32 +126,37 @@ services:
80
126
restart: unless-stopped
81
127
environment:
82
128
POSTGRES_USER: gamevault
83
-
POSTGRES_PASSWORD: YOURPASSWORDHERE
129
+
POSTGRES_PASSWORD: YOURPASSWORDHERE#This is not your admin user's password - this is the database password
84
130
POSTGRES_DB: gamevault
85
131
volumes:
86
132
# Mount the folder where your PostgreSQL database files should land
@@ -155,8 +224,10 @@ You will see the previous number of log lines up to the number you entered, and
155
224
156
225
### Troubleshooting
157
226
158
-
If you recieve any errors while trying to save your GameVault configuration, be sure that all indents/spacing is correct YAML syntax.
227
+
If you receive any errors while trying to save your GameVault configuration, be sure that all indents/spacing is correct YAML syntax.
159
228
You can try a few things to ensure proper formatting:
160
229
161
230
- Use a text editor that maintains indents properly, such as Notepad++
162
231
- Copy the example docker-compose.yml file from above, paste it directly into the configuration window, and add your changes directly. This can help ensure consistent formatting.
232
+
- Ensure your server URL is correct and formatted properly. Example: `http://192.168.0.240:8080`
0 commit comments