Cloudron Forum

@james said: @robi said: It would be nice if they could be hosted by the local registry app. The docker images? That should already work and is close to my above suggestion with a private registry. You'd just need to configure the docker registry in the Cloudron dashboard under /#/docker. I believe what @robi meant is to be able to store the CloudronVersions.json in a registry, much like what authentik does with blueprints.

@Lanhild said: Updating the Cloudron CLI did the trick. That is correct. The current latest version of the cloudron cli is 8.0.2. Your stated cli version is 6.0.0, two mayor versions behind.

@james Thanks for the insight. As this is a production server, I'll wait for the update. Regards.

@girish IMO, the version information wouldn't matter for a notification email. I'd just like to know when a manual updates required

@girish automatic schema validation by the IDE

@girish Increasing the task memory did it. Issue solved.

@Lanhild You should really consider switching to https://github.com/zabbix/zabbix (Number of monitors: 170)

With this line from the start script: https://github.com/Lanhild/atuin-cloudron/blob/39e0d6de54742833091cd3b373338b78e588d232/start.sh#L15 Users don't have the ability to disable signup without having a rebuild of the container. Its probably better to use export ATUIN_OPEN_REGISTRATION=${ATUIN_OPEN_REGISTRATION:-false} instead and additionally define it with ATUIN_OPEN_REGISTRATION=true in your env.sh. This way after the first install signup is available and after you created your accounts you can easily shut it down.

Awesome! Thanks for sharing! ️ would be great if cloudron added it as an offical app.

@nebulon Yeah, it does work. What I meant was that it doesn't work for some clients, even though they are indeed connected to a network. I used to believe it was an issue on the client side, but the fact that it works on another typebot Cloudron instance for the clients is what makes me believe it comes from the server.

@girish Yes please, this'd be appreciated.

@robi was actually a parameter in the startup file. It's all updated in my repo that I've linked previously in this topic.

@james I haven't tried to make the modifications suggested since then, but i have good reasons to believe it'd work.

On a brand new DO Ubuntu server, the first pull fails. root@my:~# TOKEN=$(curl "https://auth.docker.io/token?service=registry.docker.io&scope=repository:ratelimitpreview/test:pull" | jq -r .token) curl --head -H "Authorization: Bearer $TOKEN" https://registry-1.docker.io/v2/ratelimitpreview/test/manifests/latest % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 5429 0 5429 0 0 17471 0 --:--:-- --:--:-- --:--:-- 17512 HTTP/1.1 200 OK content-length: 527 content-type: application/vnd.docker.distribution.manifest.v2+json docker-content-digest: sha256:c2d41d2ba6d8b7b4a3ffec621578eb4d9a0909df29dfa2f6fd8a2e5fd0836aed docker-distribution-api-version: registry/2.0 etag: "sha256:c2d41d2ba6d8b7b4a3ffec621578eb4d9a0909df29dfa2f6fd8a2e5fd0836aed" date: Sat, 14 Dec 2024 15:41:35 GMT strict-transport-security: max-age=31536000 ratelimit-limit: 100;w=21600 ratelimit-remaining: 0;w=21600 docker-ratelimit-source: 2604:a880:2:d1::

@JOduMonT is the reranker using ollama or with Jina api?

Things often resolve AFTER posting. Weird.

Oh wow, lots of changes! Let us know if you need anything.