Deploying to gh-pages from @ mailcow/mailcow-dockerized-docs@f7224e9647 🚀
Dieser Commit ist enthalten in:
Ursprung
79e1edbda5
Commit
6748de1e92
4 geänderte Dateien mit 5 neuen und 5 gelöschten Zeilen
|
@ -2524,7 +2524,7 @@ Should you wish to access the web interface, as before by default via v6, please
|
||||||
<strong>The 2022-12 update will restore the native IPv6 reachability from the UI.</strong></p>
|
<strong>The 2022-12 update will restore the native IPv6 reachability from the UI.</strong></p>
|
||||||
</div>
|
</div>
|
||||||
<p>If you are freshly installing mailcow and have installed Docker in the above way, Docker Compose v2 will already be installed with it. So you don't need to do anything else.</p>
|
<p>If you are freshly installing mailcow and have installed Docker in the above way, Docker Compose v2 will already be installed with it. So you don't need to do anything else.</p>
|
||||||
<p>You can check this with <code>docker-compose version</code>, if the return looks something like <code>Docker Compose version v2.5.0</code>, then the new Docker Compose is already installed on your system.</p>
|
<p>You can check this with <code>docker compose version</code>, if the return looks something like <code>Docker Compose version v2.5.0</code>, then the new Docker Compose is already installed on your system.</p>
|
||||||
<p>If it is not installed or you want to upgrade from Docker Compose v1 to v2 just follow the instructions: </p>
|
<p>If it is not installed or you want to upgrade from Docker Compose v1 to v2 just follow the instructions: </p>
|
||||||
<h4 id="uninstall-docker-compose-v1">Uninstall Docker Compose v1<a class="headerlink" href="#uninstall-docker-compose-v1" title="Permanent link">¶</a></h4>
|
<h4 id="uninstall-docker-compose-v1">Uninstall Docker Compose v1<a class="headerlink" href="#uninstall-docker-compose-v1" title="Permanent link">¶</a></h4>
|
||||||
<p><strong>If you are already running the mailcow stack with docker-compose v1, make sure you have shut down the mailcow stack and installed the latest update before upgrading to Compose v2</strong>.</p>
|
<p><strong>If you are already running the mailcow stack with docker-compose v1, make sure you have shut down the mailcow stack and installed the latest update before upgrading to Compose v2</strong>.</p>
|
||||||
|
@ -2591,7 +2591,7 @@ docker compose up -d
|
||||||
<small>
|
<small>
|
||||||
|
|
||||||
Last update:
|
Last update:
|
||||||
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_datetime">2022-06-07 16:37:52</span>
|
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_datetime">2022-06-07 16:44:34</span>
|
||||||
|
|
||||||
|
|
||||||
</small>
|
</small>
|
||||||
|
|
|
@ -2524,7 +2524,7 @@ Should you wish to access the web interface, as before by default via v6, please
|
||||||
<strong>The 2022-12 update will restore the native IPv6 reachability from the UI.</strong></p>
|
<strong>The 2022-12 update will restore the native IPv6 reachability from the UI.</strong></p>
|
||||||
</div>
|
</div>
|
||||||
<p>If you are freshly installing mailcow and have installed Docker in the above way, Docker Compose v2 will already be installed with it. So you don't need to do anything else.</p>
|
<p>If you are freshly installing mailcow and have installed Docker in the above way, Docker Compose v2 will already be installed with it. So you don't need to do anything else.</p>
|
||||||
<p>You can check this with <code>docker-compose version</code>, if the return looks something like <code>Docker Compose version v2.5.0</code>, then the new Docker Compose is already installed on your system.</p>
|
<p>You can check this with <code>docker compose version</code>, if the return looks something like <code>Docker Compose version v2.5.0</code>, then the new Docker Compose is already installed on your system.</p>
|
||||||
<p>If it is not installed or you want to upgrade from Docker Compose v1 to v2 just follow the instructions: </p>
|
<p>If it is not installed or you want to upgrade from Docker Compose v1 to v2 just follow the instructions: </p>
|
||||||
<h4 id="uninstall-docker-compose-v1">Uninstall Docker Compose v1<a class="headerlink" href="#uninstall-docker-compose-v1" title="Permanent link">¶</a></h4>
|
<h4 id="uninstall-docker-compose-v1">Uninstall Docker Compose v1<a class="headerlink" href="#uninstall-docker-compose-v1" title="Permanent link">¶</a></h4>
|
||||||
<p><strong>If you are already running the mailcow stack with docker-compose v1, make sure you have shut down the mailcow stack and installed the latest update before upgrading to Compose v2</strong>.</p>
|
<p><strong>If you are already running the mailcow stack with docker-compose v1, make sure you have shut down the mailcow stack and installed the latest update before upgrading to Compose v2</strong>.</p>
|
||||||
|
@ -2591,7 +2591,7 @@ docker compose up -d
|
||||||
<small>
|
<small>
|
||||||
|
|
||||||
Last update:
|
Last update:
|
||||||
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_datetime">2022-06-07 16:37:52</span>
|
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-iso_datetime">2022-06-07 16:44:34</span>
|
||||||
|
|
||||||
|
|
||||||
</small>
|
</small>
|
||||||
|
|
Dateidiff unterdrĂĽckt, weil mindestens eine Zeile zu lang ist
BIN
sitemap.xml.gz
BIN
sitemap.xml.gz
Binäre Datei nicht angezeigt.
Laden …
In neuem Issue referenzieren