Grav CMS

[girish]

@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 by www-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.

[yusf]

@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?

[girish]

Yup, exactly. Similar to gosu. For now, I pushed a simple doc page at https://cloudron.io/documentation/apps/grav/ . One can also do:

/usr/local/bin/gosu www-data:www-data bin/gpm install bootstrap4-open-matter

[A Former User]

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]

@jdmnt I see. Did you install the plugin using the CLI or via the Grav admin UI?

[JOduMonT]

@girish said in Grav CMS:

Did you install the plugin using the CLI or via the Grav admin UI?

My Bad; I thought I installed through the UI but apparently not, since I installed a second GravCMS and it didn't happened.

[JOduMonT]

@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 ?

[JOduMonT]

@JOduMonT ok I trick it by copying the plugin from another grav

[JOduMonT]

@girish I'm sorry but the update really botter me, I can't install this theme because it require an update

perhaps, since I'll use extensively this apps, maybe I should propose you to take over the control of this apps no ?

[yusf]

@JOduMonT There's always the option of installing Grav inside a LAMP app, which should give more freedom.

[fbartels]

@yusf or running your own version of the grav app.

[JOduMonT]

@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

[fbartels]

@JOduMonT said in Grav CMS:

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.

[girish]

Pushed the update out for Grav CMS and the admin panel. Are you able to install the other plugin now?