For those that would be interested. I have just created a live stream on Youtube for Sunday 21.06. 14:00 (CET). During that stream I want to show a bit how to make a Cloudron app and will use Matterbridge as the example for it.
I would timebox the whole stream to a max of two hours, lets see how far I'll get in that time, maybe I won't even need that much time.
There will be an unedited recording of the stream later on.
You can follow the stream at https://www.youtube.com/watch?v=RKcH2yJiLUo
Hi,
I'm thinking about creating a Cloudron app that uses fetchmail to fetch external mailboxes and deliver their mails to local accounts. Depending if I find a good example for a config ui this would then be configurable either from a small web ui or by simply editing the fetchmailrc file from the console.
Anyone else interested?
Hello everyone. See you on half an hour at https://youtu.be/RKcH2yJiLUo!
@msbt said in Proposal: Free-Tier Alterations 
:
Not sure if paying for updates defeats the purpose of having a secure system with rolling auto-updates
Exactly. I think it's bad practice to hide things like updates and 2FA behind an extra paywall.
Plus it was like this in the past already and was changed for the very same reason: you don't want to have people with vulnerable old versions out in the wild.
While native support for OAuth has recently been removed from Cloudron users can still utilise OAuth 2 and OpenID Connect (oidc) to authorize users thanks to the built in OpenID Provider of the Kopano Meet app.
Under the hood Kopano Meet uses OpenID Connect to sign users into the application and this functionality is provided through Kopano Konnect, which is bundled inside of the app and pre-configured to allow Cloudron users to login. This article will show how to extend the configuration of Kopano Konnect to allow other apps to make use of OpenID Connect.
Requirements:
Nextcloud only serves as an example most users will probably already be familiar with, any other app allowing login through oidc can be configured in a similar way.
In the below configuration snippets I am going to use the domain meet.9wd.eu for my Kopano Meet installation and cloud.9wd.eu for my Nextcloud installation. Make sure to use your actual domain names during the configuration.
To modify the configuration of Konnect you need to login at your Cloudron dashboard (which is usually available at https://my.your-comain.com) and open the terminal view of the Meet app (Look for "Console Access" in the settings of Meet). Here you need to open /app/data/konnectd-identifier-registration.yaml in an editor and add the following text to the end of the file:
- id: cloud.9wd.eu
application_type: web
name: Nextcloud Cloudron
trusted: true
redirect_uris:
- https://cloud.9wd.eu/index.php/apps/sociallogin/custom_oidc/CloudronMeet
Important: the redirect url must match the "internal name" specified during the social login configuration later on
After the file has been modified restart Konnect by running supervisorctl restart kopano-konnectd (alternatively the whole meet app could be restarted, but this is faster).
The rest of the configuration is done inside of Nextcloud.
To configure Nextcloud for oidc you first need to login with an admin level user and install the "social login" app inside of Nextcloud. After the app has been installed you have go into its settings (which are located at https://cloud.9wd.eu/settings/admin/sociallogin) to configure it.
I recommend to have the following general configuration settings set in the app:
This will mean that new users will first need to login through the "traditional" Nextcloud login and then from within their user settings link their oidc login to Nextcloud. This will be further explained once oidc is generally setup in Nextcloud.
Further down in the settings add your own "custom OpenID Connect" provider. You need to fill in the following values:
redirect_uris in konnectd-identifier-registration.yamlhttps://meet.9wd.eu/.well-known/openid-configurationOnce this is setup log out with your admin user account and you will see another login button on the Nextcloud login page titled "Kopano Konnect (Cloudron)".
Before the user can use oidc to log into Nextcloud, he need to link his existing Cloudron user to it. For this log into Nextcloud like you have done in the past and afterwards go into the settings of the user. Here you will now find an option called "social login" (the url will be similar to https://cloud.9wd.eu/settings/user/sociallogin).
Users need to manually connect their existing Nextcloud account with the oidc identity.
At this menu item you will find a section called "Available providers" with a button underneath that will read "Kopano Konnect (Cloudron)". Click this button once to link your Nextcloud account to your new OpenID identity. In case you have previously not been logged into Meet you will be asked for your credentials for this (which are your normal Cloudron credentials).
Once your Nextcloud account has been linked you can easily switch between Nextcloud and Kopano Meet without having to login again.
This article has also been published on my blog.
I recently talked to the CEO of Humhub and also made him aware of Cloudron and this topic. He said that they are currently busy with investigating ways to automate deployments in container scenarios and once that is solved they would be open to collaborate on an app for Cloudron.
Hi everyone,
in the past weeks I have been working with the Cloudron team to make Kopano Meet available as an app for Cloudron.
Meet is a modern video conferencing app that is designed as a so called Progressive Web App (PWA) which means that you can add it as an app to your phone/tablet/desktop directly from within Meet and without relying on external app stores. Functionality wise Meet provides 1 to 1 and group video calls as well as screensharing. We are utilising a library called "Glue" which facilitates easy integration into other applications, internal proof of concepts with this have already been done with Matrix and ownClouds new Phoenix UI (based on customer projects).
The app has been released to unstable last week and can be found at https://cloudron.io/store/com.kopano.meet.cloudronapp.html.
Looking forward to your feedback!
@girish said in What's coming in 6.4:
I added a last item "Make it easy to install non-app store apps".
That is great news. In case you do not yet have a better idea how this could be designed, I want to pitch the way this is organised in Portainer again. I explained it already a while back in https://forum.cloudron.io/topic/4485/proposal-the-cur-cloudron-user-repository/14?_=1626194230000. Basically a local admin can override/extend the entries from their official "appstore". Additional entries are defined in a json structure. When opening the Cloudron appstore it makes a request to https://my.cloudron.host/api/v1/appstore/apps which gets a json response with all the appstore data. What if opening the store would in addition to this also make a request to https://user:password@store.my.domain/apps.json and also show a category "community" that lists apps from this json listing. Plus points if the listing can be password protected (like the private docker registry). This could also be a nice revenue model for external app developers.
@jdaviescoates said in Why not make Cloudron fully open source again?:
Co-op Cloud
It's an interesting, but also really quite different approach. I like cloudron because it's so "hands off". Their system really just seems to be a deployment utility for docker swarm along with a standardised way of deployment.
Hi @jordanurbs,
the viability of snapshots for backup has for example been discussed in https://forum.cloudron.io/topic/4161/disc-snapshots?_=1628139201934.
Just to have it said. You could probably also host your "landing page" within Cloudron itself. Depending how that page is built you could for example host it as a static page in "surfer".
@breixopd said in Landing page not working:
my.jessiscute.xyz is set to the IP of the server running cloudron but jessiscute.xyz is set to my other host
Since your landing page is not hosted on Cloudron, its highly unlikely that it is broken "because you installed Cloudron". Maybe the hosting provider has some issues?
@privsec said in Can not uninstall Nextcloud:
I am not sure where to run those commands
These are to be run directly on the Cloudron host via for example ssh.
@roru2k20 you could have a look how its done in the builder app. its source code is available at https://git.cloudron.io/cloudron/cloudron-build-service
This uses the docker capability of exposing the local docker socket to the container. then you only need the Docker binaries in the app itself, but everything is executed on the host. This however also has the downside that you can practically take over the whole host of someone gets access to your app, which has unrestricted access to the socket.
@baswaraj said in etcd for minio:
here which ip address , do i need to put and how it works
The ip address/fqdn where you installed etcd
Hi @baswaraj,
in your last post you were not entirely clear if you are using minio on Cloudron, or of you are using Cloudron at all.
@baswaraj said in etcd for minio:
minio_etcd_endpoints
This is defined in the following way in the Minio documentation:
MINIO_ETCD_ENDPOINTS
This is comma separated list of etcd servers that you want to use as the MinIO federation back-end. This should
be same across the federated deployment, i.e. all the MinIO instances within a federated deployment should use same
etcd back-end.
So this is the ip of the etcd service that you have already installed.
PS: the link you posted does not work
@micmc afaik Rocket chat is written in meteor. in the and almost everything is possible in a custom app.
@oversight said in Could not install setup dependencies (curl).:
on a raspberry Pi4 (4G)
I don't think running Cloudron on something else than amd64 is currently not possible (although there have been some attempts at it in the past).
The app seems to be missing the capabilities item in the manifest.
Example from statping: https://git.cloudron.io/cloudron/statping-app/-/blob/master/CloudronManifest.json#L27
Interesting choice for for the vm size at Linode. With just a gig of ram I cannot imagine that Guacamole runs nicely on it however.