@robi didn’t find any when I tried to investigate. But since it’s pretty much stored in plain text on the other side I decided I may as well store it plain text on mine. Encryption and bridges/bots are just not a good fit

Perfect! Thanks for the quick answer.

@sponch Is everything working?

new! Updated to 1.0.1. codeberg.org/themeerkat/hecapte-cloudron:1.0.1 I added customization options: renaming sites, deleting sites, and specifying CORS(!) on registration. This should make it a lot easier to use.

This is a custom app based I am packaging on react-admin. I am currently just redirecting the user to {app}/logout on clicking logout. Any way to enable it for just the custom app?

Hi @scooke , To your question, I followed the instructions on the Garage website, and I added a near-copy of that documentation to the README in the package I've developed. This is all documented in the git repository for the package that I linked to. I have Garage running on my Cloudron instance, and was able to create buckets, add content, and even serve static web content from within those buckets. I'm sorry your prior experience with this did not work for you. I am now trying to do that in a way that it would be considered for inclusion as a standard package, if the Cloudron team thinks it is worthwhile. If they don't, perhaps I'll do it for myself.

@nebulon - Congrats on the release of version 9! One of my servers just updated and the new UI looks slick. When will we get to see a slick new XMPP app in the store?

Absolutely. That's an excellent and thorough answer, @james . Many, many thanks. Possible text: This add-on is intended for applications that already support OpenID Connect-based (OIDC) authentication. Apply this add-on to use Cloudron as an OpenID provider with an application that supports OIDC-based authentication. Possible improvement for proxyauth: The proxyauth add-on allows you to put an authentication wall in front of an application. This is useful in situations where the application has no authentication mechanisms of its own, or where there are features that you cannot easily turn off (for the general public), and you want to restrict access using Cloudron's built-in user and group management tools. I think the idea being that, in both cases, a bit more "why" might help. Either way, thank you. All of my questions are answered (including "oh, hey, there was an app packaging topic!").

Hello @LoudLemur @LoudLemur said in AI attempt at packaging anythingllm - problem with using demo: Now we want to find the install from custom source but can't see how. You need to use the cloudron cli tool to do that, or you could use the tool provided by @timconsidine https://ccai.appx.uk/ Your docker image of the custom app needs to be publicly available or in a private docker registry accessible by the cloudron server.

@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!