How to Start, Stop, and Update your NextCloud AIO instance via SSH/Command-line

[JordanPlayz158]

As I didn't find anything directly for this, I found the daily-backup script has ENVs for starting, stopping and updating containers so I went through the script and found out what it does and have come to share this information as I feel it is quite useful to be able to restart the container without going through a web browser, going to the main instance, logging in, admin area, AIO Interface (or taking down your apache container to be able to access AIO interface directly).

# Update mastercontainer
docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/UpdateMastercontainer.php                                                                                                         

# Update then Start containers
docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/StartAndUpdateContainers.php    

# Just start the containers
docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/StartContainers.php                                                                                                                                                                                                             

# Stop containers
docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/StopContainers.php

Based on the way the daily-backup script works, basically all the files in /var/www/docker-aio/php/src/Cron can be kind of used as a cli, I would prefer a more proper cli in the future or I hope it already exists and I entirely missed it and that this is unnecessary but if I missed it, could mean NextCloud docs have poor SEO or I wasn't able to formulate my searches clear enough

[szaimen]

Hi, see https://github.com/nextcloud/all-in-one#how-to-stopstartupdate-containers-or-trigger-the-daily-backup-from-a-script-externally

[JordanPlayz158]

Yes, I used that section to find the script which I read to get those commands, I don't see your point, there are times when you don't want to do a daily backup so I think having these commands be accessible/visible is important, perhaps you can do all of those with just messing with the environment variables but it just seems less straight forward than running the commands directly like I shown

[szaimen]

The mentioned script is exactly doing what you are looking for. A backup will only be created if you set the environmental variable accordingly.

[JordanPlayz158]

Hmmm, I guess that's fair, as I feel it is not as straight forward though, I will likely call the commands directly as I described in the guide. Thank you for explaining your logic though

[szaimen]

I would not recommend to do so as you risk breaking things - just have a look what the script does.

[JordanPlayz158]

I did look at what the script does, that is how I found the commands to start, stop, and update the containers, I appreciate the concern though.

[Sylvain303]

@JordanPlayz158 did you manage to accomplish "start/stop from ssh"?

Given what you mentioned here, I produced this too bash functions. Is it enough?
My ~nextcloud user/folder contains my customized docker-compose.yaml (👈️link to sample one) for AIO.

{
  docker exec nextcloud-aio-mastercontainer \
    sudo -u www-data php /var/www/docker-aio/php/src/Cron/StopContainers.php && {
      pushd ~nextcloud > /dev/null
      docker compose down
      popd > /dev/null
    }
}

aio_start()
{
  pushd ~nextcloud > /dev/null
  docker compose up -d && \
    docker exec nextcloud-aio-mastercontainer \
      sudo -u www-data php /var/www/docker-aio/php/src/Cron/StartContainers.php
  popd > /dev/null
}