For the coming weeks, we are going to focus on getting some new apps packaged. The list is:

• OnlyOffice
• Bitwarden - @Felix and @iamthefij have done much of the heavy lifting, we just have to get it across the line.
• OpenVPN - We will add an admin interface that let's the admins configure some popular vpn settings.
• BigBlueButton or Jitsi (we will evaluate which works well for conferencing. We have used both and they both work well but BBB might win). If you have any thoughts here, please leave a comment.
• Development apps - basically provide a git push workflow for hosting custom nodejs/php apps (and make it work so that they can be mixed with various caches and databases).

If we should prioritize something else, please let us know! But the above should keep us occupied this month.

Hi all,
We released Cloudron 4 now. The blog has more details about the release.

Changes:

• SFTP access is built into the platform. As of this release, WordPress, Surfer and LAMP apps support SFTP access. You can get the SFTP credentials from the i button in the app grid. Note that the username for each app is different!
• App tags and labels - this lets you easily categorize and search app. The current UI is very basic, we hope to iterate on this. Feedback welcome.
• Scaleway Object Storage backend for backups
• Easier email import. There is some basic docs on how to use imapsync here
• Unmanaged WordPress app - this app allows you to edit WordPress code unlike the existing WordPress app. Since, we let you edit the code, we won't deal with updates either. You can to use the WPs built-in updater for that. Docs for this app are here. Currently, this app is marked as unstable. So, you have to enable the unstable flag in settings before you can install it/see it in your Cloudron.
• Immediate App Update notifications
• Backups created right before an app update are retained for upto 3 weeks. This lets admins roll back in case they notice some breakage late.
• Community/Unstable apps. There's been a lot of app packaging going on and we can't keep up with testing of all the apps. So, we will get them all listed in the coming weeks, so others can easily test them out.
• Upstream app version is now listed in the app info dialog
• Support for email relays that do not require authentication and self-signed certificates
• Cloudron updates can now be applied without taking a full backup. This was added for situations where there might a bug in the backup logic and an upcoming Cloudron update fixes the backup issue.
• Add a way to disable outbound mail for a domain. Email -> Outbound -> Select Disabled

For the coming weeks, our focus is simply to get more of the apps out. bitwardern/jitsi/matrix etc are in various states and we want to get those out asap.

We are working on some ideas on the Cloudron side:

• Mail fts search - This will be optional since the dovecot+solr integration takes a lot of memory.
• Mail server queue and reports - This is just a UI to get an insight into what emails are incoming and outgoing on the mail server
• Mail spam controls - This will tackle the popular "Spams are still getting through" reports
• CPU resource allocation - Currently, you can control memory per app. This will allow you to control the CPU allocation as well.
• Firewall API
  • This will allow setting up basic application firewall rules. This is not clear yet but we will build on top of modsecurity/fail2ban potentially.
  • For email, this will have whitelist/blacklist
• Backup - listing, download and remove API and UI (for box and the apps).
• Per-app backup format.
• Group admins - The idea here is to create "sub admins" who can invite users but cannot control server level settings like backups.
• Whitelabel the footer/404
• App specific passwords

BTW, if you have comments/suggestions, feel free to open a thread in the Discuss section or comment here for any clarification

Hi all,
We released Cloudron 4.4. See the blog for screenshots and more info.

• Show swap info in graphs
• User avatars are now customizable (click on the profile photo icon). This removes the use of gravatar for privacy reasons.
• import: add option to import app in-place
• import: add option to import app from arbitrary backup config
• Show download progress for rsync backups
• acme2: Implement post-as-get
• AWS Marketplace image
• Stopped apps are be auto-updated anymore (since they won't run migration scripts).
• eventlog: track support ticket creation and remote support status
• cloudflare: support API tokens
• Add search field in apps view (this only appears if you have many apps)
• Make app view tags and domain filter persistent across browser refresh
• Add timezone UI. We used to auto detect this but clearly it's imperfect, so we have decided to expose it. This allows you to precisely configure when backup and update tasks get scheduled.

Hi all,
Mastodon is now available in the app store. Most of the packaging work was done by @syn . Thanks a lot, @syn!

Code: https://git.cloudron.io/cloudron/mastodon-app
App store link: https://cloudron.io/store/org.joinmastodon.cloudronapp.html
Docs: https://cloudron.io/documentation/apps/mastodon/

Good question! So far, we haven't been overwhelmed with the app count. I think we can actually easily support far more. This is only because:

• The main packaging cost is the first initial version. If you see the source code of any app package, we hardly have to make changes for a new release. It's mostly bumping the version. I am hoping once we have a CI/CD app on Cloudron, we can automate this part.
• All our stable apps have tests. We don't test anything manually. The apps that don't have proper automated tests (like confluence), we have regretted publishing. But we keep them supported and test them manually since enough paying customers are using it. But that was a lesson for us to not add apps that don't have tests.
• Many of the new apps that we are publishing now was packaged by our community - @msbt , @iamthefij , @Felix, @thetomester13 , @jimcavoli , @murgero (there's also 2-3 more but I am unable to find their id) etc. So, we are just building on top of their hard work (thanks a lot again guys!).
• Finally, our goal is not to package all the apps possible. We just want the best 2-3 apps in each category. So, if there are 30 categories. This will only come to 90 apps or so.

All that said, if you see a drop in quality in support or general, please let us know and that will a hint for us to look into adding resources

https://yetiforce.com/en/

https://github.com/YetiForceCompany/YetiForceCRM

We are working on pushing out 2.2 early next week. The main feature planned is 2FA/TOTP support for the cloudron.io login and the dashboard.

Users will see a button in their profile section to setup 2FA. You can use Google Authenticator, FreeOTP or similar app to generate one time passwords.

To keep things simple this option will only enable 2FA for the dashboard login. App logins will not requires 2FA. From our initial investigation, many apps already support 2FA and making up some scheme like password+otp will have to carefully thought through from a UX perspective.

An update on this. We tried to push the update today with a plan to roll out later this week. We found some issues with the database migration which we are currently working on. Over all, it's unlikely this gets pushed out this week.

Now for some good news: we have updated all apps to use the latest base image 1.0.0 (which is based off ubuntu 18 and contains many security fixes).

Time for some progress updates!

There is now a system menu:

Inside which, there are services list. You can monitor and configure the services:

Backups can now be cancelled. Updates can also be cancelled. Yes, the layout is bit off here but it will be fixed before the release:

Also, we have reworked the email handling for apps a bit to support some use cases. Currently, apps are create a mailbox of their own and one cannot easily access these mailboxes (if someone replied to the email). We have fixed this so that apps can now be associated with any existing mailbox. By default, an address is auto-generated for the app. You can then change this to an existing mailbox which you can access using your credentials. It's also possible now to share the mailbox name across apps.

@nebulon Isn't that how it works now already? I thought we stash all the login tokens in ~/.cloudron.json ?

I don't mind adding it since we already have apps like CloudTorrent as well.

Are we thinking of adding a global --cloudron <my.example.com> argument ?

@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!! )

@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.

I have made a fix for the next release.

This seems to be an ubuntu packaging bug even since it doesn't seem to install logrotate files (we just use upstream collectd package). I found https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1644135 which is a similar bug.

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

@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.