Problems with "Complex setup"

[gibelium]

First of all thank you for your work...

Since three days I am trying to setup nextcloud-docker-dev with master and the two stable branches stable27 and stable28. I followed the instructions closely but when I start stable27 or stable28 I always get a nextcloud instance with version "Nextcloud Hub 7 (29.0.0 dev)"

Am I missing something?

[juliusknorr]

The containers should be reachable in parallel to the existing nextcloud.local at stable27.local and stable28.local (given you have setup those entries in your /etc/hosts).

Maybe you can also double check the output of docker inspect [containerid-stable27] for the volume mapping to /var/www/html, it should point to your local worktree directory of stable27 then.

[juliusknorr]

Strange, your version.php shows the state of the master branch

[gibelium]

What options do I have?
Do you have an idea why this happened?
Is there a manual fix for this?
Can I provide more information regarding my installation so that you will be able to investigate why this happened?

[juliusknorr]

I have no explanation why your stable27 branch has that state of version.php. I assume git status has no changes listed? You could try to reset the local branch to origin/stable27 git fetch && git reset --hard origin/stable27 in your stable27 checkout and double check the version.php afterwards. Then you can destroy the running containers and bring them up again with docker-compose down -v and docker-compose up -d stable27 proxy

Otherwise I would probably try to start from scratch and document the full commands you did. So far I've not seen any similar report.

[gibelium]

I did a new clean install and now the version.php file of the server and stable27 instances are containing the correct Nextcloud version. When I try to start stable28 it keeps saying no such service: stable28.

If I remember correctly I adjusted the git worktree add ../stable27 stable27 command because I thought that a simple "." would work when I am already in the stable27 directory. This could have messed things up.

In addition I need to enter the password during the login twice in all instances (stable27 and server). Entering the correct password the first time the login fails.

[juliusknorr]

All right, thanks for the update. For the stable28 container please make sure to update the repository as it was just added recently (#249 )