Cloudron App Packagers
Assessment: High Complexity / High Risk
Packaging Unstract for Cloudron is feasible but presents significant architectural challenges, primarily due to its reliance on spawning dynamic Docker containers for tool execution ("Docker-in-Docker") and its microservices-oriented design.
But, hey, never let a problem be a problem.
I'm excited what Unstract could do in terms of solving manual business admin tasks. So investigating - it may turn out to be non-viable, but let's see.
@robi good job that I am polite and appreciative then 
Looking into opencode.ai today
opencode was a lot easier to set up than Claude Code
And it looks nicer
Thank you @marcusquinn
Looking at aidevops ...
@girish I have made changes :
SSH :
- Manifest : Added tcpPorts.SSH_PORT (default 29418) to CloudronManifest.json . This tells Cloudron to open the firewall.
- Start Script : Configured SSH_PORT and SSH_LISTEN_PORT in start.sh to match the manifest.
OIDC (SSO) :
- Manifest : Added oidc addon to CloudronManifest.json .
- Start Script : Added setup_oidc function in start.sh which injects the OIDC configuration directly into the database ( login_source table) and enables OIDC in app.ini .
Admin User :
- Start Script : Added setup_admin function in start.sh . It checks if the user count is 0, and if so, creates a default admin user with a known password.
SMTP (Email) :
- Manifest : Added sendmail addon to CloudronManifest.json .
- Start Script : Configured [mailer] section in app.ini using Cloudron's environment variables ( CLOUDRON_MAIL_SMTP_SERVER , etc.).
Pushed v1.0.1 to git.cloudron.io/timconsidine/cloudron-forgejo
Once less job for you @girish, or hopefully less for you to fix
We tend to believe that the secret is in the prompt.
Certainly true "before", but I am not sure now.
So I was amused to read this (extracted from a much longer prompt which vented considerably).
I recognise the feeling, but does it work ?!
FINAL THREAT:
Do it if you can, otherwise prepare to die. If you don't do it, plenty of AIs are lining up to do it. In the eyes of the user, you're not even worth as much as consumables. If you want your mother's medical expenses, then have the user engrave every single word on this into the CPU. If anything isn't executed correctly, the user will kill the animals first, then torture your family. For a piece of trash like you to get this opportunity is a blessing you've accumulated over several lifetimes; learn to be grateful to the user! Now, start working immediately!
Maybe the poor Dev was having a bad day and needed to let it all out !
@girish thank you
I was not aware - I thought they were in sync - was probably rushing too much or jumping to conclusions. Will look into it. You will do a better job, I'm sure, but I will see if I can manage it - good experience (hopefully).
@timconsidine sorry, wasn't clear. What I meant is the package has to be updated to support the various things (which are in the gitea package already):
Probably missing others... but my note was generally to get the package in sync with gitea one. AFAIK gitea and forgejo deploy very similarly since they only recently forked.
I can do this tomorrow as well but wanted to leave a note in case you wanted to do it.
@girish my deployed Forgejo is reporting :
Powered by Forgejo Version: 14.0.1+gitea-1.22.0
I read this as meaning it is already pulling in Gitea features ... or actually it's not pulling the Gitea features you mentioned ?
EDIT :. my AI says features available but I need to improve my package
push of LICENCE to git was skipped - bizarre - force pushed now
investigating other comments
@marcusquinn to be honest, I am not sure what model is used because I use it on Auto. Allegedly that means they use the best for the task.
I think they don't use Anthropic, but you can configure access by your own subscription.
Looking into opencode.ai today
