mirror of
https://github.com/linuxserver/cstate.git
synced 2026-01-20 20:12:05 +08:00
381 lines
35 KiB
XML
381 lines
35 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://info.linuxserver.io"/><title>nextcloud on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/nextcloud/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-11-02T23:00:00+00:00</lastBuildDate><updated>2023-11-02T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/nextcloud/index.xml" rel="self" type="application/rss+xml"/><item><title>Notification: Significant changes to cron</title><link>https://info.linuxserver.io/issues/2023-11-02-cron/</link><pubDate>Thu, 02 Nov 2023 23:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-11-02-cron/</guid><category/><description>We&rsquo;ve decided to make some changes to how cron is shipped in our images.
|
|
Previous state of cron We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for abc or root in /config/crontabs/. This has allowed users to customize crontabs.
|
|
This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations.</description><content type="html"><p>We&rsquo;ve decided to make some changes to how cron is shipped in our images.</p>
|
|
<h2 id="previous-state-of-cron">Previous state of cron</h2>
|
|
<p>We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>. This has allowed users to customize crontabs.</p>
|
|
<p>This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations. It could also mean we are unable to automatically make required changes if user customizations make an automated adjustments impossible. In these cases, users have been required to update crontabs on their own.</p>
|
|
<p>As a side note, we also offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> that can be applied to add the ability to use cron for both <code>abc</code> and <code>root</code> in any container.</p>
|
|
<h2 id="going-forward">Going forward</h2>
|
|
<p>When an application requires cron, we will also no longer setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>, unless user customizations to the crontab are required.</p>
|
|
<p>Instead, we are internalizing the crontab files. This should make it easier for us to update crontabs when changes to the image require updates to crontabs. It also means users won&rsquo;t have to keep up with changes to crontab requirements that may break their applications.</p>
|
|
<p><strong>IMPORTANT:</strong> We are NOT removing existing crontabs from <code>/config/crontabs/</code>, they will simply be ignored unless otherwise noted.</p>
|
|
<p>We will continue to offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> with a new purpose of making crontabs for <code>abc</code> and <code>root</code> customizable by setting them up in up <code>/config/crontabs/</code> and configuring the cron service to recognize them, essentially restoring the original behavior. This effectively makes the cron mod the only way to customize crontabs.</p>
|
|
<p>As a side note, we are also adjusting all existing crontabs we ship to run as <code>abc</code> instead of <code>root</code>. This improves security and consistency in our images.</p>
|
|
<h3 id="exceptions">Exceptions</h3>
|
|
<p>Diskover requires setting your own crontab schedule. The container will now run cron using <code>/config/crontabs/abc</code> instead of <code>/config/crontabs/root</code>. The <code>/config/crontabs/root</code> file is NOT being automatically removed, but will be ignored.</p>
|
|
<p>Rsnapshot requires setting your own crontab schedule, and in some cases requires backups to run as root. The container will continue to run cron using <code>/config/crontabs/root</code>.</p>
|
|
<h2 id="timing">Timing</h2>
|
|
<p>You can expect to see these changes merge today, and begin building into our images over the next few days and weeks.</p></content></item><item><title>Notification: Significant changes to cron incoming</title><link>https://info.linuxserver.io/issues/2023-10-20-cron/</link><pubDate>Fri, 20 Oct 2023 23:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-20-cron/</guid><category/><description>We&rsquo;ve decided to make some changes to how cron is shipped in our images.
|
|
Current state of cron We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for abc or root in /config/crontabs/. This has allowed users to customize crontabs.
|
|
This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations.</description><content type="html"><p>We&rsquo;ve decided to make some changes to how cron is shipped in our images.</p>
|
|
<h2 id="current-state-of-cron">Current state of cron</h2>
|
|
<p>We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>. This has allowed users to customize crontabs.</p>
|
|
<p>This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations. It could also mean we are unable to automatically make required changes if user customizations make an automated adjustments impossible. In these cases, users have been required to update crontabs on their own.</p>
|
|
<p>As a side note, we also offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> that can be applied to add the ability to use cron for both <code>abc</code> and <code>root</code> in any container.</p>
|
|
<h2 id="incoming-changes">Incoming changes</h2>
|
|
<p>When an application requires cron, we will also no longer setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>, unless user customizations to the crontab are required.</p>
|
|
<p>Instead, we are internalizing the crontab files. This should make it easier for us to update crontabs when changes to the image require updates to crontabs. It also means users won&rsquo;t have to keep up with changes to crontab requirements that may break their applications.</p>
|
|
<p><strong>IMPORTANT:</strong> We are NOT removing existing crontabs from <code>/config/crontabs/</code>, they will simply be ignored unless otherwise noted.</p>
|
|
<p>We will continue to offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> with a new purpose of making crontabs for <code>abc</code> and <code>root</code> customizable by setting them up in up <code>/config/crontabs/</code> and configuring the cron service to recognize them, essentially restoring the original behavior. This effectively makes the cron mod the only way to customize crontabs.</p>
|
|
<p>As a side note, we are also adjusting all existing crontabs we ship to run as <code>abc</code> instead of <code>root</code>. This improves security and consistency in our images.</p>
|
|
<h3 id="exceptions">Exceptions</h3>
|
|
<p>Diskover requires setting your own crontab schedule. The container will now run cron using <code>/config/crontabs/abc</code> instead of <code>/config/crontabs/root</code>. The <code>/config/crontabs/root</code> file is NOT being automatically removed, but will be ignored.</p>
|
|
<p>Rsnapshot requires setting your own crontab schedule, and in some cases requires backups to run as root. The container will continue to run cron using <code>/config/crontabs/root</code>.</p>
|
|
<h2 id="timing">Timing</h2>
|
|
<p>You can expect to see these changes merge around November 1st, 2023. An additional post will be made with all of the above information and any updates if anything changes between now and then.</p></content></item><item><title>Notification: Significant changes to cron incoming</title><link>https://info.linuxserver.io/issues/2023-10-01-cron/</link><pubDate>Sun, 01 Oct 2023 23:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-01-cron/</guid><category/><description>We&rsquo;ve decided to make some changes to how cron is shipped in our images.
|
|
Current state of cron We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for abc or root in /config/crontabs/. This has allowed users to customize crontabs.
|
|
This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations.</description><content type="html"><p>We&rsquo;ve decided to make some changes to how cron is shipped in our images.</p>
|
|
<h2 id="current-state-of-cron">Current state of cron</h2>
|
|
<p>We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>. This has allowed users to customize crontabs.</p>
|
|
<p>This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations. It could also mean we are unable to automatically make required changes if user customizations make an automated adjustments impossible. In these cases, users have been required to update crontabs on their own.</p>
|
|
<p>As a side note, we also offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> that can be applied to add the ability to use cron for both <code>abc</code> and <code>root</code> in any container.</p>
|
|
<h2 id="incoming-changes">Incoming changes</h2>
|
|
<p>When an application requires cron, we will also no longer setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>, unless user customizations to the crontab are required.</p>
|
|
<p>Instead, we are internalizing the crontab files. This should make it easier for us to update crontabs when changes to the image require updates to crontabs. It also means users won&rsquo;t have to keep up with changes to crontab requirements that may break their applications.</p>
|
|
<p><strong>IMPORTANT:</strong> We are NOT removing existing crontabs from <code>/config/crontabs/</code>, they will simply be ignored unless otherwise noted.</p>
|
|
<p>We will continue to offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> with a new purpose of making crontabs for <code>abc</code> and <code>root</code> customizable by setting them up in up <code>/config/crontabs/</code> and configuring the cron service to recognize them, essentially restoring the original behavior. This effectively makes the cron mod the only way to customize crontabs.</p>
|
|
<p>As a side note, we are also adjusting all existing crontabs we ship to run as <code>abc</code> instead of <code>root</code>. This improves security and consistency in our images.</p>
|
|
<h3 id="exceptions">Exceptions</h3>
|
|
<p>Diskover requires setting your own crontab schedule. The container will now run cron using <code>/config/crontabs/abc</code> instead of <code>/config/crontabs/root</code>. The <code>/config/crontabs/root</code> file is NOT being automatically removed, but will be ignored.</p>
|
|
<p>Rsnapshot requires setting your own crontab schedule, and in some cases requires backups to run as root. The container will continue to run cron using <code>/config/crontabs/root</code>.</p>
|
|
<h2 id="timing">Timing</h2>
|
|
<p>You can expect to see these changes merge around November 1st, 2023. An additional post will be made with all of the above information and any updates if anything changes between now and then.</p></content></item><item><title>Notification: Changes to our Nextcloud image</title><link>https://info.linuxserver.io/issues/2023-06-25-nextcloud/</link><pubDate>Sun, 25 Jun 2023 22:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-06-25-nextcloud/</guid><category/><description>We are releasing a new version of our Nextcloud image that is built with the Nextcloud application inside the image, rather than in the user /config volume. This means manually updating Nextcloud via command line will no longer be necessary or supported. The updater.phar command is completely removed. Installations for existing users will be migrated automatically when updating the container image. All future updates to your Nextcloud instance will happen via container image updates.</description><content type="html"><p>We are releasing a new version of our <a href="https://github.com/linuxserver/docker-nextcloud/">Nextcloud image</a> that is built with the Nextcloud application inside the image, rather than in the user <code>/config</code> volume. This means manually updating Nextcloud via command line will no longer be necessary or supported. The <code>updater.phar</code> command is completely removed. Installations for existing users will be migrated automatically when updating the container image. All future updates to your Nextcloud instance will happen via container image updates.</p>
|
|
<p><strong>Updating via the admin web UI is no longer supported.</strong></p>
|
|
<p><strong>Downgrading is not supported.</strong></p>
|
|
<p>An important thing to keep in mind is that systems that automatically update your container will result in irreversible changes to your Nextcloud instance. We recommend pinning a specific tagged version like <code>lscr.io/linuxserver/nextcloud:version-27.0.0</code> and manually changing your image version when you are ready to upgrade.</p>
|
|
<p>Excerpts from the updated README:</p>
|
|
<h3 id="updating-nextcloud">Updating Nextcloud</h3>
|
|
<p>Updating Nextcloud is done by pulling the new image, and recreating the container with it.</p>
|
|
<p>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.</p>
|
|
<p>Since all data is stored in the <code>/config</code> and <code>/data</code> 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.</p>
|
|
<h3 id="cant-start-nextcloud">Can&rsquo;t start Nextcloud</h3>
|
|
<p>If after updating your container image you receive a message along these lines:</p>
|
|
<blockquote>
|
|
<p>Can&rsquo;t start Nextcloud because the version of the data (<code>#.#.#.#</code>) is more than one major version behind the docker image version (<code>#.#.#.#</code>) and upgrading more than one major version is not supported. Please run an image tagged for the major version <code>##</code> first.&quot;</p>
|
|
</blockquote>
|
|
<p>The version of Nextcloud that you have installed in your persistent <code>/config</code> volume will need to be updated using an older image before you can use the new image.</p>
|
|
<p>Major version images, to be used for upgrading:</p>
|
|
<table>
|
|
<thead>
|
|
<tr>
|
|
<th>Image/Tag</th>
|
|
<th>PHP</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:version-26.0.2</code></td>
|
|
<td>8.2</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:version-25.0.4</code></td>
|
|
<td>8.1</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:version-24.0.12</code></td>
|
|
<td>8.1</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:version-23.0.4</code></td>
|
|
<td>7.4</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:version-22.2.3</code></td>
|
|
<td>7.4</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:version-21.0.3</code></td>
|
|
<td>7.4</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:version-20.0.7</code></td>
|
|
<td>7.4</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<p>Package locked tags, listed for LSIO team reference:</p>
|
|
<table>
|
|
<thead>
|
|
<tr>
|
|
<th>Image/Tag</th>
|
|
<th>PHP</th>
|
|
<th>Notes</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:26.0.2-ls245</code></td>
|
|
<td>8.1</td>
|
|
<td>Last tag with PHP 8.1</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>lscr.io/linuxserver/nextcloud:24.0.6-ls204</code></td>
|
|
<td>7.4</td>
|
|
<td>Last tag with PHP 7.4</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<ul>
|
|
<li>Check your <code>/config/www/nextcloud/config/config.php</code> file or <code>/config/www/nextcloud/version.php</code> file to determine the version you have installed</li>
|
|
<li>Switch your image to the corresponding major version from the table above (ex: your files indicate <code>24.x.x</code>, use <code>lscr.io/linuxserver/nextcloud:version-24.0.12</code>) and start the container</li>
|
|
<li>Run <code>docker exec -it nextcloud updater.phar</code> <strong><em>repeatedly</em></strong> until you have updated to Nextcloud <code>27.x.x</code>, or the updater says <code>This version of Nextcloud is not compatible with &gt; PHP x.x</code></li>
|
|
<li>Check your files again to determine the version you have installed
|
|
<ul>
|
|
<li>If your installed version is below 26, repeat the steps above until you get to version 26</li>
|
|
<li>If your installed version is 26 or 27, continue with the instructions below</li>
|
|
</ul>
|
|
</li>
|
|
<li>Switch your image to <code>lscr.io/linuxserver/nextcloud:version-27.0.0</code> and start the container. Note the <code>updater.phar</code> is no longer available, or needed</li>
|
|
<li>Run <code>docker logs nextcloud</code> and check for any issues (report <a href="https://github.com/linuxserver/docker-nextcloud/issues">issues on GitHub</a>)</li>
|
|
<li>As of posting this information, Nextclouod 27 is the latest current version. If you are reading this after a new major version of Nextcloud beyond 27 is released, check <a href="https://github.com/linuxserver/docker-nextcloud/releases">releases on GitHub</a> and proceed to switch to the next major version tag one by one until you are current. Updating more than one major version at a time is not supported</li>
|
|
<li>You should now be able to switch your image to <code>lscr.io/linuxserver/nextcloud</code> (no tag) if you prefer to run the latest image (although we do recommend pinning a specific version)</li>
|
|
<li>Run <code>docker exec -it nextcloud mv /config/nginx/site-confs/default.conf /config/nginx/site-confs/default.conf.bak</code></li>
|
|
<li>Run <code>docker exec -it nextcloud mv /config/nginx/nginx.conf /config/nginx/nginx.conf.bak</code></li>
|
|
<li>Run <code>docker restart nextcloud</code></li>
|
|
<li>Nextcloud should now be in a working state</li>
|
|
</ul>
|
|
<p>Optional:</p>
|
|
<ul>
|
|
<li>If you had customized any of the nginx configs that were renamed above, compare the <code>.bak</code> file to the new live file and apply any customizations you require. Note the <code>root</code> line in <code>site-confs/default.conf</code> should be changed from <code>/config/www/nextcloud/</code> to <code>/app/www/public</code></li>
|
|
<li>Remove the <code>.bak</code> files</li>
|
|
</ul></content></item><item><title>Nextcloud php8 Tag Deprecation Notice</title><link>https://info.linuxserver.io/issues/2022-10-24-nextcloud/</link><pubDate>Tue, 25 Oct 2022 20:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2022-10-24-nextcloud/</guid><category/><description>We are deprecating the php8 tag/branch of our Nextcloud container. The latest tag (master branch) now uses php8.</description><content type="html"><p>We are deprecating the <code>php8</code> tag/branch of our <a href="https://github.com/linuxserver/docker-nextcloud">Nextcloud container</a>. The <code>latest</code> tag (master branch) now uses php8.</p></content></item><item><title>Notification: Significant changes to nginx based images</title><link>https://info.linuxserver.io/issues/2022-08-20-nginx-base/</link><pubDate>Sat, 20 Aug 2022 18:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2022-08-20-nginx-base/</guid><category/><description>Most images using our alpine-nginx base image are being updated to alpine 3.15 with php8 and some significant changes to the nginx configs.
|
|
Changes you will likely notice:
|
|
Bring our default shipped configs as close as possible to alpine upstream defaults https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.15-stable Include worker_processes.conf and init script to generate it in the base Include resolver.conf and init script to generate it in the base Include ssl.conf in the base (the same as what is currently shipped in SWAG, but adjusted to use the self-signed certs generated by the base) include /config/nginx/site-confs/*.</description><content type="html"><p>Most images using our alpine-nginx base image are being updated to alpine 3.15 with php8 and some significant changes to the nginx configs.</p>
|
|
<p>Changes you will likely notice:</p>
|
|
<ul>
|
|
<li>Bring our default shipped configs as close as possible to alpine upstream defaults
|
|
<ul>
|
|
<li><a href="https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.15-stable">https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.15-stable</a></li>
|
|
</ul>
|
|
</li>
|
|
<li>Include <code>worker_processes.conf</code> and init script to generate it in the base</li>
|
|
<li>Include <code>resolver.conf</code> and init script to generate it in the base</li>
|
|
<li>Include <code>ssl.conf</code> in the base (the same as what is currently shipped in SWAG, but adjusted to use the self-signed certs generated by the base)</li>
|
|
<li><code>include /config/nginx/site-confs/*.conf;</code> with <code>*.conf</code> extension (rename existing user files automatically)</li>
|
|
<li>Rework <code>default.conf</code>
|
|
<ul>
|
|
<li>Expect applications inside containers to exist at <code>/app/www/public/</code>, and if that does not exist, use <code>/config/www</code></li>
|
|
<li>Include ipv6 support</li>
|
|
<li>deny access to <code>.htaccess</code>/<code>.htpasswd</code> files</li>
|
|
<li>adjust php location and <code>fastcgi_params</code> to use <code>PATH_INFO</code> and mitigate <code>HTTP_PROXY</code> vulnerability</li>
|
|
</ul>
|
|
</li>
|
|
<li>Restructure nginx configs
|
|
<ul>
|
|
<li>Configs in <code>/defaults/nginx/</code> are recursively copied to the user&rsquo;s <code>/config/nginx/</code> (maintaining the structure)</li>
|
|
<li>All configs are now named <code>*.sample</code> and all include <code>## Version YYYY/MM/DD - Changelog: &lt;url to repo history&gt;</code> used by <code>/etc/cont-init.d/85-version-checks</code>
|
|
<ul>
|
|
<li>Required configs (<code>/config/nginx/nginx.conf</code>, <code>/config/nginx/server-confs/ssl.conf</code> and <code>/config/nginx/site-confs/default.conf</code>) are enabled by default. Downstream images can include and/or enable others as needed (ex: SWAG will enable <code>/config/nginx/location-confs/proxy.conf</code> and <code>/config/nginx/server-confs/502.conf</code>)</li>
|
|
</ul>
|
|
</li>
|
|
<li>Folder structure is as follows (in the <code>/config/nginx/</code> context):
|
|
<ul>
|
|
<li>All nginx based images:
|
|
<ul>
|
|
<li>Includes <code>nginx.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>resolver.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>ssl.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>worker_processes.conf</code> (enabled by default)</li>
|
|
<li><code>/config/nginx/site-confs/*</code> included inside the <code>http</code> context in <code>/config/nginx/nginx.conf</code>
|
|
<ul>
|
|
<li>Includes <code>default.conf</code> (enabled by default)</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>SWAG:
|
|
<ul>
|
|
<li>Includes <code>502.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>authelia-location.conf</code></li>
|
|
<li>Includes <code>authelia-server.conf</code></li>
|
|
<li>Includes <code>ldap-location.conf</code></li>
|
|
<li>Includes <code>ldap-server.conf</code></li>
|
|
<li>Includes <code>proxy.conf</code> (enabled by default)</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<p>Under the hood:</p>
|
|
<ul>
|
|
<li>Split out init scripts
|
|
<ul>
|
|
<li><code>root/migrations/01-nginx-site-confs-default</code> migrate existing <code>default</code> to <code>default.conf</code></li>
|
|
<li><code>root/etc/cont-init.d/11-folders</code> creates all the folders needed in <code>/config</code></li>
|
|
<li><code>root/etc/cont-init.d/12-samples</code> removes existing <code>*.sample</code> files from <code>/config/nginx</code> and copies any included <code>*.sample</code> files from the image</li>
|
|
<li><code>root/etc/cont-init.d/13-nginx</code> enable required configs (<code>nginx.conf</code>, <code>ssl.conf</code> and <code>default.conf</code>) if they don&rsquo;t exist, setup <code>dhparams.pem</code>, setup <code>resolver.conf</code>, setup <code>worker_processes.conf</code></li>
|
|
<li><code>root/etc/cont-init.d/14-php</code> configure php</li>
|
|
<li><code>root/etc/cont-init.d/15-keygen</code> create self signed certificates for <code>ssl.conf</code></li>
|
|
<li><code>root/etc/cont-init.d/20-permissions</code> set <code>/config</code> permissions</li>
|
|
<li><code>root/etc/cont-init.d/85-version-checks</code> check all enabled <code>*.conf</code> files against all <code>*.sample</code> files shipped with the image and alert the user about updates</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<p>Status of affected images:</p>
|
|
<table>
|
|
<thead>
|
|
<tr>
|
|
<th>Image</th>
|
|
<th>Branch</th>
|
|
<th>PR</th>
|
|
<th>Notes</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td>baseimage-alpine-nginx</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-baseimage-alpine-nginx/pull/84">https://github.com/linuxserver/docker-baseimage-alpine-nginx/pull/84</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>bookstack</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-bookstack/pull/113">https://github.com/linuxserver/docker-bookstack/pull/113</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>cops</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-cops/pull/34">https://github.com/linuxserver/docker-cops/pull/34</a></td>
|
|
<td>composer downgraded to v1 for compatibility</td>
|
|
</tr>
|
|
<tr>
|
|
<td>diskover</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-diskover/pull/43">https://github.com/linuxserver/docker-diskover/pull/43</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>dokuwiki</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-dokuwiki/pull/43">https://github.com/linuxserver/docker-dokuwiki/pull/43</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>freshrss</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-freshrss/pull/40">https://github.com/linuxserver/docker-freshrss/pull/40</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>grav</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-grav/pull/9">https://github.com/linuxserver/docker-grav/pull/9</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>grocy</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-grocy/pull/52">https://github.com/linuxserver/docker-grocy/pull/52</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>heimdall</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-heimdall/pull/79">https://github.com/linuxserver/docker-heimdall/pull/79</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>librespeed</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-librespeed/pull/15">https://github.com/linuxserver/docker-librespeed/pull/15</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>lychee</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-lychee/pull/51">https://github.com/linuxserver/docker-lychee/pull/51</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>muximux</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-muximux/pull/26">https://github.com/linuxserver/docker-muximux/pull/26</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>nextcloud</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-nextcloud/pull/219">https://github.com/linuxserver/docker-nextcloud/pull/219</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>nginx</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-nginx/pull/79">https://github.com/linuxserver/docker-nginx/pull/79</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>photoshow</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-photoshow/pull/28">https://github.com/linuxserver/docker-photoshow/pull/28</a></td>
|
|
<td><a href="https://info.linuxserver.io/issues/2022-10-14-photoshow/">Deprecated</a></td>
|
|
</tr>
|
|
<tr>
|
|
<td>phpmyadmin</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-phpmyadmin/pull/12">https://github.com/linuxserver/docker-phpmyadmin/pull/12</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>piwigo</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-piwigo/pull/49">https://github.com/linuxserver/docker-piwigo/pull/49</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>pixapop</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-pixapop/pull/11">https://github.com/linuxserver/docker-pixapop/pull/11</a></td>
|
|
<td><a href="https://info.linuxserver.io/issues/2022-10-14-pixapop">Deprecated</a></td>
|
|
</tr>
|
|
<tr>
|
|
<td>projectsend</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-projectsend/pull/22">https://github.com/linuxserver/docker-projectsend/pull/22</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>snapdrop</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-snapdrop/pull/6">https://github.com/linuxserver/docker-snapdrop/pull/6</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>snipe-it</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-snipe-it/pull/28">https://github.com/linuxserver/docker-snipe-it/pull/28</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>swag</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-swag/pull/169">https://github.com/linuxserver/docker-swag/pull/169</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>xbackbone</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-xbackbone/pull/5">https://github.com/linuxserver/docker-xbackbone/pull/5</a></td>
|
|
<td></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<p>Any images with notes above may not be merged. We will make efforts to update this page if any of the images with notes above are merged at a later date. We may also make individual announcements about status updates regarding these images.</p></content></item><item><title>New Container: Nextcloud</title><link>https://info.linuxserver.io/issues/2017-03-07-nextcloud/</link><pubDate>Tue, 07 Mar 2017 00:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2017-03-07-nextcloud/</guid><category/><description>We have released a new container for Nextcloud!
|
|
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.</description><content type="html"><p>We have released a new container for <a href="https://github.com/linuxserver/docker-nextcloud">Nextcloud</a>!</p>
|
|
<p><a href="https://nextcloud.com/">Nextcloud</a> gives you access to all your files wherever you are.</p>
|
|
<p>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.</p></content></item></channel></rss> |