Hi all,
I wanted to try out an app in my juliusknorr dev environment, which requires the Team Folder (groupfolders) app to work. Initially, I installed it successfully, but I disabled it off because it broke the Files app. Then I wasn’t able to enable the app again, because my Nextcloud version was too high.
So I tried a completely fresh install, deleting containers and volumes. Also, I wanted to try out the stable33 image instead of the nextcloud container to see if that would make a difference. I keep getting this message, when I load up the browser:
🚨 Could not find a valid Nextcloud source in /var/www/html
Double check your REPO_PATH_SERVER and STABLE_ROOT_PATH environment variables in .env
These values seem to be fine when working with the nextcloud image, but apparently not when working with one of the stableXX images.
REPO_PATH_SERVER="/home/…/Documents/projects/nextcloud/docker-dev/workspace/server"
STABLE_ROOT_PATH="/home/…/Documents/projects/nextcloud/docker-dev/workspace"
Any thoughts on my original problem and on the docker problem?
EDIT on my original problem, the Team Folder app is not broken what I originally thought, but it breaks once I opt to generate test data in the app that uses the Team Folder app
Hello @mathemaat,
I use the environment a lot and it never failed me. Some bugs, ok but everything was fixable. So, I guess we can get that thing running in general on your machine.
Just to make sure, you did install the nextcloud-docker-dev environment of Julius and inside the workspace folder you cloned the server repo, correct? The bootstrap should set that up for you to have the workspace/server be the current master of nextcloud/server. If yes, go on. If no, we need to fix that.
You did create the workspace/stable33 workdir from the server repo? That is git workdir add ... inside workdir/server to check out a second working dir in the stableXX folder. You should see the corresponding sources.
I suppose here is a problem as the sources of NC are not available in the container.
Are all helper apps installed? Some apps (like viewer) are part of the official bundle but not part in the nextcloud/server repo. These need manual installation (e.g. under workspace/stable33/apps/... or if you want to play with 'em under workspace/stable33/apps-extra/...). You will probably have them already installed but just in case.
I hope, we can get the main dev env running first. Once this is running, I suggest (as you already started) to begin with a stable release (as we are rather close to a new release (33) and changes in master might not be propagated to all apps).
If we want to look into the actual problem, we should discuss separately, what you did and what exactly fails.
Chris
1 Like
The nextcloud image is working fine. It’s just the stable33 image that gives me trouble.
If I understand it correctly I need to manually clone a Nextcloud project in the workspace/stable33 directory. The workspace/server is automatically populated when I use the nextcloud image with the bootstrap script, but the same is not true for workspace/stableXX when I use a stableXX image.
It’s possible I’m (repeatedly) overlooking something, but I have the impression that this step is not documented anywhere yet.
Ok, it works now. 
cd ~/Documents/projects/nextcloud/docker-dev/workspace
git clone --branch stableXX https://github.com/nextcloud/server.git stableXX
cd stableXX
git submodule update --init
Then loading up a stableXX container lead to a working Nextcloud environment.
Well, sort of.
The idea is to do the following
cd ~/Documents/projects/nextcloud/docker-dev/workspace/server
git worktree add ../stable33 stable33
cd ../stable33
git submodule update --recursive
That way, you have a single git repo on your hard drive and you can check out all branches you need as worktrees.
To remove worktrees there is git worktree remove as well. See man git-worktree.
1 Like