Butterfly mind needed a new toy, so I packaged this. 
Well actually, it was nice find for a task I have to handle, so thought why not give it a go.
Testing it out, and if ok, will add to CustomAppGateway
Butterfly mind needed a new toy, so I packaged this. 
Well actually, it was nice find for a task I have to handle, so thought why not give it a go.
Testing it out, and if ok, will add to CustomAppGateway
@DualOSWinWiz said in CCAI : Cloudron Custom App Installer:
I spend 2 weekends and still not successful
Well, don't assume I will do better !
Have to finish my VAT return but will look at them afterwards
I was able to get a working package going pretty easily (subject to more testing).
Is this still available ? Seems not.
I've had to remove it temporarily from my CustomAppGateway catalogue. Very happy to put it back with updated repo/dcoker image links.
If you're not using OpenObserve anymore and have moved on, I might take a bashing at packaging it, because it is definitely useful and contender to replace my hosted Seq (incapable of self-hosting).
As part of testing installation of all apps in the catalogue, I discovered gremlins (such as what happens if a source repo becomes unavailable or project abandoned, as well some "bound-to-fail-eventually" parsing and other "cleverness").
So I refactored both projects to be simpler and more robust, which needed them to go down.
I probably should do another round of testing all listed apps install correctly. That's on the ToDo list. I think it is all working (ha ha ha, famous last words).
if you already installed CCAI-P, I strongly recommend you reinstall it from customappgateway.appx.uk 
Custom apps already installed should not need re-installation.
It's just the installers which have changed.
Public service announcement to minimise chance of pulling the rug from under @humptydumpty or others again 
Testing of all custom apps in catalogue reveal some stubborn issues on a couple of apps. So ...
Breaking changes to refactor CCAI-P and CustomAppGateway - they are going to go down for a short while 
Will post here when back up.
Pushed couple more fixes, continuing to test installation of every app
Fixed the issues reported by @humptydumpty
Going to test installation of every app in catalogue, which will take a little time, feel free to report any issues you find.
@humptydumpty let me try it here ....
@humptydumpty I finished the upgrade !
Apologies again that you got caught up in the middle of it
Attempting to be concise, I have completed changes to the CCAI environment.



Given Cloudron 9.1 upcoming support for custom apps, I am not planning any further major changes, just fixing any reported issues.
@humptydumpty sorry about your experience - heavy updates and and changed locations - mid-process of going live - almost done now - you might be running into the ecosystem update process.
I will update you when finished. Hopefully not long now
@crazybrad yep
- in my cautious approach I set up a dedicated address e.g. my-company-finance@app.domain.tld and forward manually/automatically emails to it, bot monitors email inbox and works only on those - not full primary email access
@robi good approach, but I suspect your neuro-plasticity far exceeds mine ! 
@crazybrad I have very similar thoughts & cautions.
I have a feeling that Agent Zero is much better than Openclaw, but I can't really say that until I have test Openclaw fairly. So continuing on the package "just in case" it can help me or others.
Click-bait heading but explanation :
Suffering from a tantrum (I blame it on low blood sugar), I decided that I have had enough of AI chat engines forcing me to compose longer messages using <shift>+<enter> because plain <enter> submits the message to the AI dev assistant.
Usually that causes a mal-formed request to the agent, before I have given all current instructions and relevant details. It's especially bad when I am asking for strategy advice, and it only gets half the relevant story.
While some chat UI's have handled this by allowing the user to choose what is the submit key, most haven't and most frustratingly, ALL the cores ones I use for dev haven't, and I get the impression never will.
It really slows down my flow.
So I decided there's only answer - disable the enter key !
I used a free utility https://karabiner-elements.pqrs.org to re-map the <enter> key to <space>. I could have totally disabled it, but I thought <space> is the safer option.
Now I will never send a message to an agent by mistake
, and I no longer care whether they fix this issue in future or not.

So how do I actually implement <enter> when I need to ?
I also re-mapped <enter> to a seldom used key (in my case <RightCommand> on Mac).
Is it a perfect answer ? Absolutely not.
Dies it prevent malformed submits ? Absolutely
I haven't yet bothered to configure key usage on a per-application basis, (in email I might want to keep normal <enter> usage).
Posting this in case you clever people have better solutions.
How have you solved it ?
It would probably be a good idea to have conventional use of <enter> key 
@girish thank you - very helpful - still digesting it.
Hoping to get my final "end of life" changes done today, which can allow CCAI-P to limp on until Cloudron in-platform functionality is tested, then turn the CCAI and CAG websites into digital tombstones.
No need for any rush - always happy for you to take your time to do a proper job (unlike my hashed together PoC).
House-keeping :

Improvements :
The Future :
I'm calling this a v1.0.0 package
I may add/tweak something later, but I'm now using this as a production tool.
Currently I like it more than openclaw (clawdebot, moltbot).
But returning to work on my package of openclaw, and will reconsider which is better when openclaw package is complete.
I really like Agent Zero support for Telegram, and a relatively easy addition of new skills and tasks using the /run xxx structure.
My testing and live usage has mostly been with my selfhosted Ollama instance which is configured with ollama cloud models (so large models run on ollama servers). Seems low cost and large power).
If you test with other providers and issues found, let me know.
It's a big image (3.9Gb), so make sure you have disk space. But it installs quite quickly.
Make you set memory for your installation quite high - I have 4Gb and maybe will bump a little higher for production use.
v0.1.12 : fixed searx issue, now using Brave Search API key
now pushed to git.cloudron.io/cloudron-agent0 and docker hub image tcmbp132021/cloudron-agent0:latest (aka v0.1.12)
@miednr I build all my apps using local device docker, push to a cloudron private registry and use cloudron install --image xxx.
I feel guilty in some way for not using Cloudron Builder, but local gets the job done fine, so good that you got your build out and deployed.