From 3ee252f74d9a3107811ae80df574931ad06eaa66 Mon Sep 17 00:00:00 2001 From: <> Date: Tue, 21 May 2024 11:59:18 +0000 Subject: [PATCH] Deployed 9e1f7247 with MkDocs version: 1.6.0 --- images/docker-boinc/index.html | 4 ++-- images/docker-nextcloud/index.html | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/images/docker-boinc/index.html b/images/docker-boinc/index.html index 353154b93..569304c06 100644 --- a/images/docker-boinc/index.html +++ b/images/docker-boinc/index.html @@ -1,4 +1,4 @@ - boinc - LinuxServer.io
Skip to content

linuxserver/boinc

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

BOINC is a platform for high-throughput computing on a large scale (thousands or millions of computers). It can be used for volunteer computing (using consumer devices) or grid computing (using organizational resources). It supports virtualized, parallel, and GPU-based applications.

boinc

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/boinc: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

This image sets up the BOINC client and manager and makes its interface available via Guacamole server in the browser. The interface is available at http://your-ip:8080 or https://your-ip:8181.

By default, there is no password set for the main gui. Optional environment variable PASSWORD will allow setting a password for the user abc.

It is recommended to switch to Advanced View in the top menu, because the Computing Preferences don't seem to be displayed in Simple View.

Sometimes, the pop-up windows may open in a tiny box in the upper left corner of the screen. When that happens, you can find the corner and resize them.

GPU Hardware Acceleration

Intel

Hardware acceleration users for Intel Quicksync will need to mount their /dev/dri video device inside of the container by passing the following command when running or creating the container: --device=/dev/dri:/dev/dri We will automatically ensure the abc user inside of the container has the proper permissions to access this device.

Nvidia

Hardware acceleration users for Nvidia will need to install the container runtime provided by Nvidia on their host, instructions can be found here: https://github.com/NVIDIA/nvidia-docker We automatically add the necessary environment variable that will utilise all the features available on a GPU on the host. Once nvidia-docker is installed on your host you will need to re/create the docker container with the nvidia container runtime --runtime=nvidia and add an environment variable -e NVIDIA_VISIBLE_DEVICES=all (can also be set to a specific gpu's UUID, this can be discovered by running nvidia-smi --query-gpu=gpu_name,gpu_uuid --format=csv ). NVIDIA automatically mounts the GPU and drivers from your host into the BOINC docker container.

Options in all KasmVNC based GUI containers

This container is based on Docker Baseimage KasmVNC which means there are additional environment variables and run configurations to enable or disable specific functionality.

Optional environment variables

Variable Description
CUSTOM_PORT Internal port the container listens on for http if it needs to be swapped from the default 8080.
CUSTOM_HTTPS_PORT Internal port the container listens on for https if it needs to be swapped from the default 8181.
CUSTOM_USER HTTP Basic auth username, abc is default.
PASSWORD HTTP Basic auth password, abc is default. If unset there will be no auth
SUBFOLDER Subfolder for the application if running a subfolder reverse proxy, need both slashes IE /subfolder/
TITLE The page title displayed on the web browser, default "KasmVNC Client".
FM_HOME This is the home directory (landing) for the file manager, default "/config".
START_DOCKER If set to false a container with privilege will not automatically start the DinD Docker setup.
DRINODE If mounting in /dev/dri for DRI3 GPU Acceleration allows you to specify the device to use IE /dev/dri/renderD128
LC_ALL Set the Language for the container to run as IE fr_FR.UTF-8 ar_AE.UTF-8
NO_DECOR If set the application will run without window borders for use as a PWA.
NO_FULL Do not autmatically fullscreen applications when using openbox.

Optional run configurations

Variable Description
--privileged Will start a Docker in Docker (DinD) setup inside the container to use docker in an isolated environment. For increased performance mount the Docker directory inside the container to the host IE -v /home/user/docker-data:/var/lib/docker.
-v /var/run/docker.sock:/var/run/docker.sock Mount in the host level Docker socket to either interact with it via CLI or use Docker enabled applications.
--device /dev/dri:/dev/dri Mount a GPU into the container, this can be used in conjunction with the DRINODE environment variable to leverage a host video card for GPU accelerated appplications. Only Open Source drivers are supported IE (Intel,AMDGPU,Radeon,ATI,Nouveau)

