Cloudron Forum

An extremely old thread, but here goes.

My Radicale instance broke, tried to fix it, but realised that I never liked it much anyway. So looked at alternatives and found Baikal.

Now packaged and released as a Community App.
In your AppStore,

Enter when prompted : https://communityapps.appx.uk/cloudron-baikal/CloudronVersions.json

Brief info at https://communityapps.appx.uk

[ @James @community-apps ]

@jdaviescoates good luck with trying it, hope you like it.

I will fix the mobile responsive view, thanks for letting me know.

@ekevu123
if you have a startup.sh or other launch script, it is common to have the script touch /app/data/initialized during first setup, all setup inside a test whether .initialized is present or not.
If so, skip setup.
If not, then do setup.
Setup including key generation.

I haven't reviewed how you launch the app, so not sure how viable it is for you, but it's very common for other apps.

---

if [ ! -f /app/data/.initialized ]; then
  cp -a -n /app/code/defaults/config/. /app/data/config/ || true
  touch /app/data/.initialized
fi

Can't stop laughing
I got a little frustrated with one package.
AI error
I challenged it "robustly"
Its response ?

Very cheeky, since the login error was not creds, but paths set by AI.

My original Cloudron-Facilmap package has been re-packaged as a Community App, so available for installation through AppStore "Add a Custom App".
Prior to it being added in @community-apps, you can find it here :
https://communityapps.appx.uk

@jdaviescoates said:

I'd personally really like FacilMap - I think @timconsidine has packaged it but none of his many packages have yet made it into the new Community Apps, but presumably it won't take too much more work to get them in there...

Facilmap has been re-packaged as a community app.
Small delay as I attempt to build a publishing process.
Other apps will follow.
I have messaged @James about getting it added to the category.
In the interim, for my own organisation, I will put all my community apps here : https://communityapps.appx.uk

Thanks @girish

TBH, most people don't read docs despite all this

Yep, true

Soon there won't be any docs. AI coding agent utility will produce some illegible binary asset "cloudron.aifood", which another agent will use. We humans won't need to know or read anything.

Thanks @nebulon

maybe better some https://foo.bar/changelog link

nice idea, let me think about that.
testing my build script which makes it a mandatory input (to overcome my lack of discipline )

@murgero I'm with you

The bash build script I am building uses a parameter :
echo " -p 0 = install only, 1 = publish (revoke/add/push)"

If command has -p 0, it does cloudron install --image ....

If command has -p 1, it does cloudron versions add etc.

Not sure how it will work in practice, needs some real-world usage.

Trying to smooth my workflow for CommunityApps (w/o mentioning Safari ) ...

---

• given that CloudronVersions.json is, well, a JSON file, presumably we can edit it if needed, then give access (git repo, static site) ? 2 scenarios I've met are :
  • (a) cli revoke only revokes the last entry, user might want to revoke previous ones (parameter to specify which to revoke would be nice),
  • (b) docker image location might be wrong ... or moved ... and don't want to repeat build workflow

---

• publishing docs should make explicit a clear expected workflow (dangerous assumption that I have this correct), maybe with a pic for fast absorption w/o reading
  • do your dev
  • update CloudronManifest.json & CHANGELOG
  • do your build / push
  • run cloudron versions add
  • commit/post CloudronVersions.json
  • test / loop

---

