N
Our recommendation is to use a data-only e-sim (eg silent.link) and ditch the phone number. If you need SMS for 2FA, just use a web provider such as crypton.sh
fyi, for calendar you'll need a caldav bridge, davX is available on Zap Store
On Zap Store you can also see what apps others are recommending / installing (and zap the devs directly)
We are happy to block the IP of any country implementing dangerous policies like this
No responsible adult should allow their kids to upload personal identity documents to random (or worse, mainstream) websites
curious if anyone has tried it / has any feedback?
https://github.com/etkecc/ketesa
Billed as the replacement for Synapse Admin..
Routstr is now available as a community app: https://raw.githubusercontent.com/Routstr/routstrd-auth/refs/heads/cloudron/CloudronVersions.json
You can plug routstr in as a model provider to an array of AI clients, such as Roo Code, Claude, Opencode, Cursor, etc. Just use the url (eg your.cloudron.domain) and the api key.
There is no web app, it's just an API server. To set it up, use the terminal on the server, or install it locally with bun install -g routstrd
Instructions: https://github.com/Routstr/routstrd-auth/tree/cloudron#cloudron
Note - you have a choice of models, and you pay for them using Bitcoin over the lightning network. To top up your balance, run: routstrd receive xxxx where xxxx is an amount in sats. This balance will be shared across all the users, so it's a great way to provide no-kyc AI to your team.
same issue here. Moving to 8gb worked. subsequently resizing back to 2gb or 4gb does not work.
8gb is pretty big!
After being dissatisfied with existing time tracking solutions, we built our own. It is now available for others to try, and we'd love to get your feedback. We have been using it in production for ~6 months. Features include:
The first user to log in becomes the admin. You can set roles by project (eg owner, manager etc) to allow scoped visibility into hours tracked, and you can configure usage alerts by project or customer using a matrix API key.
https://git.nostrdev.com/trakstr/cloudron-trakstr/raw/branch/master/CloudronVersions.json
We've bumped strfry to the latest version (1.1.0) and made it a community app
You can try it out here: https://git.nostrdev.com/stuff/cloudron-strfry/src/branch/main/CloudronVersions.json
Didn't get this notification. The blossom cloudron is an old version of blossom now. Will look at auth when we bump it up.
Hi Joseph - yes you can - we use these apps ourselves and plan to maintain them (until such time as someone else ever does)
I notice that BTC Pay link points to btc-core - there are actually two apps (some features in BTC Pay depend on BTC Core):
One instance of BTC Core can serve all instances of BTC Pay. You can also run BTC Pay without core, or using another instance of core.
Are there any tools to help validate a cloudronversions.json file? Put this together: https://git.nostrdev.com/stuff/cloudron-btcpay/raw/branch/main/CloudronVersions.json
But can't seem to figure out why it always says "Could not resolve CloudronVersions.json from URL"
ok - the versions.json is ready for btc core: https://git.nostrdev.com/stuff/cloudron-bitcoin-core/raw/branch/main/CloudronVersions.json
had to move it back to our own repo so that it could update the json as part of the pipeline (cloudron uses gitlab vs the runners being in gitea)
will do btcpay server next, in the coming days
@timconsidine - didn't realise this was ready, thanks for the docs pointer, it looks straightforward enough. Will get onto it asap! Which realistically will be this weekend or early next week.
BTC Core is v29 and it should not be updated. There were contentious changes added in v30, and to be pragmatic, it would be best to stick with v29 for the foreseeable future. This does not affect BTCPay Server.
About the community app release, can you give more details? What would need to happen?
BTC Pay Server should run independently of BTC Core (the core part is only needed when you set up the wallet within a shop). So if it is not responding, it is not due to Core.
using gosu does the trick, thank you
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama pull qwen3.5:35b
pulling manifest
pulling 900dde62fb7e: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 23 GB
pulling 7339fa418c9a: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 11 KB
pulling 9371364b27a5: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 65 B
pulling 606ad9f1ecbc: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 482 B
verifying sha256 digest
writing manifest
success
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama ps
NAME ID SIZE PROCESSOR CONTEXT UNTIL
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama ls
NAME ID SIZE MODIFIED
qwen3.5:35b 3460ffeede54 23 GB 50 seconds ago
nemotron-3-super:latest 95acc78b3ffd 86 GB 19 hours ago
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama serve
Couldn't find '/root/.ollama/id_ed25519'. Generating new private key.
Error: could not create directory mkdir /root/.ollama: read-only file system
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# gosu cloudron:cloudron bash -c 'HOME=/app/data/ollama-home ollama serve'
Error: listen tcp 127.0.0.1:11434: bind: address already in use
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# gosu cloudron:cloudron bash -c 'HOME=/app/data/ollama-home ollama ps'
NAME ID SIZE PROCESSOR CONTEXT UNTIL
qwen3.5:35b 3460ffeede54 25 GB 100% CPU 4096 4 minutes from now
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code#
Getting the following in a fresh install after downloading the model:
Setting the HOME variable does not help.
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama run qwen3.5:35b
Error: mkdir /root/.ollama: read-only file system