Skip to content

Commit 03922c5

Browse files
DissBeeAlfagun74
authored andcommitted
Update truenas-scale.md
Updated for clarity. Corrected a few typos.
1 parent 42e9d8b commit 03922c5

1 file changed

Lines changed: 85 additions & 14 deletions

File tree

docs/server-docs/setup/truenas-scale.md

Lines changed: 85 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,46 @@ Since the release of TrueNAS Scale version 24.10 (Electric Eel), Docker is now u
1313

1414
- a running TrueNAS Scale Server (version 24.10 or newer)
1515
- 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.
1756

1857
## Step 1: Log in to your TrueNAS Scale Dashboard
1958

@@ -25,14 +64,18 @@ Since the release of TrueNAS Scale version 24.10 (Electric Eel), Docker is now u
2564

2665
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!
2766

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.
2968
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.
3069

3170
```plaintext
3271
PUID: 568
3372
PGID: 568
3473
```
3574

75+
An example of the finished config is available below under "Step 2a".
76+
77+
78+
3679
**Configuring Storage**
3780

3881
GameVault expects three directories:
@@ -44,6 +87,9 @@ GameVault expects three directories:
4487
These directories will need to be created before you can deploy GameVault on your TrueNAS Scale server.
4588
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.
4689

90+
An example of the finished config is available below under "Step 2a"
91+
92+
4793
## Step 2a: Setting your GameVault Admin user
4894

4995
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:
62108
image: phalcode/gamevault-backend:latest
63109
restart: unless-stopped
64110
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.
68114
DB_HOST: db
69115
DB_USERNAME: gamevault
70-
DB_PASSWORD: YOURPASSWORDHERE
116+
DB_PASSWORD: YOURPASSWORDHERE #This is not your admin user's password - this is the database password
71117
volumes:
72118
# Mount the folder where your games are
73119
- /mnt/yourgames:/files
@@ -80,32 +126,37 @@ services:
80126
restart: unless-stopped
81127
environment:
82128
POSTGRES_USER: gamevault
83-
POSTGRES_PASSWORD: YOURPASSWORDHERE
129+
POSTGRES_PASSWORD: YOURPASSWORDHERE #This is not your admin user's password - this is the database password
84130
POSTGRES_DB: gamevault
85131
volumes:
86132
# Mount the folder where your PostgreSQL database files should land
87133
- /mnt/GameVault/database:/var/lib/postgresql/data
88134
```
89135
136+
You should change the `DB_PASSWORD` and `POSTGRES_PASSWORD` variables to be an actual password instead of "YOURPASSWORDHERE".
137+
138+
You can set this to anything you want, but they both need to be the same password or it will not work.
139+
140+
90141
You are now ready to deploy GameVault!
91142

92-
## Step 3: Navigate to Apps and Disover Page
143+
## Step 3: Navigate to Apps and Discover Page
93144

94145
Go to **apps** -> **discover**
95146

96147
![Scale-EE-Step-3](/img/docs/setup/scale/Scale-EE-Step-3.png)
97148

98149
## Step 4: Select "Install via YAML"
99150

100-
Click the three dot icon next the the "Custom App" button:
151+
Click the three-dot icon next the "Custom App" button:
101152

102153
![Scale-EE-Step-4](/img/docs/setup/scale/Scale-EE-Step-4.png)
103154

104155
Then, select the option to "Install via YAML":
105156

106157
![Scale-EE-Step-4a](/img/docs/setup/scale/Scale-EE-Step-4a.png)
107158

108-
In the pop-out window, enter the name of the custom app: for this example we used "gamevault-backend"
159+
In the pop-out window, enter the name of the custom app. For this example, we used "gamevault-backend"
109160

110161
Then, paste the entire contents of your docker-compose.yml file into the "Custom Config" section:
111162

@@ -119,21 +170,39 @@ The system will automatically do all the setup and return you to the main **Apps
119170

120171
You have now successfully set up your GameVault Server using TrueNAS Scale!
121172

173+
You can access your server using the GameVault client. Use your server's IP address followed by the designated port.
174+
175+
Example: `http://192.168.0.240:8080`
176+
122177
[Click here to continue.](setup.md#what-next)
123178

124179
## Additional Info
125180

181+
### Registering Your Admin User
182+
183+
Once you have the server running, you will need to download/install the GameVault client. It will walk you through the setup process.
184+
185+
Here are a few things to keep in mind during this setup process:
186+
187+
- The server URL should start with "http://" and end with the required port number "8080"
188+
- Example: `http://192.168.0.240:8080`
189+
- Replace the "192.168.0.240" with your TrueNAS server's IP address.
190+
- If you are running other apps, be sure they are not also using port 8080 - this will cause a conflict.
191+
- You can check this by looking at each of your running apps - used ports will show under the "Ports" section of the "Workloads" window.
192+
- If there is a conflict, you will need to change the conflicting app, or GameVault, to use a different port.
193+
- Be sure to register your admin user before you try to login. Use the same username you specified in the config file.
194+
126195
### Stopping the Server
127196

128-
To stop the GameVault server, navigate to the main **Apps** page, and check the box next to your running instance of gamevault:
197+
To stop the GameVault server, navigate to the main **Apps** page, and check the box next to your running instance of GameVault:
129198

130199
![Scale-EE-Stop1](/img/docs/setup/scale/Scale-EE-Stop1.png)
131200

132201
Then, click the drop-down menu for "Select action", and choose "Stop All Selected"
133202

134203
![Scale-EE-Stop2](/img/docs/setup/scale/Scale-EE-Stop2.png)
135204

136-
This will shutdown GameVault and the database.
205+
This will shut down GameVault and the database.
137206

138207
### Reading the Logs
139208

@@ -143,7 +212,7 @@ Under the "Workloads" section, you will see two "Containers" running:
143212

144213
![Scale-EE-logs1](/img/docs/setup/scale/Scale-EE-logs1.png)
145214

146-
Click the "veiw logs" icon next to either the database container (db) or the gamevault container (gamevault-backend) to open the logs:
215+
Click the "view logs" icon next to either the database container (db) or the GameVault container (gamevault-backend) to open the logs:
147216

148217
![Scale-EE-logs2](/img/docs/setup/scale/Scale-EE-logs2.png)
149218

@@ -155,8 +224,10 @@ You will see the previous number of log lines up to the number you entered, and
155224

156225
### Troubleshooting
157226

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.
159228
You can try a few things to ensure proper formatting:
160229

161230
- Use a text editor that maintains indents properly, such as Notepad++
162231
- 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`
233+
- Join the Discord and submit a support request!

0 commit comments

Comments
 (0)