Cloudron Forum

@robi Short answer: no, not in the sense you mean. Infisical has no third-party extension mechanism. There is no equivalent of vault plugin register, no external plugin binaries, no stable interface for adding auth methods or secrets engines. The backend/src/server/plugins/ directory is just Fastify's internal module convention, and the Backstage / Airflow / varlock "Infisical plugins" you may run across are plugins for those systems that consume Infisical's API. Nothing extends the server itself. LDAP is also about the worst candidate for a community implementation, because of where it lives: backend/src/ee/services/ldap-config/, alongside the SAML and OIDC SSO services. Everything under ee/ is proprietary-licensed rather than MIT, and the self-hosted terms say Infisical retains rights over modifications and patches to it. You could write a clean-room LDAP auth method in the MIT half instead, which sidesteps the licence question, but it would never be merged upstream since it competes directly with the paid feature. That means maintaining a permanent fork of a codebase shipping several releases a month, and on Cloudron, building and tracking your own image forever. Worth separating two things though. What is gated is human SSO. Machine identity auth including OIDC is on the free tier, per the feature table in my first post, so machines can already federate against Keycloak or similar without a licence. It is only admin login to the Infisical UI that needs LDAP/SAML/OIDC. If you want a genuine plugin system with no open core, OpenBao is the honest answer: MPL 2.0, Linux Foundation governance, external plugin binaries in a separate repo, with LDAP auth, the SSH CA and dynamic secrets all included free. Not something you bolt onto Infisical, an alternative to it. We are currently packaging OpenBao for Cloudron and will hopefully make it available as a community application later.

Always good to check the logs for progress

@LoudLemur said in Forgejo Testing Feedback: Login with Cloudron Gitea had the same report a while back. I think this is hardcoded in the app and the app does not allow changing the OIDC provider name.

This is how one guy mods OSRM for his own use case:

I would like to change some of these already. I want to ask which apps they might like to package in the future, and also what we could do to encourage more packagers to try.

Librechat got acquired - https://clickhouse.com/blog/librechat-open-source-agentic-data-stack . Incoming ....

@jdaviescoates said in Cloudron update to 7.5.1 - Success!: @mhgcic said in Cloudron update to 7.5.1 - Success!: I could increase the RAM to see if that helps. Regardless if it is what's causing the issues you're currently facing, I'd definitely get more RAM if I were you. Each instance of Mastodon needs at least 1.5GB and each instance of Discourse at least 2GB. Already that is at least 10.5GB RAM you need before you've included all your other apps plus Cloudron and Ubuntu themselves. And these are bare minimums. If you have users actually actively using these apps they'll need more. We know this and monitor daily, and we have software that lets us know that RAM needs to be increased whether it is on a server level or on an app level. We upgrade as and when needed, We also use throttling so if extra RAM or CPU is needed it is given until we decide on its upgrade needs. After testing it had nothing to do with CPU or RAM it seems to be networking or a service possibly.

You are amazing to have solved this and fixed it so quickly, @nebulon. To get the typebots you were running working again, you can try this: Restore from an earlier working backup Navigate to your typebot flow and at the three dots at the top right .... export the flow. Save it in a safe place. Reinstall Typebot in Cloudron create a new typebot by selecting the import flow When you try and re-publish, it will give the typebot a new address, so you might like to edit that option to set it to your previously published address: [image: brave_bITJdJAtRT.png]

@timconsidine said in Cloudron Documentation Ideas: I find Cloudron documentation fine in its current form Cloudron has good quality documentation, I agree.

Alright, trying to strike a balance here, I moved Feature Requests up again, but I assume unless the forum supports a per-user order, this discussion is endless on personal perference

@LoudLemur ah ok, I didn't actually watch the video External links always worry me, thanks for clarifying.