文件列表:

.editorconfig (613, 2024-01-04)
Dockerfile (1066, 2024-01-04)
Dockerfile.aarch64 (1074, 2024-01-04)
Jenkinsfile (50953, 2024-01-04)
LICENSE (35149, 2024-01-04)
jenkins-vars.yml (857, 2024-01-04)
package_versions.txt (34236, 2024-01-04)
root/ (0, 2024-01-04)
root/etc/ (0, 2024-01-04)
root/etc/s6-overlay/ (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/ (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-config-end/ (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-config-end/dependencies.d/ (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-config-end/dependencies.d/init-quassel-web-config (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-quassel-web-config/ (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-quassel-web-config/dependencies.d/ (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-quassel-web-config/dependencies.d/init-config (0, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-quassel-web-config/run (1555, 2024-01-04)
root/etc/s6-overlay/s6-rc.d/init-quassel-web-config/type (8, 2024-01-04)
... ...

[](https://linuxserver.io) [](https://blog.linuxserver.io "all the things you can do with our containers including How-To guides, opinions and much more!") [](https://discord.gg/YWrKVTn "realtime support / chat with the community and the team.") [](https://discourse.linuxserver.io "post on our community forum.") [](https://fleet.linuxserver.io "an online web interface which displays all of our maintained images.") [](https://github.com/linuxserver "view the source for all of our repositories.") [](https://opencollective.com/linuxserver "please consider helping us by either donating or contributing to our budget") The [LinuxServer.io](https://linuxserver.io) team brings you another container release featuring: * regular and timely application updates * easy user mappings (PGID, PUID) * custom base image with s6 overlay * weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth * regular security updates Find us at: * [Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more! * [Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team. * [Discourse](https://discourse.linuxserver.io) - post on our community forum. * [Fleet](https://fleet.linuxserver.io) - an online web interface which displays all of our maintained images. * [GitHub](https://github.com/linuxserver) - view the source for all of our repositories. * [Open Collective](https://opencollective.com/linuxserver) - please consider helping us by either donating or contributing to our budget # [linuxserver/quassel-web](https://github.com/linuxserver/docker-quassel-web) [](https://scarf.sh/gateway/linuxserver-ci/docker/linuxserver%2Fquassel-web) [](https://github.com/linuxserver/docker-quassel-web) [](https://github.com/linuxserver/docker-quassel-web/releases) [](https://github.com/linuxserver/docker-quassel-web/packages) [](https://gitlab.com/linuxserver.io/docker-quassel-web/container_registry) [](https://quay.io/repository/linuxserver.io/quassel-web) [](https://hub.docker.com/r/linuxserver/quassel-web) [](https://hub.docker.com/r/linuxserver/quassel-web) [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-quassel-web/job/master/) [](https://ci-tests.linuxserver.io/linuxserver/quassel-web/latest/index.html) [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/) [](https://github.com/magne4000/quassel-webserver) ## Supported Architectures We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://distribution.github.io/distribution/spec/manifest-v2-2/#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/). 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-\ | | arm64 | | arm64v8-\ | | 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 ``` ### 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](https://docs.linuxserver.io/faq#strict-proxy). ## 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](https://docs.linuxserver.io/general/docker-compose)) ```yaml --- version: "2.1" services: quassel-web: image: lscr.io/linuxserver/quassel-web:latest container_name: quassel-web environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - QUASSEL_CORE=192.168.1.10 #optional - QUASSEL_PORT=4242 #optional - QUASSEL_HTTPS= #optional - URL_BASE=/quassel #optional volumes: - /path/to/data:/config ports: - 64080:64080 #optional - 64443:64443 #optional restart: unless-stopped ``` ### docker cli ([click here for more info](https://docs.docker.com/engine/reference/commandline/cli/)) ```bash docker run -d \ --name=quassel-web \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Etc/UTC \ -e QUASSEL_CORE=192.168.1.10 `#optional` \ -e QUASSEL_PORT=4242 `#optional` \ -e QUASSEL_HTTPS= `#optional` \ -e URL_BASE=/quassel `#optional` \ -p 64080:64080 `#optional` \ -p 64443:64443 `#optional` \ -v /path/to/data:/config \ --restart unless-stopped \ lscr.io/linuxserver/quassel-web:latest ``` ## Parameters Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `:` 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. | Parameter | Function | | :----: | --- | | `-p 64080` | Quassel-web http webui | | `-p 64443` | Quassel-web https webui | | `-e PUID=1000` | for UserID - see below for explanation | | `-e PGID=1000` | for GroupID - see below for explanation | | `-e TZ=Etc/UTC` | specify a timezone to use, see this [list](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List). | | `-e QUASSEL_CORE=192.168.1.10` | specify the URL or IP address of your Quassel Core instance | | `-e QUASSEL_PORT=4242` | specify the port of your Quassel Core instance | | `-e QUASSEL_HTTPS=` | Set to `true` to have Quassel web serve over https on port 64443 instead of http on port 64080. | | `-e URL_BASE=/quassel` | Specify a url-base in reverse proxy setups ie. `/quassel` | | `-v /config` | this will store config on the docker host | ## Environment variables from files (Docker secrets) You can set any environment variable from a file by using a special prepend `FILE__`. As an example: ```bash -e FILE__MYVAR=/run/secrets/mysecretvariable ``` Will set the environment variable `MYVAR` based on the contents of the `/run/secrets/mysecretvariable` file. ## Umask for running applications For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support. ## User / Group Identifiers When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`. Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic. In this instance `PUID=1000` and `PGID=1000`, to find yours use `id your_user` as below: ```bash id your_user ``` Example output: ```text uid=1000(your_user) gid=1000(your_user) groups=1000(your_user) ``` ## Docker Mods [](https://mods.linuxserver.io/?mod=quassel-web "view available mods for this container.") [](https://mods.linuxserver.io/?mod=universal "view available universal mods.") 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. ## Support Info * Shell access whilst the container is running: ```bash docker exec -it quassel-web /bin/bash ``` * To monitor the logs of the container in realtime: ```bash docker logs -f quassel-web ``` * Container version number: ```bash docker inspect -f '{{ index .Config.Labels "build_version" }}' quassel-web ``` * Image version number: ```bash docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-web:latest ``` ## Updating Info Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the [Application Setup](#application-setup) section above to see if it is recommended for the image. Below are the instructions for updating containers: ### Via Docker Compose * Update images: * All images: ```bash docker-compose pull ``` * Single image: ```bash docker-compose pull quassel-web ``` * Update containers: * All containers: ```bash docker-compose up -d ``` * Single container: ```bash docker-compose up -d quassel-web ``` * You can also remove the old dangling images: ```bash docker image prune ``` ### Via Docker Run * Update the image: ```bash docker pull lscr.io/linuxserver/quassel-web:latest ``` * Stop the running container: ```bash docker stop quassel-web ``` * Delete the container: ```bash docker rm quassel-web ``` * 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) * You can also remove the old dangling images: ```bash docker image prune ``` ### Via Watchtower auto-updater (only use if you don't remember the original parameters) * Pull the latest image at its tag and replace it with the same env variables in one run: ```bash docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ containrrr/watchtower \ --run-once quassel-web ``` * You can also remove the old dangling images: `docker image prune` **warning**: 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). ### Image Update Notifications - Diun (Docker Image Update Notifier) **tip**: We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported. ## Building locally If you want to make local modifications to these images for development purposes or just to customize the logic: ```bash git clone https://github.com/linuxserver/docker-quassel-web.git cd docker-quassel-web docker build \ --no-cache \ --pull \ -t lscr.io/linuxserver/quassel-web:latest . ``` The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static` ```bash docker run --rm --privileged multiarch/qemu-user-static:register --reset ``` 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](https://www.linuxserver.io/blog/a-farewell-to-arm-hf) * **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.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：