Topics created by nebulon

Ok i had a modified LampApp for multible MCServers and as i bring that App up with 10 Ports for 10 MCservers they are not enabled i had enabled them after installation... And if Cloudron supports Portranges they are also still all time open than... No difference.. but in this state that TS-App is unusable for NPL and Gamerlicenses... The way with 9 more ports are the best possible for now.

This is now published as unstable until we got some feedback to mark it stable: https://forum.cloudron.io/topic/2121/teamspeak

Freescout is absolutely awesome, fast and easy "shared mailbox". Would love to see this in an CloudronApp, I know 2 organizations using Cloudron will immediately start using this app.

Great, thanks @girish that's good to know!

From what I can gather, this just means that eventually the user would have to submit some license key to the Kirby instance.

Maybe this can be used for the development of this app https://github.com/shopwareLabs/shopware-docker

The start.sh within the app is fixed now with the latest release. Please let me know if this doesn't work now. The whitelist is still not enabled by default since the app sticks to the upstream projects defaults for now.

Source https://github.com/phanan/koel Open Source Self-Hosted Koel Alternatives https://alternativeto.net/software/koel/?license=opensource&platform=self-hosted

@nebulon said in Disk filled up with kernel update artifacts: rm -rf /var/tmp/mkinitramfs* I had to instead do: cd /var/tmp find . -type f -delete -print This was running for like 5 hours! (and still running)

Wanted to post the known important issues so far: Invalid aliases causes an internal error. https://git.cloudron.io/cloudron/box/issues/533 External domains are not migrated properly. When an app used an external domain in 1.x, this was moved as a "manual" domain in 2.x. If you try to enable email for this migrated domain, you will hit https://git.cloudron.io/cloudron/box/issues/525. Workaround is in the bug report.

I think was just carried over from our previous issue tracker. Not sure anymore what it exactly meant and why the mail client wouldn't be able to connect. I guess we can ignore this.