HumHub - social network software
-
replied to A Former User on last edited by
@atrilahiji Never stop never stopping! You're doing great!
-
replied to fbartels on last edited by A Former User
@fbartels Sure thing: https://git.atridad.dev/alt-ron/cloudron-humhub-app/-/tree/harden-app-code
Thanks! I'm convinced this is 1) impossible or 2) something so simple yet I have not noticed it somehow
-
@atrilahiji for me this works with
➜ cloudron-humhub-app git:(harden-app-code) git rev-parse --short HEAD 0b5df1c
Steps I tried:
- Install app (in debug mode, but only so that i could override and start the
start.sh
manually) - finished Humhub installation
- went into admin and selected modules
- installed a module
- activated a module
- no php error can be seen
- Install app (in debug mode, but only so that i could override and start the
-
@atrilahiji no, no changes at all. maybe some leftovers from a previous installation of yours?
Yes, you can run
cloudron install --debug
where then the init script is not run. you then need to exec into the app and run it manually. -
replied to fbartels on last edited by A Former User
@fbartels Oh weird yeah that works... no clue why it wouldn't work if the start.sh is run normally during an install...
IDK if you saw the same error but if I don't start in debug mode and switch to Recovery Mode, running start.sh results in a permission error for PHP again.
EDIT: Nvm I think I figured it out... -
@atrilahiji the modules directory does not exist at all in
/app/code
and then it fails at creating it in the first place. You have to prepare this in a similar way to https://git.atridad.dev/alt-ron/cloudron-humhub-app/-/blob/harden-app-code/Dockerfile#L78-80 where the folder symlink needs to already be created during docker build and then in start.sh you need to make sure that the folder and its default contents exist. -
This should work now: https://git.atridad.dev/alt-ron/cloudron-humhub-app/-/releases/0.8.0
Now to tackle updates. With everything we need in /app/data now it should be a piece of cake. Thanks for the help @fbartels !
-
Had a few dumb bugs, and here we are at 1.0.3. But hey it works. Now I know never to work on windows. The line endings being wrong fucked the package.
-
replied to A Former User on last edited by
@atridad I'm getting a cert error on your repo.
-
I've also been getting in the habit of storing my containers I built over on my gitlab registry. So that project should now have an image built for 1.1.0 of the package.