Has anyone tried using Claude Code / Ralph Wiggum to package Cloudron apps?

[marcusquinn]

The coding isn't really the hard part any more. The testing and decision-making still remains a human in the loop domain.

We're going in the right direction, though.

IMO it won't replace developers, it'll just mean developers move up the food chain for creating and managing value by guiding and overseeing coding and devops agents.

Testing and gotchya checking still remains reliant on human experience.

Plus, like flying, you always want to know there's a pilot with a stake in survival.

[robi]

This works because you're dealing with a pile of low quality training data.

This is why we use tons of water to flush sewage/dirt/etc until something we want (diamond/gold) is left over.

Subtractive process like a sculptor removing debris to reveal the statue within the rock.

Requires lots of filtering. Just like with Ralph Wiggum

[marcusquinn]

Reminder to use the context7 mcp in your vibe coding, as that will have the knowledge of all the latest cloudron documentation.

[robi]

@marcusquinn I wonder if @timconsidine uses it.

[timconsidine]

@robi / @marcusquinn I haven't been using context7 MCP but I probably should - not been using any MCP, but again I should - will add to my list - just tell my TRAE to go check docs.cloudron.io/packaging

[jdaviescoates]

@timconsidine said in Has anyone tried using Claude Code / Ralph Wiggum to package Cloudron apps?:

TRAE

https://www.trae.ai/ I presume?

[timconsidine]

@jdaviescoates yes, that's the one
there are others (previously used Windsurf)
But I like TRAE

[scooke]

@timconsidine That packaging link gives me a 404.... Ah, wait a minutes, context7 would just use the text that's under that link, correct? Like /addons, /cheat-sheet, /cli, /manifest, /publishing, /tutorial... and you just append the same command, use context7 at the end of the prompt in the Solo prompt box? I assume your prompt includes Cloudron somewhere. How verbose is it? Like, "Make an app following https://docs.cloudron.io/packaging/ for bookwyrm"? This stuff is fascinating.

[timconsidine]

@scooke I haven't got round to using context7 yet.

The packaging link was typed off the top of my head.
I think the main problem is that there is not a "root" page for the packaging docs. IMO Cloudron should create one.

Let me investigate a bit more later (fighting Zoneminder packaging at the moment)

[timconsidine]

@scooke I checked out context7 - looks good !
thank you @marcusquinn for bringing it to all our attention

easy sign up and a free plan for 1,000 requests per month (don't know how quickly that gets consumed in practice)

@scooke, it seems someone already ingested docs.cloudron.io into context7 (@loudlemur raised this previously, although I missed that post)

so there's effectively no setup to do. TRAE supports context7 from its Marketplace (no cost) and it seems context7 supports all the major coding assistants (if TRAE is not your thing).

I am using TRAE Pro plan, not the SOLO mode - thinking about subscribing for SOLO but currently the Pro plan Builder (now Builder with MCP option) is rocking it for me.

and yes, I'm guessing that a simple prompt in TRAE AI chat after adding the context7 MCP might work :
"use context7 to review cloudron docs and help me package bookwyrm (GitHub : github.com/<dev>/<app>) for deployment on Cloudron"

I will need to check it out further.
After my success with packaging 2 complex apps Zoneminder and Seafile, I'm keen to see what other "impossible" Wishlist items can be ticked off.

EDIT : and it would be wise to add a rule in your AI assistant to use context7 without asking :

Always use Context7 MCP when I need library/API documentation, code generation, setup or configuration steps without me having to explicitly ask.