@jadudm Thanks for your further input. It helps me forming a better understanding whatever the outcome of this discussion is. That packaging apps in general and maybe this one in particular has a resource cost (time, money etc..) is no doubt of mine. So I am already grateful for the time you, others, everyone is spending considering this. I am looking forward to the input of others too and @staff if possible, to see if this is a "yay or nay" situation or if there is more nuance to it. I would also still be keen in exploring to which extend relaying information upstream might have an influence on packaging this for Cloudron.

@jadudm said in Planka - A Trello-like Kanban board React/Redux: If the Cloudron team thought this was good to add to the stable of apps, I'd give it a go. I'm sure they have nothing against it . As far as I know they don't give a go ahead regarding apps or have a selection / veto process. If someone from community packages an app, they'll be super happy, they'll do some final checks to ensure it's done well and they'll publish it. It's more for the app they package themselves that they select usually from the wishlist depending on votes, or from their own needs. But there again, it's just a way to prioritise, rather than to say they wouldn'd happy to publish others.

@perelin well done! How is it? Also, if you have a git repo, it makes it easier for other to test and staff to begin packaging it for the App Store.

v0.50.0 https://github.com/twentyhq/twenty/releases

While you wait, I believe Hetzner has a disk image with this on it.

@joseph I have tried them in Coolify. Both are great, with Heyfrom trying to go head to head against typeform, and Opnform is your general go-to form. You can do lots with them both, design wise its beautiful and simple to use. I think soon Opnform will support payment as well. I think this is a great combination since we also already have Cal in Cloudron. With proper form app we can reduce the number of plugin we use in Wordpress too. Currently my go-to is Fluent forms, but I'm tryng to decentralise everything and only leaves WP just for the website. So clients do not need to go into WP backend just to see the forms admissions and so on. After Cloudron 9, I hope the team can try bring them in. It will be one of the best thing ever for all Cloudron users, I'm sure.

sorry actually demo is visible on their youtube channel

Seems to use/depend on mongo and keydb which is a faster multithreaded Redis. So it may be installable in a mongo based donor app.

Then there is https://github.com/The-Pocket-World/PocketManus as well

@perelin https://forum.cloudron.io/topic/13466/nzbget-on-cloudron-efficient-usenet-downloader

It may not matter, but I prefer this running on Postgres for longevity of support (currently 2029) and integrations from there. The dashboard uses Postgres too. The dash I think should stay with the package for completeness of one instance, as all the auth to the server happens there too. Perhaps have an option to disable it on multiple instances, but then one doesn't have to use it and still configure all the auth across servers.

@robi said in blot.im: @chetbaker This looks like something simple enough that can be installed in the LAMP app, mainly because you need to have the Apache config for the 3 services. Otherwise it may have worked in Surfer (or 3 Surfers). Is it big from a git clone? There may be a reason the developer suggests using --depth 1 Give it a shot with LAMP! I'll help if I can. exactly. Apparently the rest of the repo is just for managing users, etc. I tried this morning to run the docker compose in a ubuntu machine using the documentation but I failed. I will try again.

This software is now on 4.5.0 Beta. Here are the changes since when the application was first requested: https://github.com/sabnzbd/sabnzbd/compare/3.1.1...4.5.0Beta2