• docs for CLI should explain more about 'cloudron build' and 'cloudron build build' (repeat words does my head in BTW, please don't )
• docs should make clear that 'cloudron build' will auto assign a tag if not provided ?

---

• CHANGELOG is great discipline ... but I am not disciplined :
  • presumably we can mock it out ("frig it" in AngloSaxon) to make 'cloudron versions add' work, ...
  • or better question, can we automate it (use a publish script to bump version in CloudronManifest.json, maybe with user input, replicate in CHANGELOG, do cloudron build, run cloudron versions add, commit to git, push CloudronVersions.json to static location), ...
  • or EVEN BETTER question, how do you as pro devs handle this ? I'm guessing not manually.

---

• can we please have some short options for things like :
  • '--build-arg <namevalue>' [maybe '-a' or '-arg' or '-ba']
  • '--repository' [maybe '-r' or '-repo'].
  • Even '-nc' for no cache and '-np' for no push (others are ok).

Although I guess they are probably in a script so maybe it does not matter.

Wow - thank you so much for taking the time to research like that
Weirdly I could not find how in Safari to do that (embarrassing)
So I threw teddy out of pram, closed safari, set Firefox as default, and it worked immediately after pressing ENTER
Thank you !
Not sure whether I will switch back.
I hate Chrome, as an experience but also in principle, don’t really like Firefox and am tired of “also-ran” alternatives.

Thanks again for taking the time to solve this

@james said:

We had to make this switch to also support passkeys and other future webauthn validations.

cool
understood

Thanks -@James and @girish
I held off manual creation of ~/.cloudron.json so as to test 7.1.1

% sudo npm install -g cloudron
Password:

changed 60 packages in 3s

17 packages are looking for funding
  run `npm fund` for details
% cloudron -V
7.1.1
% rm ~/.cloudron.json 
% cloudron login
Cloudron Domain (e.g. my.example.com): my.example.uk
Press ENTER to authenticate using the browser...

Browser (Safari) says :

Safari Can’t Open the Page

Safari can’t open the page “http://localhost:1312/callback?code=TG_GsgNBsyfaY66pc4HsIj7135uFiuY7xvNM896Qwwl&state=24225191912c03d1feae234a7335894e&iss=https%3A%2F%2Fmy.example.uk%2Fopenid”. The error is: “Navigation failed because the request was for an HTTP URL with HTTPS-Only enabled” (WebKitErrorDomain:305)

specifically : Navigation failed because the request was for an HTTP URL with HTTPS-Only enabled” (WebKitErrorDomain:305)

I don't see anything else in browser dev view console or network.

Laptop terminal times out with this :

file:///Users/username/.nvm/versions/node/v25.2.1/lib/node_modules/cloudron/src/helper.js:157
            reject(new Error('Login timed out after 2 minutes'));
                   ^

Error: Login timed out after 2 minutes
    at Timeout._onTimeout (file:///Users/username/.nvm/versions/node/v25.2.1/lib/node_modules/cloudron/src/helper.js:157:20)
    at listOnTimeout (node:internal/timers:605:17)
    at process.processTimers (node:internal/timers:541:7)

Node.js v25.2.1

Would it not be easier to support use of a token for cloudron login ?

% cloudron login --token ffb1bc87d9ef8127f41aae7a7f950xxxxxxxxxxxxxxxxxxxxx --server my.example.uk
Cloudron Domain (e.g. my.example.com): my.example.uk
Opening browser for authentication...

Browser involvement seems bit retrograde to me ...

I am using a CHANGELOG.md
But it needs content in style of :

[1.1.4]
* registry update on instance

Weird.
I upgraded my CLI installation to 7.1.0.
Cannot login from laptop terminal to my.example.com
Constantly throws me to browser localhost address which fails with a message .

Safari can’t open the page
“http://localhost:1312/callback?code=IkBfP7hAchXf7CuoLvZsd1SVOiAAVm7b17j1pY35no0&amp;state=4aa18a1e97cac91cc1391b53a03d4f95&amp;iss=https%3A%2F%2Fmy.example.uk%2Fopenid”.

some HTTP vs HTTPS issue

• on 9.1.3
• Switched the docker registry in my Cloudron dashboard
• Changed my cloudron instance user password (general rotation)
• uninstalled CLI
• deleted ~/.cloudron.json
• reinstalled CLI

I'm losing the plot.
Is this related to login change (see below) ?
Or to my Safari installation (other problems faced) ?

% cloudron login --help
Usage: cloudron login [options] [cloudron]

Login to cloudron

Options:
  -u, --username <username>  Username [will be removed after Cloudron 9.1]
  -p, --password <password>  Password [will be removed after Cloudron 9.1]
  -h, --help                 display help for command

@ekevu123 congratulations and thank you for doing this.
Will look further into it when back to a desk(top).

Stubborn dog-with-a-bone that I am, I did more research, and hopefully this can put to bed my diversion of the thread (sorry), and maybe help others with a similar use case / workflow objective to mine :

• Forgejo (official Cloudron AppStore) provides standard git source code functionality AND it has a built-in container registry functionality
• so no need to consider changes to the official docker registry app for public pulls
• forgejo supports private and public repos (which git.cloudron.io does not)
• forgejo supports public image pulls (like hub.docker.com) but also multiple private containers (hub.docker.com only allows 1)
• I can uninstall docker registry app and gitea/gitlab apps, multiple used for segregating cloudron community work from closed app dev, using Forgejo organization instead.

So the answer for my bandwidth-limited brain of 1 app for (almost) everything seems to be Forgejo (available today, no dev work).

However, @girish made valuable comment that hosting container images is a disk/network usage risk. Even for a small dev footprint like mine, this could be critical (let alone Cloudron scale).

I need to think & test out, but maybe Forgejo actions can automate container push to hub.docker.com, and do automated cleanup in the instance. So from dev point of view it's a single answer (Forgejo) with CI/CD offloading disk/network risks to hub.docker.com (or whatever).

@girish you're right.
I'll have to rethink strategy.
I was focussed on simplicity, single git platform and single image registry.
But I guess it's gonna have to be separate streams :

• A: community apps : git A plus Dockerhub
• B: other dev : git B plus private image registry
  Apologies if my ambitions for combining have confused the picture/discussion.

@girish does sharing creds / creating users gives full registry access ? Or a user (virtual or real) can be limited to certain repos?

—-
EDIT : the support for Community Apps is awesome.
Thank you again for doing this “non-priority” enhancement.
Totally ok with CloudronVersions.json living in source repo such as git.cloudron.io

But plan seems to break down without easy public docker image (2 registries is good for segregating but cumbersome in practice)

You already got it, but often proxyAuth is the simplest.