Cloudron Forum

Hello @phneutre Did you setup the wildcard alias according to the docs? https://docs.cloudron.io/packages/discourse/#incoming-email-setup For unique addresses per category, setup mail aliases for forum@YourMailDomain.TLD. For a category named offtopic, create a mail alias like forum@YourMailDomain.TLD. Create a wildcard mail alias * to choose any category name freely.

Hello @n8n users @brutalbirdie debugged this issue and found the issue. https://github.com/n8n-io/n8n/issues/26748#issuecomment-4031286237 We will update the Cloudron N8N app soon to fix this issue.

We solved this in the end by adding some clean up to the GitLab runner's after_script in our .gitlab-ci.yml file: before_script: - stat -c %m /tmp - du -sh /tmp - ls /tmp -la - export XDG_CACHE_HOME=$(mktemp -d) # Each job leaks files into the gitlab-runner's private /tmp after_script: - rm -rf $XDG_CACHE_HOME - du -sh /tmp - ls /tmp -la - find /tmp -mindepth 1 -maxdepth 1 -user gitlab-runner -exec rm -rf {} + - du -sh /tmp - ls /tmp -la We could see the files that got left over when we added the logging lines.

Hi, I see the fix has been merged and the latest update (1.13.2) was applied on my instance yet I cannot open my drive files maybe a workaround is needed to export our files and re-import them, I'm not sure what to do but it's frustrating to not access my files for a few weeks now. I'm sorry to ask again for support, but it's very annoying. Thanks in advance!

️ Critical limitation: The Cloudron Strapi package runs with a read-only /app/code filesystem. This means the Content-Type Builder is permanently unusable in production mode, and there is no supported way to deploy custom content types to it. Schema files cannot be written via transfer, push, or direct filesystem access. The only partial workaround is: build content types locally in dev mode → use strapi transfer --exclude files to push to production. However this only works if the schemas already exist on the destination, which they cannot, making it a circular problem. Directus (also available on Cloudron) stores its schema in the database rather than the filesystem, making it fully compatible with Cloudron's immutable package model.

Thanks for your reply! I guess we'll just keep the existing users on oidc then. Or maybe, if they're willing to, they can migrate manually. Most shares and other tools (collectives, calendars) are shared via groups, not link.

@odie kindly remind them again

it has changed its name to (I assume) deal with the patent issues https://docs.karakeep.app/administration/hoarder-to-karakeep-migration/

Still wish there was a way to self-host an annotating the web solution.

@davejgreen I have responded on support@ . Let's continue there and I will report back my findings here.

@girish IMO, the version information wouldn't matter for a notification email. I'd just like to know when a manual updates required

@lanhild I see. The mysql multipleDatabase feature was written initially for phabricator, which is now long gone. AFAIK, no app uses multiple mysql databases. Same for postgres (though maybe synapse matrix + the user auth is a candidate, not sure).

@andreasdueren There is now a cloudron sync push/pull which only uploads changed files . Work similar to rsync in the sense that it uses size+mtime to detect changes. It's not possible to use rsync binary itself. That requires either ssh or rsync daemon - neither is available in app containers.