Language Support - Internationalization

The environment variable LC_ALL can be used to start this image in a different language than English simply pass for example to launch the Desktop session in French LC_ALL=fr_FR.UTF-8. Some languages like Chinese, Japanese, or Korean will be missing fonts needed to render properly known as cjk fonts, but others may exist and not be installed. We only ensure fonts for Latin characters are present. Fonts can be installed with a mod on startup.

To install cjk fonts on startup as an example pass the environment variables:

-e DOCKER_MODS=linuxserver/mods:universal-package-install
+ boinc - LinuxServer.io      

linuxserver/boinc

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

BOINC is a platform for high-throughput computing on a large scale (thousands or millions of computers). It can be used for volunteer computing (using consumer devices) or grid computing (using organizational resources). It supports virtualized, parallel, and GPU-based applications.

boinc

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/boinc: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

This image sets up the BOINC client and manager and makes its interface available via Guacamole server in the browser. The interface is available at http://your-ip:8080 or https://your-ip:8181.

By default, there is no password set for the main gui. Optional environment variable PASSWORD will allow setting a password for the user abc.

It is recommended to switch to Advanced View in the top menu, because the Computing Preferences don't seem to be displayed in Simple View.

Sometimes, the pop-up windows may open in a tiny box in the upper left corner of the screen. When that happens, you can find the corner and resize them.

GPU Hardware Acceleration

Intel

Hardware acceleration users for Intel Quicksync will need to mount their /dev/dri video device inside of the container by passing the following command when running or creating the container: --device=/dev/dri:/dev/dri We will automatically ensure the abc user inside of the container has the proper permissions to access this device.

Nvidia

Hardware acceleration users for Nvidia will need to install the container runtime provided by Nvidia on their host, instructions can be found here: https://github.com/NVIDIA/nvidia-docker We automatically add the necessary environment variable that will utilise all the features available on a GPU on the host. Once nvidia-docker is installed on your host you will need to re/create the docker container with the nvidia container runtime --runtime=nvidia and add an environment variable -e NVIDIA_VISIBLE_DEVICES=all (can also be set to a specific gpu's UUID, this can be discovered by running nvidia-smi --query-gpu=gpu_name,gpu_uuid --format=csv ). NVIDIA automatically mounts the GPU and drivers from your host into the BOINC docker container.

Options in all KasmVNC based GUI containers

This container is based on Docker Baseimage KasmVNC which means there are additional environment variables and run configurations to enable or disable specific functionality.

Optional environment variables

Variable Description
CUSTOM_PORT Internal port the container listens on for http if it needs to be swapped from the default 8080.
CUSTOM_HTTPS_PORT Internal port the container listens on for https if it needs to be swapped from the default 8181.
CUSTOM_USER HTTP Basic auth username, abc is default.
PASSWORD HTTP Basic auth password, abc is default. If unset there will be no auth
SUBFOLDER Subfolder for the application if running a subfolder reverse proxy, need both slashes IE /subfolder/
TITLE The page title displayed on the web browser, default "KasmVNC Client".
FM_HOME This is the home directory (landing) for the file manager, default "/config".
START_DOCKER If set to false a container with privilege will not automatically start the DinD Docker setup.
DRINODE If mounting in /dev/dri for DRI3 GPU Acceleration allows you to specify the device to use IE /dev/dri/renderD128
LC_ALL Set the Language for the container to run as IE fr_FR.UTF-8 ar_AE.UTF-8
NO_DECOR If set the application will run without window borders for use as a PWA.
NO_FULL Do not autmatically fullscreen applications when using openbox.

Optional run configurations

