LAMP App - How to enable mod_expires.c ?

[M-arcus]

I am trying to enable the expires module for apache2.

But if I try to do it via /app/data/run.sh or via the repair-mode, it tells me that the Apache2 mod folder is read-only.

How do I enable this module?

[girish]

@M-arcus I have pushed a new release which enables the apache module.

Currently, there is no way to enable modules on the fly. It has to be part of the package. Since expires is fairly standard, I added it to the package itself. Otherwise, we have to investigate what's the best approach for this.

[M-arcus]

@girish Thanks for the quick update.

Maybe you can symlink the apache2 folder to a writable folder inside /app

[girish]

Have to think about that because I think modules require not just configuration but also code to be installed via apt.

[M-arcus]

A bunch of mods are already installed, but not activated.

I would separate this into:

• Activating already installed mods
• Installing and activating new monds

[chmod777]

@girish, any updates on installing apache modules in the cloudron LAMP stack?

I would like to try https://github.com/OpenIDC/mod_auth_openidc in it

[nebulon]

That might be a great idea if that works out. Just trying to get it up and running in the package. One question though is about the login redirect URI back to the app. Given that this package is very generic, I am not sure if we should define a route for callback on behalf of the app (which might make it hard to use depending on the actual app/code running in this lamp instance) OR the admin is required to manually add an OpenID client via the dashboard, instead of pre-provisioning that.

Any input here might help to decide on how to go about this.

[nebulon]

Using an example setup, this works fine. Now we just need to decide if we should auto-provision oidc credentials with a fixed redirect callback URI or not.

If we do not pre-provision it, the Cloudron access controls won't be applied