nextcloud/all-in-one
1
1
Fork 0
mirror of https://github.com/nextcloud/all-in-one.git synced 2024-12-29 10:10:55 +08:00
Code Issues Projects Releases Packages Wiki Activity
all-in-one/manual-install
History
szaimen 201dfc67f3 fix removing clamav and onlyoffice correctly 
Signed-off-by: szaimen <szaimen@e.mail.de>
2022-08-25 12:20:06 +02:00
..
latest-arm64.yml Yaml updates 2022-08-21 12:16:25 +00:00
latest.yml Yaml updates 2022-08-21 12:16:25 +00:00
readme.md Update readme.md 2022-08-15 09:52:48 -05:00
sample.conf Yaml updates 2022-07-23 12:17:00 +00:00
update-yaml.sh fix removing clamav and onlyoffice correctly 2022-08-25 12:20:06 +02:00

readme.md

Manual installation

You can run the containers that are build for AIO with docker-compose. This comes with a few downsides, that are discussed below.

Advantages

  • You can run it without a container having access to the docker socket
  • You can modify all values on your own

Disadvantages

  • You lose the AIO interface
  • You lose update notifications and automatic updates
  • You lose all AIO backup and restore features
  • You need to know what you are doing, especially when modifying the docker-compose file
  • Probably more

How to use this?

First, install docker and docker-compose if not already done. Then simply run the following:

git clone https://github.com/nextcloud/all-in-one.git
cd all-in-one/manual-install

Then copy the sample.conf to a new file, e.g. cp sample.conf my.conf, open the new conf file, e.g. with nano my.conf, edit all values that are marked with # TODO!, close and save the file.

Now copy the provided yaml file to a docker-compose file by running on x64 cp latest.yml docker-compose.yml and on arm64 cp latest-arm64.yml docker-compose.yml.

Now you should be ready to go with sudo docker-compose --env-file my.conf up.

How to update?

Since the AIO containers may change in the future, it is highly recommended to strictly follow the following procedure whenever you want to upgrade your containers.

  1. Run sudo docker-compose --env-file my.conf down to stop all running containers
  2. Back up all important files and folders
  3. Run git pull in order to get the updated yaml files from the repository. Now bring your docker-compose.yml file up-to-date with the updated one from the repository. You can use diff docker-compose.yml latest.yml on x64 and diff docker-compose.yml latest-arm64.yml on arm64 for comparing.
  4. Also have a look at the sample.conf if any variable was added or renamed and add that to your conf file as well. Here may help the diff command as well.
  5. After the file update was successful, simply run sudo docker-compose --env-file my.conf pull to pull the new images.
  6. At the end run sudo docker-compose --env-file my.conf up in order to start and update the containers with the new configuration.

FAQ

Backup and restore?

If you leave NEXTCLOUD_DATADIR in your conf file at the default value of nextcloud_aio_nextcloud_data and don't modify the yaml file, all data will be stored inside docker volumes which are on Linux by default located here: /var/lib/docker/volumes. Simply backing up this location should be a valid backup solution. Then you can also easily restore in case something bad happens. However if you change NEXTCLOUD_DATADIR to a path like /mnt/ncdata, you obviously need to back up this location, too because the Nextcloud data will be stored there. The same applies to any change to the yaml file.

Obviously you also need to back up the conf file and the yaml file if you modified it.