the repository is marked as a "work in progress" and there has been no formal release as of yet. I think these two facts make it hard to really consider this for an app. @yusf said in Nitter - A free and open source alternative Twitter front-end focused on privacy.: I assumed it was completely statically served but maybe not? It seems to bring some form of binary daemon. Given that this is named like the project makes it not seem like it can be served by any webserver.

Nice, thanks @girish

I would actually rather prefer active login sessions like you have with other such tools like docker login where you switch between them, but if the token is still valid you don't have to explicitly login. The --cloudron arg is quite some overhead to pass all the time.

i have the same Problem at home i use Cloudron 4.4.4 there int runs fine, but yesterday i installed a new clorudron installation v. 4.4.5 and ther i have problems with collabora. when i open a word file from nextcloud the first time it opens, but when i close the file and 30s later i open it again collabora doesnt load, it stays at 1% loading and i cant opan any other file.

Can you describe the use-case a bit further? Cloudron already collects logs for each application and addon, as well as the Cloudron related platform components. Generally it is not supported to install other daemons on the side of Cloudron on the same server, since we cannot test such configurations during updates. FYI all the logs are collected currently as described here https://cloudron.io/documentation/troubleshooting/#logs

First thing in the readme: Note: There might be thousands such solutions available already! :D

@pdubs For custom apps, simply add a special route in your nodejs app like /cloudron_healthcheck and make it return a http status code 200. Then fixup the healthCheckPath of your app's CloudronManifest.json.

@RichardJActon The docs are a bit ambiguous here but you have to first navigate to https://my.example.com/api/v1/session/password/resetRequest.html first (replace your domain name), then provide your email and reset it and then the sql command will give you the reset token.

I would also delete ~/.cloudron.json for good measure since we change the format of the config a few times and maybe you have something from an older CLI version.

@jdaviescoates The link in the old request is for old code

Good point, I thought this would be triggered by the security update job from ubuntu already, but apparently not.

@JOduMonT Currently, Cloudron does not support IPv6 and requires an IPv4. You can, of course, configure your server to have IPv6 address additionally and configure DNS AAAA records manually and that should work. Goes without saying, we want to add IPv6 support at some point (I know it's 2020!! )

@yusf @girish beat you to it https://forum.cloudron.io/topic/2158/vikunja-the-to-do-app-to-organize-your-life (also it only has one k)

@jeau Very nice! For those interested in looking into what the app actually is, there is a demo at - https://projectmirador.org/demo/

Is just DKIM and SPF not required or generally that domain not for sending out emails? If the latter is the case, the checks can be disabled by setting the Email Relay to "Disable" in the Outbound tab of the Email settings for this domain.