True, but Admin 1 does not look to be compatible with Grav 2 (which was made to work with Admin 2).
Further, at least from my understanding, there are other issues that arose for our site that would have been mitigated through the migration process.
@superhua whoops yes, my mistake. I put a wrong regexp. But I also found that all that 1.7.50.x releases have been removed upstream - https://discourse.getgrav.org/t/upgrade-to-grav-v1-7-50-9-not-working/29222/4 . I will revoke all the packages .
I have this working in both directions now!
The key was :
14 su www-data -c 'git config --global user.name ReachableCEO'
15 su www-data -c 'git config --global user.email charles@turnsys.com'
And I then created a page in grav and it synced up to my repo:
[image: image.png]
Thanks to everyone for the assistance!
Yes indeed, that's how I proceeded in the end. It worked fairly well.
BTW, I just came across the remote development feature of the Zed editor (https://zed.dev/docs/remote-development). Don't know if that could work in an app/code/ directory but if, it will make coding Grav easier.
@martinv It looks like Grav creates it's own backups by default there. You can change this in /admin/tools
The default is 5GB which matches your size! Technically, Cloudron already takes backups , so these backups are sort of redundant
[image: image.png]
@girish said in Multisite Support:
@JLX89 not yet! I think when the Grav CLI is updated, it would be easier to test things out a bit more.
That sounds great, thank you!
The package was initially made by @jimcavoli . It seems he initially packaged with LDAP but subsequently removed it - https://git.cloudron.io/cloudron/grav-app/-/commit/94f656384e6c808e5a2bbc59e944f587f5362382 . @jimcavoli do you remember why?
In my case I was installing the plugin via the webinterface.
To reset the permissions usually in all apps an app restart does this already. So maybe indeed a simply app restart fixes that.
