Cloudron Forum

Go ahead with the Open Source edition only. Need an incentive?: This means giving another app for your users.

What happened here is that you saw paid software and you want a piece of the action. I gave you options you gave me less, no big deal.

Here's how it's made: Reach me when you get 100 users running the Open Source edition I will grant you an exclusive license to host Chevereto Lite (not yet released) for free for your users during a year. After that let's settle a license fee that will keep you competitive. If you want to keep talking business of course.

Open Source edition is available through public registry (GitHub CR, DockerHub). For the paid editions you need to build locally as we don't have a private container registry yet.

To access the proprietary code users provide the license key in some build process that I streamlined for them. They fill some env file and the thing does the building for them. Here the pure docker builder: https://github.com/chevereto/docker/blob/4.1/docs/PURE-DOCKER.md#build-image

Data (uploads, assets and database) is compatible between editions. What changes is the actual application filesystem, it must be a different container image for the application layer.

Hi @nebulon great to see you here.

Ideally you will want to have two container images, one for each edition, because the software packages are different. An alternative could be to provision a special license for Cloudron from which you can build the image and make it available only for your network. I could also provide a private container registry and let the user deal with licensing directly from us, but to move in that direction I need to see some traction first.

Unless you are up to deal with the app layer persistence in which case the process can be made directly from the Chevereto dashboard. For non-docker based provisioning the user can enter the key directly and the system will download and extract the Pro edition filesystem:

I can workaround a lot here, I'm the factory after all.

For basic LAMP there's no special requirements, you require a bunch of libs (imagick, ffmpeg, etc) and from there is just bind the website to the public path. To learn about the HTTP server requirements you can check from line 6: https://github.com/chevereto/docker/blob/4.1/Dockerfile#L6

Perhaps for video uploading you will require to increase the post limits, the usual stuff.

@andreasdueren Sure, that's totally needed. The differences aren't listed on the website yet and the table you saw at GitHub appeared just two days ago: https://github.com/chevereto/chevereto/commit/c43666f8d51c4c26c03b41ee1f68f978b72edc90

I didn't add the comparison table before because I had the intention to let users to try the software on their own and explore it, but I noticed that is so feature rich that such process may take months and it is annoying when you are on a rush.

Thanks for the feedback.

@jdaviescoates Yes, that's right. You get access to all extensive features, check the list here: https://chevereto.com/features#list

Chevereto has two editions (Free and Pro) where Pro has all features included. There may be more editions in the future, like a "Hobby" tier or even an "Enterprise" edition with extra stuff like SSO/LDAP. Will run a survey later this year to determine that offering.

Well, it seems that I can stir this a little bit.

By when I participated here I had this dilemma regarding editions in Chevereto, that's all over as since 2022-11-30 I've been pushing Open Source Chevereto edition. Here the very first release: https://github.com/chevereto/chevereto/releases/tag/4.0.5 (you can learn more here: https://rodolfoberrios.com/2022/12/01/chevereto-goes-free/)

I also have this container registry with about 28K downloads for Chevereto: https://github.com/chevereto/chevereto/pkgs/container/chevereto and I recently started this DockerHub mirror here: https://hub.docker.com/r/chevereto/chevereto

Chevereto free edition is now available on Pikapods, Vultr Marketplace, DigitalOcean Marketplace and more. I think that it will be a great addition to Cloudron, I mean, come on.

I think that I will just write a guide on my docs on how to deploy the custom Chevereto image. I feel that my intervention here is going nowhere... I just noticed that I went from bootstrap to container registry and now again we are talking about bootstrap.

I've the code and will, you know where to reach me. I'm always available.

Thanks anyway.

@nebulon paid version is a different code base but it works with the same system requirements. One way to provide it is by each user creating its own image.

The alternative is this, the bootstrap version: https://github.com/chevereto/docker which you can upgrade, the application is just mapped to a local bind dir.

Hey there, I've some great news.

We now have a container builder repository, here: https://github.com/chevereto/container-builder

What it does is that it uses github infra to build your own Chevereto paid edition image and upload it to the container registry of your choice. From there you can run your Chevereto image anywhere.

Does Cloudron allow users to provide their own container images? If that's feasible our paid users could use your panel

Let me know if you want more details about this.

@girish said in Vultr Marketplace:

Cloudron is now available in the Vultr marketplace - https://www.vultr.com/marketplace/apps/cloudron

Glad to see you guys there too!

