linuxserver/quassel-web¶
Quassel-web is a web client for Quassel. Note that a Quassel-Core instance is required, we have a container available here.
Supported Architectures¶
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/quassel-web:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-<version tag> |
| arm64 | ✅ | arm64v8-<version tag> |
| armhf | ❌ |
Application Setup¶
By default this container webui will be available on https://$SERVER_IP:64443. To setup this container you can either use the environment variables we recommend or manually setup the configuration file by leaving out the QUASSEL_CORE environment variable among others. The configuration file using this method can be found at:
/config/settings-user.js
+ quassel-web - LinuxServer.io linuxserver/quassel-web¶
Quassel-web is a web client for Quassel. Note that a Quassel-Core instance is required, we have a container available here.
Supported Architectures¶
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/quassel-web:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture Available Tag x86-64 ✅ amd64-<version tag> arm64 ✅ arm64v8-<version tag> armhf ❌
Application Setup¶
By default this container webui will be available on https://$SERVER_IP:64443. To setup this container you can either use the environment variables we recommend or manually setup the configuration file by leaving out the QUASSEL_CORE environment variable among others. The configuration file using this method can be found at:
Strict reverse proxies¶
This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container.
Usage¶
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)¶
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
Versions¶
- 10.11.23: - Rebase to Alpine 3.18. Rename settings-user.js to .cjs to match upstream.
- 06.07.23: - Deprecate armhf. As announced here
- 13.02.23: - Rebasing to Alpine 3.17, migrate to s6v3.
- 12.02.22: - Rebasing to alpine 3.15.
- 01.06.20: - Rebasing to alpine 3.12.
- 19.12.19: - Rebasing to alpine 3.11.
- 28.06.19: - Rebasing to alpine 3.10.
- 18.05.19: - Reconfigure environmental variable setup.
- 28.04.19: - Initial Release.
Last update: November 10, 2023
Created: February 5, 2019
\ No newline at end of file
+Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
Versions¶
- 10.11.23: - Rebase to Alpine 3.18. Rename settings-user.js to .cjs to match upstream.
- 06.07.23: - Deprecate armhf. As announced here
- 13.02.23: - Rebasing to Alpine 3.17, migrate to s6v3.
- 12.02.22: - Rebasing to alpine 3.15.
- 01.06.20: - Rebasing to alpine 3.12.
- 19.12.19: - Rebasing to alpine 3.11.
- 28.06.19: - Rebasing to alpine 3.10.
- 18.05.19: - Reconfigure environmental variable setup.
- 28.04.19: - Initial Release.
Created: February 5, 2019