Bluesky Personal Data Server

[sfeldkamp]

Hey everyone!

I've published this as a community app. Currently only a "testing" version (how does that work anyway?), so please don't add it to the Community Apps topic just yet. Would love to get some feedback on it and see if any issues are discovered.

https://github.com/sfeldkamp/cloudron-bluesky-pds

[timconsidine]

@sfeldkamp well done !

Is "testing" a valid entry in CloudronVersions.json publishState ? It's creative but I was under impression that it is 'published' or 'revoked', binary choice. But I might be wrong. It's all rather new !

I'd put it as 'published' and just not list it in the community apps category for now.

[robi]

It seems like they're all in alpha testing until they make it into the app store for beta testing.

[sfeldkamp]

@timconsidine

I got this in the output for the cloudron versions add --help command. But I couldn't say if it has any effect or if it's just informational. It doesn't stop anyone from installing the app. Not sure about whether it would trigger updates.

[girish]

@sfeldkamp @timconsidine 'testing' state marks the release (just that version and not the app itself) as 'unstable' (just like cloudron's own app store packages). UI wise: when you install such a version, it will give a warning. Behavior wise: cloudron won't automatically update the app to that version .

It's really an advanced use case. We copied our app store behavior 1:1 for the community apps.

[sfeldkamp]

@girish

Thank you for explaining! It doesn't appear to be working that way for installs. I don't see any visual indicator for the Community App when installing it, nor on the app after it's installed. Here is the link to the versions file.

https://raw.githubusercontent.com/sfeldkamp/cloudron-bluesky-pds/main/CloudronVersions.json

Let me know if I should cross post this to support as a bug report (or elsewhere). I haven't tested whether "testing" prevents an automatic update from being discovered.

[LoudLemur]

@shanelord01 https://forum.cloudron.io/topic/12472/please-use-this-template-to-make-an-app-wishlist-request

[LoudLemur]

Wandering Monster packaging report: Verdict: Don't package. Wrong category, wrong scale, wrong topology — the same shape of mistake as Wikibase and Wazuh.

https://paste.wanderingmonster.dev/?1b5e4e9d9d1fa26c#4USbgYxhMQ5DRq3gwyKc6wbegUHXe6QZtmVGp4axNZcK

[jdaviescoates]

@LoudLemur it's already packaged. I'm really not sure of the value of these reports, they appear to mostly be way off the mark.

[LoudLemur]

@jdaviescoates Thanks, I was just processing a batch of them, and didn't check carefully if they had been packaged yet.

One thing that would be useful is to find where these reports stray. If they are just noise, I will definitely stop the monster, but if they can be adjusted to be more helpful, I shall try that.

This one was particularly clear that it was a no-no, yet it manged to be packaged!