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
{{ message }}
This repository was archived by the owner on Jan 3, 2025. It is now read-only.
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
109
-
```
109
+
110
+
```bash
110
111
docker run --rm --privileged multiarch/qemu-user-static:register --reset
111
112
```
112
113
113
114
Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64`.
114
115
115
-
## Update the chagelog
116
+
## Update the changelog
116
117
117
118
If you are modifying the Dockerfiles or any of the startup scripts in [root](https://github.com/linuxserver/docker-quassel-web/tree/master/root), add an entry to the changelog
[Quassel-web](https://github.com/magne4000/quassel-webserver) is a web client for Quassel. Note that a Quassel-Core instance is required, we have a container available [here.](https://hub.docker.com/r/linuxserver/quassel-core/)
42
-
42
+
[Quassel-web](https://github.com/magne4000/quassel-webserver) is a web client for Quassel. Note that a Quassel-Core instance is required, we have a container available [here.](https://hub.docker.com/r/linuxserver/quassel-core/)
@@ -57,6 +57,13 @@ The architectures supported by this image are:
57
57
| arm64 | arm64v8-latest |
58
58
| armhf | arm32v6-latest |
59
59
60
+
## Application Setup
61
+
62
+
By default this container webui will be available on `http://$SERVER_IP:64080`. To setup this container you can either use the envrionment variables we recommend or manually setup the configuration file by leaving out the `QUASSEL_CORE` environment variable among others.
63
+
The configuration file using this method can be found at:
64
+
```
65
+
/config/settings-user.js
66
+
```
60
67
61
68
## Usage
62
69
@@ -88,7 +95,7 @@ services:
88
95
89
96
### docker cli
90
97
91
-
```
98
+
```bash
92
99
docker run -d \
93
100
--name=quassel-web \
94
101
-e PUID=1000 \
@@ -102,7 +109,6 @@ docker run -d \
102
109
ghcr.io/linuxserver/quassel-web
103
110
```
104
111
105
-
106
112
## Parameters
107
113
108
114
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
@@ -123,7 +129,7 @@ You can set any environment variable from a file by using a special prepend `FIL
123
129
124
130
As an example:
125
131
126
-
```
132
+
```bash
127
133
-e FILE__PASSWORD=/run/secrets/mysecretpassword
128
134
```
129
135
@@ -142,28 +148,17 @@ Ensure any volume directories on the host are owned by the same user you specify
142
148
143
149
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
By default this container webui will be available on `http://$SERVER_IP:64080`. To setup this container you can either use the envrionment variables we recommend or manually setup the configuration file by leaving out the `QUASSEL_CORE` environment variable among others.
155
-
The configuration file using this method can be found at:
156
-
```
157
-
/config/settings-user.js
158
-
```
159
-
160
-
161
156
## Docker Mods
157
+
162
158
[](https://mods.linuxserver.io/?mod=quassel-web"view available mods for this container.")[](https://mods.linuxserver.io/?mod=universal"view available universal mods.")
163
159
164
160
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
165
161
166
-
167
162
## Support Info
168
163
169
164
* Shell access whilst the container is running: `docker exec -it quassel-web /bin/bash`
@@ -180,38 +175,45 @@ Most of our images are static, versioned, and require an image update and contai
180
175
Below are the instructions for updating containers:
181
176
182
177
### Via Docker Compose
178
+
183
179
* Update all images: `docker-compose pull`
184
180
* or update a single image: `docker-compose pull quassel-web`
185
181
* Let compose update all containers as necessary: `docker-compose up -d`
186
182
* or update a single container: `docker-compose up -d quassel-web`
187
183
* You can also remove the old dangling images: `docker image prune`
188
184
189
185
### Via Docker Run
186
+
190
187
* Update the image: `docker pull ghcr.io/linuxserver/quassel-web`
191
188
* Stop the running container: `docker stop quassel-web`
192
189
* Delete the container: `docker rm quassel-web`
193
190
* Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
194
191
* You can also remove the old dangling images: `docker image prune`
195
192
196
193
### Via Watchtower auto-updater (only use if you don't remember the original parameters)
194
+
197
195
* Pull the latest image at its tag and replace it with the same env variables in one run:
198
-
```
196
+
197
+
```bash
199
198
docker run --rm \
200
199
-v /var/run/docker.sock:/var/run/docker.sock \
201
200
containrrr/watchtower \
202
201
--run-once quassel-web
203
202
```
203
+
204
204
* You can also remove the old dangling images: `docker image prune`
205
205
206
206
**Note:** We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using [Docker Compose](https://docs.linuxserver.io/general/docker-compose).
* We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
210
211
211
212
## Building locally
212
213
213
214
If you want to make local modifications to these images for development purposes or just to customize the logic:
0 commit comments