Add new apps to Co-op Cloud #94

Closed
opened 2021-06-22 13:38:23 +00:00 by knoflook · 17 comments
Member

If you want to see an app added to coopcloud please comment under this issue with the name of application you want to see. Before doing that check if somebody else suggested the same app and if so, vote with emojis! Please also vote for your own suggestions!

If you want to see an app added to coopcloud please comment under this issue with the name of application you want to see. Before doing that check if somebody else suggested the same app and if so, vote with emojis! Please also vote for your own suggestions!
Author
Member

Invidious (https://github.com/iv-org/invidious)
anonymizing youtube frontent (invidio.us)

Invidious (https://github.com/iv-org/invidious) anonymizing youtube frontent (invidio.us)
Author
Member

firefly-iii https://www.firefly-iii.org/
finance manager.

firefly-iii https://www.firefly-iii.org/ finance manager.
Owner

nocodb https://github.com/nocodb/nocodb
The Open Source Airtable alternative

nocodb https://github.com/nocodb/nocodb The Open Source Airtable alternative
Owner

Calendso https://calendso.com/
The Open Source Calendly Alternative

Calendso https://calendso.com/ The Open Source Calendly Alternative
Owner

Suite CRM https://suitecrm.com/
Customer/Client/Contact Relationship Manager (CRM) system

Suite CRM https://suitecrm.com/ Customer/Client/Contact Relationship Manager (CRM) system
decentral1se changed title from Add new apps to coopcloud to Add new apps to Co-op Cloud 2021-06-22 16:21:17 +00:00
Owner

https://github.com/knadh/listmonk
High performance, self-hosted newsletter and mailing list manager with a modern dashboard. Single binary app.

https://github.com/knadh/listmonk High performance, self-hosted newsletter and mailing list manager with a modern dashboard. Single binary app.
Owner

https://mailtrain.org/
Self Hosted Newsletter App Built on Top of Nodemailer

https://mailtrain.org/ Self Hosted Newsletter App Built on Top of Nodemailer
Owner
~~https://github.com/superseriousbusiness/gotosocial Golang fediverse server.~~ **ADDED**: https://git.autonomic.zone/coop-cloud/gotosocial
Owner

https://github.com/misskey-dev/misskey
A interplanetary communication platform rocket.

https://github.com/misskey-dev/misskey A interplanetary communication platform rocket.
Owner

CoTURN, https://github.com/coturn/coturn
TURN server


Currently, a coturn service is included in coop-cloud/matrix-synapse, and coop-cloud/workadventure.

It seems that CoTURN currently requires "host-mode networking", because of the large number of UDP ports required, e.g. see here https://github.com/silvio/docker-matrix/issues/38

Even if we resolved this using port ranges, UDP ports can't be forwarded per-host via Traefik anyway, so there's a one-CoTURN-per-ingress-IP limitation, just like for other UDP services, and similar to our one-Mailu-per-ingress-IP limitation.

This is making me think that CoTURN should be a separate, shared app, instead of a service on containers -- I believe Cloudron does it this way.

CoTURN, https://github.com/coturn/coturn TURN server --- Currently, a coturn service is included in coop-cloud/matrix-synapse, and coop-cloud/workadventure. It seems that CoTURN currently requires "host-mode networking", because of the large number of UDP ports required, e.g. see here https://github.com/silvio/docker-matrix/issues/38 Even if we resolved this using port ranges, UDP ports can't be forwarded per-host via Traefik anyway, so there's a one-CoTURN-per-ingress-IP limitation, just like for other UDP services, and similar to our one-Mailu-per-ingress-IP limitation. This is making me think that CoTURN should be a separate, shared app, instead of a service on containers -- I believe Cloudron does it this way.
Owner

https://github.com/nolanlawson/pinafore
Alternative web client for Mastodon

https://github.com/nolanlawson/pinafore Alternative web client for Mastodon
Owner

haven't used this but looks like a clean alternative to google photos, https://lychee.electerious.com/

also does it make sense to have an issue per app instead of one long thread? I dunno :)

haven't used this but looks like a clean alternative to google photos, https://lychee.electerious.com/ also does it make sense to have an issue per app instead of one long thread? I dunno :)
Author
Member

haven't used this but looks like a clean alternative to google photos, https://lychee.electerious.com/

also does it make sense to have an issue per app instead of one long thread? I dunno :)

Yeah I just wanted to dump a few ideas here 🤷‍♂️ didn't expect this to grow so fast. I think that having more issues has an advantage of being easily searchable but also a disadvantage of creating a lot of issues which might be somewhat demotivating. If anybody knows software for tracking that we could use it. I would say it would be best to have an editable list of apps with the possibility of voting for them and some way of showing how much work has been done on it? Even a couple of states like: no work done, person assigned, work in progress, alpha, beta.

> haven't used this but looks like a clean alternative to google photos, https://lychee.electerious.com/ > > also does it make sense to have an issue per app instead of one long thread? I dunno :) Yeah I just wanted to dump a few ideas here 🤷‍♂️ didn't expect this to grow so fast. I think that having more issues has an advantage of being easily searchable but also a disadvantage of creating a lot of issues which might be somewhat demotivating. If anybody knows software for tracking that we could use it. I would say it would be best to have an editable list of apps with the possibility of voting for them and _some_ way of showing how much work has been done on it? Even a couple of states like: no work done, person assigned, work in progress, alpha, beta.
Owner

Maybe a separate, empty coop-cloud/apps repo would have the benefits of separate tickets, without clogging up this one? 🤔

@knoflook we could maybe use labels for the states you're suggesting?

Maybe a separate, empty `coop-cloud/apps` repo would have the benefits of separate tickets, without clogging up this one? 🤔 @knoflook we could maybe use labels for the states you're suggesting?
Owner

I'm fine with whatever folks wanna do. Labels thing sounds good. Another idea would just use an open pad (e.g. https://pad.autonomic.zone/v9n7W7OJQsqjZAC7a9_Ehg) and then we can CNAME the published pad for reading and anyone can update it?

I'm fine with whatever folks wanna do. Labels thing sounds good. Another idea would just use an open pad (e.g. https://pad.autonomic.zone/v9n7W7OJQsqjZAC7a9_Ehg) and then we can CNAME the published pad for reading and anyone can update it?
Owner

@3wordchant and I chatted briefly today about it and decided a new repo would be best so I made one, https://git.autonomic.zone/coop-cloud/Apps

@3wordchant and I chatted briefly today about it and decided a new repo would be best so I made one, https://git.autonomic.zone/coop-cloud/Apps
Owner

decided a new repo would be best so I made one, https://git.autonomic.zone/coop-cloud/Apps

Looks like we're over there then!

> decided a new repo would be best so I made one, https://git.autonomic.zone/coop-cloud/Apps Looks like we're over there then!
This repo is archived. You cannot comment on issues.
No description provided.