Cloudron Forum

There's this guide - https://docs.cloudron.io/guides/upgrade-ubuntu-20/ in case you haven't seen it already. Main gotcha is that the mysql server sometimes upgrades and sometimes doesn't. In the end, we want MySQL server 8. Sometimes, it asks you whether you want to remove mysql data. Be sure not to remove it!

Flatpack and Appimage formats do not provide the kind of process and filesystem isolation that Docker does. I would not be comfortable running run a service like Cloudron if it allowed running things other than well-defined/managed containers.

Yes, there are ways to break isolation and escalate out of a Docker container, but flatpack apps can, essentially, write anywhere on my system. Updating the ecosystem is also much more difficult; by comparison, it is possible to auto-build Docker containers from source and track recent updates/manage timely security vulns in a way that flatpack/appimage packages do not/rarely do.

Both the old java as well as the bedrock edition have now been updated.

Yup, we are also in DigitalOcean, AWS Markplace, Vultr as well. Time4VPS also has an image but it's outdated, unfortunately we don't control that image. If anyone knows other hosting providers where we should integrate let us know 😄 Even better if you have a contact in those providers...

@grienauer
When I did my testing for the Valheim Server App I wrote this script to make testing easier.

Note tho, this only works when not using any addons, but localstorage works with the local mount.

#!/bin/bash # Function to get the user to input the needed vars get_vars () { read -p "Cloudron E-Mail: " EMAIL read -p "Cloudron Username: " USERNAME read -s -p "Cloudron Password: " PASSWORD read -p "Cloudron URL: " CLOUDRON_URL read -p "DOCKER REPOSITORY URL: " DOCKER_REPOSITORY_URL read -p "DOCKER USERNAME: " DOCKER_REPOSITORY_USERNAME read -p -s "DOCKER PASSWORD: " DOCKER_REPOSITORY_PASSWORD printf "EMAIL=$EMAIL\n USERNAME=$USERNAME\n PASSWORD=$PASSWORD\n CLOUDRON_URL=$CLOUDRON_URL\n DOCKER_REPOSITORY_URL=$DOCKER_REPOSITORY_URL\n DOCKER_REPOSITORY_USERNAME=$DOCKER_REPOSITORY_USERNAME\n DOCKER_REPOSITORY_PASSWORD=$DOCKER_REPOSITORY_PASSWORD\n " > .env } # check if .env file exists and read it or check if vars exsist if [ -f ".env" ]; then export $(egrep -v '^#' .env | xargs) &> /dev/null else echo ".env File missing - asking for required vars" get_vars fi if [ -z "$EMAIL" ] || [ -z "$USERNAME" ] || [ -z "$PASSWORD" ] || [ -z "$CLOUDRON_URL" ] || [ -z "$DOCKER_REPOSITORY_URL" ] || [ -z "$DOCKER_REPOSITORY_USERNAME" ] || [ -z "$DOCKER_REPOSITORY_PASSWORD" ]; then echo "some vars are empty - asking for required vars" get_vars fi echo "=> Login Docker" docker login --username $DOCKER_REPOSITORY_USERNAME --password $DOCKER_REPOSITORY_PASSWORD $DOCKER_REPOSITORY_URL echo "=> Login Cloudron" cloudron login --username $USERNAME --password $PASSWORD my.$CLOUDRON_URL set -x # Get the ID and VERSION from the CloudronManifest.json ID=$(jq -r ".id" CloudronManifest.json) VERSION=$(jq -r ".version" CloudronManifest.json) echo "=> Create Test Data dir" mkdir -p ./cloudron_test/data ./cloudron_test/tmp ./cloudron_test/run echo "=> Cleanup Test Data" rm -rf ./cloudron_test/data/* ./cloudron_test/tmp/* ./cloudron_test/run/* echo "=> Build test image" cloudron build --set-repository $DOCKER_REPOSITORY_URL/$ID # docker build -t $DOCKER_REPOSITORY_URL/$ID:$VERSION . if [[ RUN_IMG = "" ]]; then read -p "Do you want to run the image created image?: (y/N)" RUN_IMG fi if [[ "$RUN_IMG" = "y" || "$RUN_IMG" = "Y" ]]; then echo "=> Run `test` tag of build image" docker run -ti --read-only \ --volume $(pwd)/cloudron_test/data:/app/data:rw \ --volume $(pwd)/cloudron_test/tmp:/tmp:rw \ --volume $(pwd)/cloudron_test/run:/run:rw \ $DOCKER_REPOSITORY_URL/$ID:$VERSION \ bash fi echo "=> Running tests" cd test echo "=> Running ncu - updating deps" ncu -u npm -i echo "=> Installing package.json" npm install if [[ -f ./node_modules/.bin/mocha ]]; then ./node_modules/.bin/mocha ./test.js -b fi if [[ -f ../node_modules/.bin/mocha ]]; then ../node_modules/.bin/mocha ./test.js -b fi # remove installed test instance echo "Cancel now if you wish to keep the app installed" sleep 10 cloudron uninstall --app test.$CLOUDRON_URL

