Grav CMS
-
Investigated this a bit and this is just a plugin related issue. https://github.com/jgonyea/grav-plugin-get-id3/blob/develop/get-id3.php#L174 is trying to install the get-id3 library and failing. It's unclear why because there is no logs about why it's failing. The workaround is to follow https://github.com/jgonyea/grav-plugin-get-id3#post-installation. Just need to:
cp -r /app/data/user/plugins/get-id3/tmp/extracted/getID3-1.9.15/getid3/* /app/data/user/plugins/get-id3/library
-
@girish Thanks so much for getting Grav on Cloudron! I've been having several issues which I think are related to permissions and I've posted the details at https://git.cloudron.io/cloudron/grav-app/issues/1
Happy to help test etc. if helpful.
Thanks again,
Paul -
@paulhibbitts The issue is related to permissions indeed. When you ran
bin/gpm install bootstrap4-open-matter
this installed the files as root. You have to make sure the files are owned bywww-data
user. You can fix this in two way:sudo -u www-data -- bin/gpm install bootstrap4-open-matter
Alternately, just restart the app (from Console -> Restart). Restarting the app will run the packages startup script again which fixes up the ownership.
-
@girish Is this similar to the
gosu
command used for the, say, NodeBB app? Please document it if you haven't already.I'm thinking there should be some wrapper command for each app that needs custom command line stuff like this so that the command looks and feels similar across apps. What do you think?
-
Hi @girish
I don't understand why but I after installing the plugins gitsync had to chown the plugins dir again
chown 33:33 -R /app/data/user/plugins
unless gitsync plugin was unable to save his configuration file
all the rest in /app/data/user was fine.
maybe a sticky bit could fix this
-
@girish a new version of Grav is out
I cant install plugin (such as autodate) because it required the new version
their is a way to bypass this, such as temporary removing the read-only option on the container do the update than putting it back ? -
@yusf and @fbartels Yes I could also run my own server as I was doing before and not participating to this community
@girish I was able to reproduce the issue with the permission in ./user/config/plugins by installing via the WebAdmin the theme: Quark Open Publishing so I believe sticking the permission would be a good idea
-
Yes I could also run my own server as I was doing before and not participating to this community
that was not at all what we were suggesting
But if you have special requirements or always immediately want to run the latest version if may be a benefit to look at the app source and simply deploy your own customised version. Your customisations and updates can then of course be made available via pull requests to the main app.