@nostrdev-com I've installed it, went smooth, and have even uploaded a blob. How do I make this private? I really don't want some random to upload nasty stuff! Here is some of my config: discovery: # find files by querying nostr relays nostr: enabled: true relays: - wss://relay.mynostr.com # - wss://nostrue.com # - wss://relay.damus.io # - wss://nostr.wine # - wss://nos.lol # - wss://nostr-pub.wellorder.net # find files by asking upstream CDNs # NOTE: do not set this to your own server, it will create an infinite loop upstream: enabled: true domains: - https://cdn.satellite.earth storage: # local or s3 backend: local # Imminently removes a blob when there are no owners removeWhenNoOwners: false # local storage local: dir: ./data/blobs # rules are checked in descending order. if a blob matches a rule it is kept # "type" (required) the type of the blob, "*" can be used to match any type # "expiration" (required) time passed since last accessed # "pubkeys" (optional) a list of owners # any blobs not matching the rules will be removed rules: # mime type of blob - type: text/* # time since last accessed expiration: 1 month - type: "image/*" expiration: 1 year - type: "video/*" expiration: 5 days - type: "model/*" expiration: 1 week - type: "*" expiration: 2 days upload: # enable / disable uploads enabled: true # require auth to upload requireAuth: true # only check rules that include "pubkeys" requirePubkeyInRule: false list: requireAuth: true allowListOthers: false tor: enabled: false proxy: ""

Many thanks, @james. The text was absolutely helpful. Also, that diff hint is gold. I may end up with a PR against the docs when I'm done, because that kind of hint is a nice trick to figure out quickly all the places an app touches the disk.

@joseph Yes, I thought I mentioned that just before the apache app.conf. It does. Thanks for chiming in!

Hi @girish, @nebulon, and team, I've updated the Typesense package to address the backup roadblock from the docs (https://typesense.org/docs/guide/backups.html#backup-steps). This should make it compatible with Cloudron's strategy for database-like apps. Key changes in v29.0.1: Added "localstorage" addon for persistent /app/data (includes DB files and snapshots). Defaulted data-dir to /app/data in start.sh. Added backup.sh to trigger a full server snapshot via /operations/snapshot API, saving to snapshots/latest.tar (relative to /app/data). It backs up all collections automatically and checks for success. Added restore.sh to untar latest.tar on startup if present, ensuring consistent restores. Improved logging for the API key in start.sh. Tested on my live install (search.daveswift.com with existing collections)—backup creates the snapshot file, and restore loads it on restart without issues. The snapshot is a complete dump of all data, per Typesense docs. Repo: https://github.com/clientamp/typesense-cloudron (changes on main, see CHANGELOG.md). Latest image: clientamp/typesense-cloudron:29.0.1 (or timestamped builds like 20250929-111100). For integration, Cloudron could run backup.sh via a hook before filesystem backup, then ignore raw DB files. Happy to add more (e.g., compression). Thanks!

@girish said in Matrix WhatsApp Bridge: "extensions" to apps by third parties is quite a burden for app packages. I understand that it needs to be feasible to maintain these kind of things. Cloudron needs to be profitable after all. I hope we can find some solution for these things, especially if they're simple go binaries like this one.

@scooke raises some valid points about user expectations, and I will freely admit that I am not sure where or how the line should be drawn. Conceptually there is indeed some friction between : user is not comfortable installing CLI tools and docker and using them, effectively setting a competence bar and edging them out of this activity making it easier to do what they're not comfortable with, effectively lowering that bar and inevitably encountering support requests if/when it becomes normal/easy to install unsupported apps (via @Kubernetes scripts, my tool or an official way) However I am clear on these points : installing custom apps should be easier (hence my app) : on one level, it's purely and simply a timesaver, e.g. for a user who is competent in installing apps, at least that's how I am using my tool currently nothing wrong in concept with Cloudron providing an official GUI for installing custom apps (Cloudron has already provided the CLI and know-how for non-gui) support line must be clear : Cloudron as a team/business are not responsible for custom apps (not supported, not maintained) if properly handled, easier installation of custom apps can reduce forum pressure on Cloudron team for new apps into the AppStore I like @scooke idea of a pop-up confirmation box or similar : clarity and disclaimer is good. Whether it goes as far as requiring a reboot of the Cloudron instance, I'm not sure. But I will add a disclaimer box to my app. Beyond that, it gets a bit unclear for me : does the packager provide support (my view : only optionally / voluntary / reasonable efforts) do packagers need a reputation score (my view : nice but not viable as a formal rating, who has time and authority to set these, instead maybe some unofficial star rating 1-5 from users with successful deployment of a custom app) can an installer for custom apps provide a monetisation mechanism (comment from @girish) which effectively incentivises packagers to work through the AppWishlist (my view : yes, it could, but it's another layer on-top) should support for installed custom apps be channelled (a) into an UNSUPPORTED category of existing Cloudron forum, or (b) very deliberately into a different forum (my view : B makes a point but A is easier and more natural) @scooke said in Installing custom Apps on Cloudron: Please do not turn Cloudron into another messy Yunohost. I agree 100% on this. It must definitely be the goal of any efforts in this area. Equally, IMHO, standing still is not an option. We have too many well-intentioned but actually not-our-business "lectures" about how Cloudron should expand, and also too many "please please please" requests, pointing to unmet user demand. We cannot be like King Canute trying to push the waves back.

Yes, thank you, this has worked perfectly!

Bumping to let people know I have not forgotten, its just been a busy summer for me!

@girish said in Install new custom app with environment variables?: @ekevu123 cloudron install --env ENV1=1 ENV2=2 --location subdomain . Then, you can verify using cloudron env list. Thank you! I think this is the best solution for this problem.

Thank you @James In the interim, I am attempting a workaround <can't find fingers-crossed emoji>

@girish thanks for looking into it all working now, so probably a glitch somewhere, not worth investigating further

I've my Last.fm account since 2010, but nowadays I'm also scrobbling to https://listenbrainz.org/ as a backup in case Last.fm dies. I also aim to make my own scrobbler/stats independently from ListenBrainz and Last.fm, taking inspiration from https://coryd.dev/posts/2024/tracking-the-music-i-listen-to and https://sive.rs/ti

Okay, thank you for the advise!