Cloudron Forum

Roll back for GitLab is a no-go thing. Let's hope that Gitlab does not do something in future update release which would prevent using it.

@tobiasb good catch. I think because it depends on resolvconf, it ends in errored state. I will disable that service explicitly

I have implemented this in Cloudron 10 . You can set the maxmemoryPolicy in the manifest.

Thanks! Fixed now

Good find, apparently std*.resume() is not available on recent nodejs versions anymore and was already obsolete. I've published a new cli version now with the fix.

actually after looking closer in the code, the RRSet record api should also work as ich even for more records. It only would hit an issue, if one record has more than 25 values.

Yes to use it together with Gitlab app, the user management is not openid as documented in cloudron docs.

I would say lets close this here. I do not see any failed cleanup jobs even multiple jobs try todo the same.

Makes sense. +1

@girish This would already help to find out that not something hidden in the OS takes the storage.