Topics created by fbartels

Both issues are addressed with the new version 0.3.0 now

I am really excited about this. I'll see if I can still package Drone Runners as an app too. My ideal would be Drone CI and runners all on Cloudron. I reached out to @fbartels to potentially sponsor that as well. I want to try making it myself but honestly it is tempting to sponsor. Felix does some great work. Edit: Heh I say this as I switch to GitLab and run a GitLab runner. No matter, it would still be good to see some CI tools on Cloudron to go with the Git platforms.

@girish @nebulon methinks this thread should be moved into the App Packaging/ Custom App category?

Agola is really quite nice.

The following configuration needs to be added to the identifier registration of Kopano Konnect to enable SSO with Rocketchat: - id: rocketchat.9wd.eu name: Rocketchat trusted: true application_type: web redirect_uris: - https://rocketchat.9wd.eu/_oauth/konnect Remember to restart Konnect after modifying the registry. If you want to verify that the configuration was properly loaded you have to modify log_level in /app/data/konnectd.cfg to read /app/data/konnectd.cfg. With another restart Konnect will then print a message like the following at startup: Apr 20 20:21:30 time="2020-04-20T18:21:30Z" level=debug msg="registered client" application_type=web client_id=rocketchat.9wd.eu insecure=false origins="[https://rocketchat.9wd.eu]" redirect_uris="[https://rocketchat.9wd.eu/_oauth/konnect]" trusted=true with_client_secret=false In Rocket.chat the following configuration needs to be added. For this go into the admin backend, select "OAuth" and there "Add custom oauth". I am using the following settings: URL: https://meet.9wd.eu Token Path: /konnect/v1/token Token Sent Via: Header Identity Token Sent Via: Same as "Token Sent Via" Identity Path: /konnect/v1/userinfo Authorize Path: /signin/v1/identifier/_/authorize Scope: openid profile email Id: rocketchat.9wd.eu Secret: rocketchat Login Style: Default Button Text: Kopano Konnect (needs to be something the user can relate to) Button Text Color: #FFFFFF Button Color: #13679A Username field: preferred_username Merge users: false After storing these log out of Rocket.chat and you will see a new button on your login page titled "Kopano Konnect", which will then use the new login method.

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

Nice, thanks @girish

I have created https://git.cloudron.io/cloudron/box/issues/649

Thanks for the heads up and the workaround! The last update explicitly removed the admin status propagation from Cloudron user accounts to the app. This is done to unify how user accounts get permissions assigned within all apps. The idea is, that the Cloudron admin status is not carried over to apps, since apps have too many different concepts what an admin is and is not. I guess there is no good way without requiring manual permission changes to move to this new understanding what admin means on Cloudron.

Thanks @girish! With the above dockerfile cloudron build now succeeds. I have a longer train ride on friday, maybe I can make something happen with bitwarden during it.

Had this issue on support couple of times already: https://git.cloudron.io/cloudron/box/issues/610

@nebulon said in Mail domain alias for subdomain: I guess what you are looking for is a way to match the app internal username (resulting in this email) with some other inbox? yes, exactly (as long as you refer to the user in nextcloud by internal username). Sending would not be required, only receiving (which should minimise the setup effort, since only a mx record is needed).

@fbartels Yes, the format of cloudron.json had changed between the CLI version. We didn't write the migration code since we thought it wasn't important.

@girish said in Alternative to "oauth proxy"?: we felt we cannot win on our own yes, the world would be a better place if all applications would properly support oauth2 or even better openid connect. I will anyways first give https://github.com/bitly/oauth2_proxy a try and if that does not work I'll configure mod_authnz_ldap in the apache bundled in the base image.

@girish said in smtp_forward for Haraka?: I am not sure if smtp_forward will work for your use case. oh, that is indeed true. I stumbled upon something that suggested that this could be achieved with smtp_forward, but reading the page closer this indeed would not work as desired for me. I'd rather want to avoid fetching mails from cloudron the the extra server. I'll have to think about some alternative approaches (maybe stick with my current relay setup and just make cloudron one of the relay targets). Thanks for looking into this!

Yep, now I'm interested ! (see https://forum.cloudron.io/topic/2179/mailclient-with-pop3-support)