Hello @chmod777 I have rebased the oidc-support branch against the master branch. You should be able to run git pull in the oidc-support branch now.

oK, Im not sure if I just fat fingered something or if this was fixed, but the yaml is now set up to be working. Here is my .yaml file name: Sync Repo with Cloudron LAMP app on: workflow_dispatch: push: branches: [main] jobs: deploy-to-cloudron-app: runs-on: ubuntu-latest environment: [WHATEVER YOUR ENVIRONMENT NAME WAS IN SETTINGS OF REPO] steps: - name: Checkout Repository uses: actions/checkout@v4 - name: Diagnostic – Print environment context run: | echo "=== GITHUB CONTEXT ===" echo "Branch: $GITHUB_REF" echo "Workflow: $GITHUB_WORKFLOW" echo "Runner: $RUNNER_NAME" echo "Workspace: $GITHUB_WORKSPACE" echo "======================" - name: Diagnostic – Check secret presence shell: bash run: | declare -A secrets secrets["CLOUDRON_FQDN"]="${{ secrets.CLOUDRON_FQDN }}" secrets["CLOUDRON_TOKEN"]="${{ secrets.CLOUDRON_TOKEN }}" secrets["CLOUDRON_APP_ID"]="${{ secrets.CLOUDRON_APP_ID }}" echo "Checking secrets..." for key in "${!secrets[@]}"; do if [ -z "${secrets[$key]}" ]; then echo "❌ $key is EMPTY" else echo "✅ $key is set" fi done - name: Cloudron Push to App uses: cloudron-io/cloudron-push-to-app@latest with: CLOUDRON_FQDN: "${{ secrets.CLOUDRON_FQDN }}" CLOUDRON_TOKEN: "${{ secrets.CLOUDRON_TOKEN }}" CLOUDRON_APP_ID: "${{ secrets.CLOUDRON_APP_ID }}" CLOUDRON_PUSH_DESTINATION: "/app/data" CLOUDRON_CREATE_APP_BACKUP: "false"

PHP 7.4 and 8.0 are removed in the latest package.

Thanks folks. I'll give that a whirl

@timconsidine said in Disable Strict Mode Mysql: @girish I thought our app cannot SET GLOBAL due to restricted permissions ? True / false ? My earlier comment seems to be a typo. I think I meant SET SESSION . ONLY_FULL_GROUP_BY cannot be disabled globally on Cloudron. It's a deprecated flag in MySQL and any code needing it is deviating from SQL standards.

Hello @charlesnw With this commit: https://git.cloudron.io/platform/docker-base-image/-/commit/2e4f7fd5fde83652567dd0a00a695f523bef98d1 yarn was removed from the docker base image. So yes, yarn is no longer included in any app by default.

Closed due to inactivity

Closed due to inactivity Note: Issue was resolved. If this ever happens to you, stop the backup, restart the server and re-run the backup.

@james said in Is this pip install persistent for app updates?: Hello @imc67 You can use venv or uv to create virtual environments. Here is a quick cheatsheet for venv => https://aaronlelevier.github.io/virtualenv-cheatsheet/ Many prefer uv these days, see => https://github.com/astral-sh/uv thanks again! I used venv and it works very well!

I couldn't resolve this but discovered that it isn't in fact as complicated as I thought it would be to migrate to the Freescout App. Just in case anyone else comes up against this challenge: Install and setup Freescout app Drop all the tables in the database and import database from previous installation If you have any modules: upload module folders to storage/modules Upload attachments folder to storage Done

@alejandrolengua have you already created the A record as instructed? If so it's probably just a matter of waiting for propagation like it says. Can be really quick, can take hours (or technically even days but that's pretty rare)

@scooke nod, I used cp -a * but forgot I also had to do .*

@BrutalBirdie Thank you for the incredibly comprehensive tutorial. It seems this guide is best suited for users with advanced knowledge, so I’ll need to take some time to study and understand every detail you’ve provided. Much appreciated! Thank you @joseph for the documentation reference. I'll look into it.

I am using Moodle inside LAMP App (and not directly the Moodle one) because I migrated an older version that was using PHP version 7.4 that I managed to upgrade using the terminal inside Cloudron.

Well done! Super easy @simong

Thank you Joseph - that helped a lot. Then, everything just works fine :).

@joseph Thank you, it works now! cc: @nebulon

AAannnnnd now it is working. I wish I could tell you why, but I don't. Thanks @robi

Hmm I still have permission denied inside the container to read /media/MyMount EDIT This time, it's working, for future reference, only thing I did was to set the home directory properly in the systemD service for each mount, remount them and then systemctl restart box or from the UI restart the box, my mounts are now visible inside the containers and I can read from them [image: 1734902378511-386b79d8-79cb-47db-8687-019194acef53-image.png]