@loudlemur said in Monkey See, Monkey Do: Cloudron Video Explainers:

RTFM

Let’s make RTFM stand for Read the Friendly Manual or better make a new acronym such as WTFV or WTT for Watch the Tuto.

@privsec said in Monkey See, Monkey Do: Cloudron Video Explainers:

How to properly setup/secure your server to a high level of protection

For me, the highest level of protection is a server without access to the internet; then more realistically it is a server with access to the internet but where all the services are behind a VPN; such as OpenVPN, WireGuard, ...).

With a server open to the world, you are at the mercy of the developers (the one who develop the application such as Nextcloud, WordPress, ...)

@loudlemur relax, it will sort itself out

@timconsidine

Cloudron seems to be using a very similar marketing strategy already, though arguably not advertising it adequately:

Cloudron - Complete Mail Solution

Whilst on this topic, some hosts are a bit nervous about Cloudron's email capability, or perhaps they are just nervous in general about email. (I think they don't want mass-mailing, emailing of newsletters, etc.) Perhaps somebody could give us some guidance or suggestions related to this?

Thank you !

@scooke Thank you very much! Bookmarked

@girish said in Cloudron Licence:

I have fixed the year in the license.

As for the license itself, the platform code is not opensource or free software if that is what you are wondering. We contribute to opensource in other ways both financially and with development - https://www.cloudron.io/opensource.html . The license text is an adaptation of various other licenses like GitLab EE, Sourcegraph EE license etc.

All our app packages are opensource. All the code is at https://git.cloudron.io/

I would like Cloudron to be released under a Free Licence. I am sure I am not alone in this.

I feel uneasy about it being non-Free. It feels like the rug could be pulled out from underneath at any moment. It is not that I think that Cloudron might "turn evil", but that pressure could be brought to bear on the maintainers, and in that way infrastructure built on Cloudron could be cancelled.

Is there any hope that Cloudron might be re-releaed under a Free licence?

@timconsidine
Cloudron already have a YT channel. Here it is on an Invidio.us instance:

https://invidious.snopyta.org/channel/UCOaWnVX6wqEI-IMdV9_s8_A

Cloudron could one-click import that channel onto LBRY

https://lbry.com/faq/youtube

Odysee Youtube Sync

@jdaviescoates said in Cloudron selfhosting platform:

@nebulon if I were you I'd edit the post with the wrong links to put the correct links back in, or just delete the comment (and perhaps block the user too).

And perhaps simply delete this thread, so we don't waste our time to finally getting nowhere loll

Andy

@Thulani I have Moodle installed in the LAMP app; it looks like something like OrangeHRM, and even Sentrifugo, is also installable via the LAMP app. I'll give them a whirl and see if they are.

(some time later...) Ok, both Sentrifugo and OrangeHRM installed fine; there was a bit of a trial and error setting up email correctly with Sentrifugo but it worked out. Sentrifugo is running well now on the LAMP app with just 256MB ram; OrangeHRm keeps giving me weird SQL errors when adding (but failing) new employees (SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '2020-06-13 09:53:34pm' for column 'created_date' at row 1) and other error messages.

@foliovision you can also try docker system prune -a --volumes but generally I have never succeeded in making that reclaimable space be less than 2GB in any server using docker (even without Cloudron).

@ahkg the reason for whitelisting 172.18.0.1 give access to all requests, is that this is the ip of the Cloudron internal gateway into the subnet where all apps are running.

Unfortunately for your case the cloudron healtcheck also comes via this gateway. I think your htaccess file needs to check for the X-Forwarded-For header to check against the correct inbound address.