For once, this post is not really to request an app, but to announce that my package for it is ready ^^

https://git.cloudron.io/mehdi/couchpotato-app

http://couchpota.to/

@girish said in What's coming in 6.4:

Specifically, we moved from callback based programming to more modern async/await.

Great ! Honestly, that was long overdue ^^ I think it is a great time investment, as it will definitely speed up future developments significantly.

I quite agree with @timconsidine . We could have these apps on Cloudron, but with a big fat red warning that says the app is unsupported :

• zero user support
• larger backups
• no auto-update

If unhappy: bother the original author.

I am strongly against replacing the server in the current OpenVPN app.

However, it totally makes sense as a new, separate, app.

@ruihildt said in Why not make Cloudron fully open source again?:

I'm sad not to be able to recommend Cloudron as the best open source paas since the license change.
It has in effect changed my relation to the project, from an invested advocate to a simple client.

I totally agree with this part. More than that, I would never have picked up Cloudron at all at the beginning if it weren't open source.

And as to contributions, I am the author of one of these rare contributions ^^ (to make the platform compatible with the OpenVPN app), and I would definitely not have contributed if it were not open source.

TLDR: I am 100% in favor of switching back to an open source licence.

(As for the precise licence, I do not really care, be it MIT, Apache, GPL, AGPL ... whatever.)

I am a regular user of cryptpad, and I can confirm it works well ! It's basically an Etherpad, but with end2end encryption. Would love to see it on cloudron.

@infogulch said in Scaling / High Availability Cloudron Setup:

I'd rather have multi-node app management than distributed app runtime. Manage all your cloudron nodes and assign apps between them, migrate them etc, but most apps can still only be deployed to one cloudron instance at a time. At least I think this would be a better scaling/ha goal for a v1 implementation.

I totally agree, and I think it's the way the cloudron team is headed for the V1

@LoudLemur

Gitea is a fork of Gogs, so they are quite similar : both are lightweight and efficient, but quite minimalist.

GitLab is much heavier, but has much more features.

I suggest going with Gitea if you only need Git hosting + basic issue tracker. I suggest GitLab if you are interested in having integrated CI, more complete issue tracking, package manager, ... basically every bells and whistles you could think of and then some ^^

@lonk It combines Jellyfin (for which there's already an app now), Transmission, SickChill, Couchpotato (the 3 I just mentioned), a custom file manager (built before Cloudron had one), and a custom TV Shows and Movies streaming interface (built before I integrated Jellyfin). Plus a few custom things, like a script to auto-remove finished torrents on transmission, and a script to auto-convert videos to MP4 for easy streaming in the browser (for my custom streaming interface. I disabled it now that I mainly use jellyfin, which handles this automatically).

@girish @nebulon My Transmission app is done, tests and all https://git.cloudron.io/mehdi/transmission-app

In my opinion, it's ready to push to store. It may need a bit more doc, but other than that it's good to go

BTW, the proxyAuth addon rocks !

BTW the cloudrons docs page seems to be wrong:

Ackee is a Self-hosted, Node.js based analytics tool for those who care about privacy

I think there was a copy/paste that got out of hand ^^

@wisameldin Temporary failure resolving 'archive.ubuntu.com' => looks like your server has connectivity issues. Or maybe DNS issues. Which provider are you using?

@girish Yes there is. .ipfs is not a "normal" TLD. It's for websites which are on IPFS, which is an alternate decentralized protocol. Kinda like .onion domains for serving websites on tor.

However, i don't really know how cloudron could support it, as I believe it does not use standard http/s at all, so regular apps would not work.

@LoudLemur Basically what @robi said : this driver (or any driver for that matter) will only contain information on how to communicate with the hardware, not how the hardware is made, and especially not why it's made that way.

As an alternative, I know that https://www.seafile.com/ is a file storage solution which offers end2end encryption, but when I last tried it (admittedly a few years ago) the client software was

Basically, what you want for this is end-to-end encryption (and I know a bit about this, it's literally my job to implement E2EE ^^).

The problem is that the nextcloud app that provides E2EE is bad, like really bad, like "my files just disappeared, i have no idea why" bad.

So, long story short, there is no simple way for you to provide this service to your friend with nextcloud with you not being able to look at their files.

@MichaelF Take a look at https://docs.cloudron.io/troubleshooting/#recovery-after-disk-full , if you haven't already

(BTW, hiding your IPv6 address when you show the domain in your curl example is not very useful ^^ dig AAAA hemmer.land gives 2a03:b0c0:3:d0::13ec:f001)

@stormgrass said in IPv6 for Mastodon - how?:

Seeing how both produce different results in my DNS records: is adding the DO-issued address into Cloudron as a static IP the correct course of action, or should I be using the Network Interface instead?

Not necessarily : it is very common that servers get assigned a /64 IPv6 address : that means a bloc of IP addresses where only the first half is common, and the second half can be anything.

If the 2 addresses have the same first half, there's nothing weird about the results being different.

If not, there's something afoot.

Also, about your curl test failing, dumb question but are you sure that your local machine has IPv6 connectivity ? To test, you can try something like ping6 google.com

@binary1zero From the constraints you mentioned, I do not understand why you don't simply use the home server as a main email server, but with an external relay for outgoing email (assuming your ISP does not block inbound 25).

From what I know, PTR and stuff is only necessary for outbound relay, as it mostly affects server reputation when other server decide incoming email is spam.