Variable Description
--privileged Will start a Docker in Docker (DinD) setup inside the container to use docker in an isolated environment. For increased performance mount the Docker directory inside the container to the host IE -v /home/user/docker-data:/var/lib/docker.
-v /var/run/docker.sock:/var/run/docker.sock Mount in the host level Docker socket to either interact with it via CLI or use Docker enabled applications.
--device /dev/dri:/dev/dri Mount a GPU into the container, this can be used in conjunction with the DRINODE environment variable to leverage a host video card for GPU accelerated appplications. Only Open Source drivers are supported IE (Intel,AMDGPU,Radeon,ATI,Nouveau)

Language Support - Internationalization

The environment variable LC_ALL can be used to start this image in a different language than English simply pass for example to launch the Desktop session in French LC_ALL=fr_FR.UTF-8. Some languages like Chinese, Japanese, or Korean will be missing fonts needed to render properly known as cjk fonts, but others may exist and not be installed. We only ensure fonts for Latin characters are present. Fonts can be installed with a mod on startup.

To install cjk fonts on startup as an example pass the environment variables:

-e DOCKER_MODS=linuxserver/mods:universal-package-install
 -e INSTALL_PACKAGES=fonts-noto-cjk
 -e LC_ALL=zh_CN.UTF-8
 

The web interface has the option for "IME Input Mode" in Settings which will allow non english characters to be used from a non en_US keyboard on the client. Once enabled it will perform the same as a local Linux installation set to your locale.

Lossless mode

This container is capable of delivering a true lossless image at a high framerate to your web browser by changing the Stream Quality preset to "Lossless", more information here. In order to use this mode from a non localhost endpoint the HTTPS port on 8181 needs to be used. If using a reverse proxy to port 8080 specific headers will need to be set as outlined here.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
@@ -57,4 +57,4 @@
   --pull \
   -t lscr.io/linuxserver/boinc:latest .
 

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

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.02.24: - Update Readme with new env vars and ingest proper PWA icon.
  • 03.04.23: - Rebase to KasmVNC base image. Deprecate armhf build as the new base does not support it. Add bzip2 and xz-utils.
  • 14.11.22: - Fix opencl driver.
  • 18.09.22: - Rebase to jammy.
  • 24.02.22: - Rebase to focal.
  • 31.01.22: - Improve device permissions setting verbosity.
  • 23.03.21: - Rebase to rdesktop-web baseimage. Deprecate GUAC_USER and GUAC_PASS env vars. Existing users can set the new var PASSWORD for the user abc.
  • 01.04.20: - Install boinc from ppa.
  • 17.03.20: - Add armhf and aarch64 builds and switch to multi-arch image.
  • 16.03.20: - Clean up old pid files.
  • 15.03.20: - Initial release.
\ No newline at end of file +

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 10.02.24: - Update Readme with new env vars and ingest proper PWA icon.
  • 03.04.23: - Rebase to KasmVNC base image. Deprecate armhf build as the new base does not support it. Add bzip2 and xz-utils.
  • 14.11.22: - Fix opencl driver.
  • 18.09.22: - Rebase to jammy.
  • 24.02.22: - Rebase to focal.
  • 31.01.22: - Improve device permissions setting verbosity.
  • 23.03.21: - Rebase to rdesktop-web baseimage. Deprecate GUAC_USER and GUAC_PASS env vars. Existing users can set the new var PASSWORD for the user abc.
  • 01.04.20: - Install boinc from ppa.
  • 17.03.20: - Add armhf and aarch64 builds and switch to multi-arch image.
  • 16.03.20: - Clean up old pid files.
  • 15.03.20: - Initial release.
\ No newline at end of file diff --git a/images/docker-nextcloud/index.html b/images/docker-nextcloud/index.html index ac6d403c4..ce986cf92 100644 --- a/images/docker-nextcloud/index.html +++ b/images/docker-nextcloud/index.html @@ -1,4 +1,4 @@ - nextcloud - LinuxServer.io
Skip to content

linuxserver/nextcloud

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Nextcloud gives you access to all your files wherever you are.

Where are your photos and documents? With Nextcloud you pick a server of your choice, at home, in a data center or at a provider. And that is where your files will be. Nextcloud runs on that server, protecting your data and giving you access from your desktop or mobile devices. Through Nextcloud you also access, sync and share your existing data on that FTP drive at the office, a Dropbox or a NAS you have at home.

