Postiz - Cloudron Community App

[BrutalBirdie]

Since Postiz is no longer in the Cloudron app store I forked the old package and created a community app.

️ WARNING | NO SUPPORT FROM ME! ️

I will not provide any support for the Postiz community app.
The app will be kept updated by my GitHub Workflow and when it breaks, it breaks.
And when it breaks, I will only fix it when I feel like it.
Anyone else who want to contribute on GitHub, feel free.

Minimal Postiz Support, here is the link to the docs: https://docs.postiz.com/self-host/providers/

[timconsidine]

@BrutalBirdie well done and thank you.
I started using Postiz but ceased when there were issues (twitter limitation?) and removal from official App Store was mooted.

Your post raises one extra thought.
Forum posts age and get ignored.
I wonder if there is a case for tagging Community Apps as "maintained" (maybe leaving unmaintained as silent opposite).
But @james might have nightmares about the thought.
We probably want to avoid "badge soup" and extensions to CloudronVersions.json which muddy the water for devs.

Maybe simplest is app publishers use existing "tags" but as well as "app type" (productivity, AI, business, files, whatever), we also have "status type" tags like "maintained", "best efforts fixes only", "report an issue and I will fix it in 2 hours".
Yeah, well, maybe not the last one.

Ooh, another thought, can we put emoji or emoticon in a CloudronVersions file ? Must try it sometime.

[james]

@timconsidine said:

Ooh, another thought, can we put emoji or emoticon in a CloudronVersions file ? Must try it sometime.

Please don't.. (=
I think we never tested for that or even thought about it.

@timconsidine said in Postiz - Cloudron Community App:

I wonder if there is a case for tagging Community Apps as "maintained" (maybe leaving unmaintained as silent opposite).
But @james might have nightmares about the thought.
We probably want to avoid "badge soup" and extensions to CloudronVersions.json which muddy the water for devs.

Maybe simplest is app publishers use existing "tags" but as well as "app type" (productivity, AI, business, files, whatever), we also have "status type" tags like "maintained", "best efforts fixes only", "report an issue and I will fix it in 2 hours".
Yeah, well, maybe not the last one.

Maybe a custom "support" badge in the CA is a good idea.
Also, we could add that CA apps that have not been updated in $N time they get marked as 'stale' or something.
That also brings up a whole other rats tail. What to do with a community app that is abandoned?
If someone else wants to take over and continue giving support they would have to maybe fork stale repo, we would have to remove the stale CA app and then the new maintainer could publish their CA app.
When it comes to that, we will figure something out.

[timconsidine]

Please don't.. (=

Ok !

I thought tags might help in the Postiz case : @brutalbirdie could just add a tag "unsupported".

I also thought about time-based-update status checks.
But if you take example of my Facilmap app, it's not been updated (except eMudhra in case) and doesn't change, no upstream releases and it's in daily use. A low-maintenance workhorse. I don't think marking it as stale would be fair or useful to any who do use it.
There will be many other similar cases. Maybe a packager's "touch update" could defeat the auto-stale, but it's more work just to side-step an event.

Abandoned apps : yes, a problem to think about.

Ooops, I am at risk of hijacking the topic. Will continue elsewhere if needed.

[BrutalBirdie]

Maybe similar to:

an optional support link? That can point to anything. A forum post, a website, a form to request paid support, what ever.
Like that:

Might be the most flexible way of doing that.

[jdaviescoates]

@BrutalBirdie said:

️ WARNING | NO SUPPORT FROM ME! ️

I will not provide any support for the Postiz community app.
The app will be kept updated by my GitHub Workflow and when it breaks, it breaks.
And when it breaks, I will only fix it when I feel like it.
Anyone else who want to contribute on GitHub, feel free.

Minimal Postiz Support, here is the link to the docs: https://docs.postiz.com/self-host/providers/

I think that's all fair enough, but TBH I think it probably ought to also be re-iterated over on https://ca.cloudron.io/app/io.github.brutalbirdie.postiz too