@nebulon my bootstrap script gets you until the install form where the user will be prompt under HTTP to submit account details to proceed with the installation. It doesn't carry the installation as that process has account limitations (password length enforcement, forbidden usernames) but if you want to automate that bit you could simply detect the first run based on the container placeholder and execute the submitInstall installer command.

The installation at that step is just build the database, it doesn't touch the filesystem. As you may noticed, I left the installer.php available to use it as tooling on top of the images look at /chevereto folder in the container.

I suggest you to implement Chevereto on Cloudron using/forking my Docker images as I will constantly maintaining it, specially in regards to the PHP provisioning. That's why I provide separately Apache and PHP-FPM images, so you stop worrying about PHP regardless which flavor you like better. Use php-fpm if you want to handle the server, simply plug the process. Use Apache HTTP if you want to rely in mod_php.

Regarding your implementation, I can't recommend to use linking for the app/settings.php file, I recommend you to use env variables for that purpose. If user needs to sneak a setting it should be made by overriding the env variables, not working on the same file used for app/settings.php dist. If the user needs to add something at "settings level" it should be made with a file made for that sole purpose.

Dear all,

I have crafted the official Docker provisioning for Chevereto. The images are available here: https://hub.docker.com/r/chevereto/chevereto

These provide httpd-php and php-fpm images with a bootstrap script that runs on container creation, so it installs the software once and just spawn services from there.

Let me know if this helps to get Chevereto on Cloudron.

@nebulon sure, I understand. I have been updating things to make it compatible with the immutable realm. I need to tweak my installer to support tagged releases which at this time it only works with latest, I will work on that.

Most work is on the actual application code, my goal is 12-factor. Regarding the settings file I'm now using env, I've updated that recently https://v3-docs.chevereto.com/setup/system/settings-file.html

You can check the images here https://github.com/chevereto/docker is a live wip atm.

I've created a installer shell script, this will ease the provisioning a lot.

cd ../data/public

curl -sSL https://raw.githubusercontent.com/chevereto/shell/main/chevereto-free.sh | sudo bash -s -- \
    -h ${CLOUDRON_MYSQL_HOST} \
    -p ${CLOUDRON_MYSQL_PORT} \
    -n ${CLOUDRON_MYSQL_DATABASE} \
    -u ${CLOUDRON_MYSQL_USERNAME} \
    -x ${CLOUDRON_MYSQL_PASSWORD} \
    -w http://localhost/ \
    -A admin \
    -E admin@localhost.loc \
    -X password \
    -f ${CLOUDRON_MAIL_FROM} \
    -i inbox@localhost.loc \
    -m community

^^^ You need to customize the -A -E -X and -i options.

The repo is here: https://github.com/chevereto/shell

@nebulon I was able to play a litte bit, it seems that it will be trivial to get it running: https://chevereto-lamp.demo.cloudron.io/

Running these from app/data/public folder:

wget -O installer.php https://chevereto.com/download/file/installer

php installer.php -a download -s chevereto-free

php installer.php -a extract -s chevereto-free -f chevereto-pkg-*.zip -p .

php installer.php -a createSettings \
    -h=${CLOUDRON_MYSQL_HOST} \
    -p 3306 \
    -n=${CLOUDRON_MYSQL_DATABASE} \
    -u=${CLOUDRON_MYSQL_USERNAME} \
    -x=${CLOUDRON_MYSQL_PASSWORD} \
    -f app/settings.php

php installer.php -a submitInstallForm \
    -w http://localhost/ \
    -u user -e user@hostname.loc \
    -x password \
    -f from@hostname.loc \
    -i inbox@hostname.loc \
    -m community

rm -rf installer.php

My installer has a CLI API, I've updated the documentation today.

https://github.com/chevereto/installer

I'm a software developer from Chile. I created https://chevereto.com about 14 years ago and I've some other projects, I'm mostly into development of self-hosted software. I'm also a metallurgical engineer, 35 years old.

I also speak Spanish and I'm looking forward to distribute my software to more users. Thanks cloudron for providing this tool for guys like us.

@nebulon Thanks for the welcome, I don't have any reason besides that the Open Source edition doesn't have the paywall so it feels like a more straightforward approach for the new user. Both editions run on the exact same stack, I've some live demo right here: https://github.com/chevereto/docker as I've been optimizing support for containers lately.

What I'm trying to do is to provide servicing using container layers and sit the application as a project folder. That way the application manages itself its updating and the user can carry their modifications, I will be happy to review alternatives and share different strategies.

I make chevereto, there's an open source edition https://github.com/chevereto/chevereto-free

Let me know what I can do to help in the process.