nextcloud

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/nextcloud: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

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Tag Available Description
latest Stable Nextcloud releases
develop Beta Nextcloud pre-releases only

Application Setup

Access the webui at https://<your-ip>:443, for more information check out Nextcloud.

Note: occ should be run without prepending with sudo -u abc php or sudo -u www-data php ie; docker exec -it nextcloud occ maintenance:mode --off

Updating Nextcloud

Updating Nextcloud is done by pulling the new image, and recreating the container with it.

It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16.

Since all data is stored in the /config and /data volumes, nothing gets lost. The startup script will check for the version in your volume and the installed docker version. If it finds a mismatch, it automatically starts the upgrade process.

Collaborative Editing

Nextcloud's built-in collaborative editing packages (Collabora/CODE and OnlyOffice) only work on x86_64 systems with glibc, and therefore they are not compatible with our images. You should create separate containers for them and set them up in Nextcloud with their respective connector addons.

If (auto) installed, those built-in packages may cause instability and should be removed.

HEIC Image Previews

In order to enable HEIC image preview generation you will need to add the following to your config.php file in your `config/www/nextcloud/config' directory;

  'enable_previews' => true,
+ nextcloud - LinuxServer.io      

linuxserver/nextcloud

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Nextcloud gives you access to all your files wherever you are.

Where are your photos and documents? With Nextcloud you pick a server of your choice, at home, in a data center or at a provider. And that is where your files will be. Nextcloud runs on that server, protecting your data and giving you access from your desktop or mobile devices. Through Nextcloud you also access, sync and share your existing data on that FTP drive at the office, a Dropbox or a NAS you have at home.

nextcloud

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/nextcloud: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

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Tag Available Description
latest Stable Nextcloud releases
develop Beta Nextcloud pre-releases only

Application Setup

Access the webui at https://<your-ip>:443, for more information check out Nextcloud.

Note: occ should be run without prepending with sudo -u abc php or sudo -u www-data php ie; docker exec -it nextcloud occ maintenance:mode --off

Updating Nextcloud

Updating Nextcloud is done by pulling the new image, and recreating the container with it.

It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16.

Since all data is stored in the /config and /data volumes, nothing gets lost. The startup script will check for the version in your volume and the installed docker version. If it finds a mismatch, it automatically starts the upgrade process.

Collaborative Editing

Nextcloud's built-in collaborative editing packages (Collabora/CODE and OnlyOffice) only work on x86_64 systems with glibc, and therefore they are not compatible with our images. You should create separate containers for them and set them up in Nextcloud with their respective connector addons.

If (auto) installed, those built-in packages may cause instability and should be removed.

HEIC Image Previews

In order to enable HEIC image preview generation you will need to add the following to your config.php file in your `config/www/nextcloud/config' directory;

  'enable_previews' => true,
   'enabledPreviewProviders' =>
   array (
     'OC\Preview\PNG',
@@ -63,4 +63,4 @@
   --pull \
   -t lscr.io/linuxserver/nextcloud:latest .
 

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset
-

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 19.05.24: - Added util-linux package required for taskset.
  • 10.04.24: - Added imagemagick-pdf.
  • 05.04.24: - Added imagemagick-heic. Manual update to config.php required - see above.
  • 02.04.24: - Existing users should update: site-confs/default.conf - Add support for the Client Push (notify_push) plugin and the new mod.
  • 22.03.24: - Add imagemagick-svg module.
  • 06.03.24: - Rebase to Alpine 3.19 with php 8.3.
  • 02.01.24: - Existing users should update: site-confs/default.conf - Cleanup default site conf.
  • 22.12.23: - Site default conf updating to include mime.types for js and mjs and update location to include more file types.
  • 28.10.23: - Disable web upgrades using occ during init.
  • 31.08.23: - Re-add updatenotification app. This allows users to be notified for app updates, but also notifies for NextCloud updates. Updating NextCloud via the web UI is not supported when using this image.
  • 14.08.23: - Add develop branch.
  • 25.06.23: - Move Nextcloud installation inside container. Remove CLI updater. See changes announcement.
  • 21.06.23: - Existing users should update /config/nginx/site-confs/default.conf - Security fix for real ip settings.
  • 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
  • 13.04.23: - Move ssl.conf include to default.conf.
  • 21.03.23: - Add php81-sysvsem as new dep for v26. Update default X-Robots-Tag to `noindex, nofollow``.
  • 02.03.23: - Set permissions on crontabs during init.
  • 20.01.23: - Rebase to alpine 3.17 with php8.1.
  • 10.10.22: - Rebasing to alpine 3.15 with php8. Restructure nginx configs (see changes announcement).
  • 30.09.22: - Disabled output_buffering as per [nextcloud docs](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html
  • 21.05.22: - Update version check endpoint.
  • 28.04.22: - Increase OPCache interned strings buffered setting to 16.
  • 14.04.22: - Nginx default site config updated for v23 (existing users should delete /config/nginx/site-confs/default.conf and restart the container). Fix LDAP connection.
  • 11.09.21: - Rebasing to alpine 3.14
  • 21.03.21: - Publish php8 tag for testing.
  • 25.02.21: - Nginx default site config updated for v21 (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 21.01.21: - Fix php iconv (was breaking the mail addon). If installed, attempt to remove broken CODE Server app during startup.
  • 20.01.21: - Increase php fcgi timeout to prevent 504 Gateway timeout errors (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 16.01.21: - Rebasing to alpine 3.13. Users with issues on 32-bit arm, see this article.
  • 12.08.20: - Various updates to default site config, including added support for webfinger (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 03.06.20: - Rebasing to alpine 3.12
  • 03.06.20: - Add php7-bcmath and php7-fileinfo
  • 31.05.20: - Add aliases for occ and updater.phar
  • 31.03.20: - Allow crontab to be user customized, fix logrotate.
  • 17.01.20: - Updated php.ini defaults and site config, including an optional HSTS directive (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 19.12.19: - Rebasing to alpine 3.11.
  • 18.11.19: - Nginx default site config updated for v17 (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 28.10.19: - Change cronjob to run every 5 minutes.
  • 24.10.19: - Nginx default site config updated due to CVE-2019-11043 (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 14.07.19: - Download nextcloud during build time.
  • 28.06.19: - Rebasing to alpine 3.10.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 27.02.19: - Updating base nginx config to sync up with v15 requirements.
  • 22.02.19: - Rebasing to alpine 3.9.
  • 28.01.19: - Add pipeline logic and multi arch.
  • 25.01.19: - Add php7-phar for occ upgrades.
  • 05.09.18: - Rebase to alpine 3.8.
  • 11.06.18: - Use latest rather than specific version for initial install.
  • 26.04.18: - Bump default install to 13.0.1.
  • 06.02.18: - Bump default install to 13.0.0.
  • 26.01.18: - Rebase to alpine 3.7, bump default install to 12.0.5.
  • 12.12.17: - Bump default install to 12.0.4, fix continuation lines.
  • 15.10.17: - Sed php.ini for opcache requirements in newer nextcloud versions.
  • 20.09.17: - Bump default install to 12.0.3.
  • 19.08.17: - Bump default install to 12.0.2.
  • 25.05.17: - Rebase to alpine 3.6.
  • 22.05.17: - Update to nextcloud 12.0, adding required dependecies and note about commenting out SAMEORIGIN; line.
  • 03.05.17: - Use community repo of memcache.
  • 07.03.17: - Release into main repository and upgrade to php7 and Alpine 3.5.
\ No newline at end of file +

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 19.05.24: - Added util-linux package required for taskset.
  • 10.04.24: - Added imagemagick-pdf.
  • 05.04.24: - Added imagemagick-heic. Manual update to config.php required - see above.
  • 02.04.24: - Existing users should update: site-confs/default.conf - Add support for the Client Push (notify_push) plugin and the new mod.
  • 22.03.24: - Add imagemagick-svg module.
  • 06.03.24: - Rebase to Alpine 3.19 with php 8.3.
  • 02.01.24: - Existing users should update: site-confs/default.conf - Cleanup default site conf.
  • 22.12.23: - Site default conf updating to include mime.types for js and mjs and update location to include more file types.
  • 28.10.23: - Disable web upgrades using occ during init.
  • 31.08.23: - Re-add updatenotification app. This allows users to be notified for app updates, but also notifies for NextCloud updates. Updating NextCloud via the web UI is not supported when using this image.
  • 14.08.23: - Add develop branch.
  • 25.06.23: - Move Nextcloud installation inside container. Remove CLI updater. See changes announcement.
  • 21.06.23: - Existing users should update /config/nginx/site-confs/default.conf - Security fix for real ip settings.
  • 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
  • 13.04.23: - Move ssl.conf include to default.conf.
  • 21.03.23: - Add php81-sysvsem as new dep for v26. Update default X-Robots-Tag to `noindex, nofollow``.
  • 02.03.23: - Set permissions on crontabs during init.
  • 20.01.23: - Rebase to alpine 3.17 with php8.1.
  • 10.10.22: - Rebasing to alpine 3.15 with php8. Restructure nginx configs (see changes announcement).
  • 30.09.22: - Disabled output_buffering as per [nextcloud docs](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html
  • 21.05.22: - Update version check endpoint.
  • 28.04.22: - Increase OPCache interned strings buffered setting to 16.
  • 14.04.22: - Nginx default site config updated for v23 (existing users should delete /config/nginx/site-confs/default.conf and restart the container). Fix LDAP connection.
  • 11.09.21: - Rebasing to alpine 3.14
  • 21.03.21: - Publish php8 tag for testing.
  • 25.02.21: - Nginx default site config updated for v21 (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 21.01.21: - Fix php iconv (was breaking the mail addon). If installed, attempt to remove broken CODE Server app during startup.
  • 20.01.21: - Increase php fcgi timeout to prevent 504 Gateway timeout errors (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 16.01.21: - Rebasing to alpine 3.13. Users with issues on 32-bit arm, see this article.
  • 12.08.20: - Various updates to default site config, including added support for webfinger (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 03.06.20: - Rebasing to alpine 3.12
  • 03.06.20: - Add php7-bcmath and php7-fileinfo
  • 31.05.20: - Add aliases for occ and updater.phar
  • 31.03.20: - Allow crontab to be user customized, fix logrotate.
  • 17.01.20: - Updated php.ini defaults and site config, including an optional HSTS directive (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 19.12.19: - Rebasing to alpine 3.11.
  • 18.11.19: - Nginx default site config updated for v17 (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 28.10.19: - Change cronjob to run every 5 minutes.
  • 24.10.19: - Nginx default site config updated due to CVE-2019-11043 (existing users should delete /config/nginx/site-confs/default.conf and restart the container).
  • 14.07.19: - Download nextcloud during build time.
  • 28.06.19: - Rebasing to alpine 3.10.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 27.02.19: - Updating base nginx config to sync up with v15 requirements.
  • 22.02.19: - Rebasing to alpine 3.9.
  • 28.01.19: - Add pipeline logic and multi arch.
  • 25.01.19: - Add php7-phar for occ upgrades.
  • 05.09.18: - Rebase to alpine 3.8.
  • 11.06.18: - Use latest rather than specific version for initial install.
  • 26.04.18: - Bump default install to 13.0.1.
  • 06.02.18: - Bump default install to 13.0.0.
  • 26.01.18: - Rebase to alpine 3.7, bump default install to 12.0.5.
  • 12.12.17: - Bump default install to 12.0.4, fix continuation lines.
  • 15.10.17: - Sed php.ini for opcache requirements in newer nextcloud versions.
  • 20.09.17: - Bump default install to 12.0.3.
  • 19.08.17: - Bump default install to 12.0.2.
  • 25.05.17: - Rebase to alpine 3.6.
  • 22.05.17: - Update to nextcloud 12.0, adding required dependecies and note about commenting out SAMEORIGIN; line.
  • 03.05.17: - Use community repo of memcache.
  • 07.03.17: - Release into main repository and upgrade to php7 and Alpine 3.5.
\ No newline at end of file