Since the call for action was rather on short notice and only @msbt replied so far
I'll postpone to another date.
Creating a new poll for dates

@samuelhalff
We can look at it in the workshop

HeyO

@msbt // @timconsidine // @kubernetes // @Neiluj (did you rename to @teiluj ?) // @luckow

Should we do this on the 29.11.2025 (tomorrow) at 20 o'clock CEST Timezone?

@privsec said in Connecting the LAMP app with Git:

(I want to push to this directory, rather then to public)

Note on that.
The action runs:

cloudron push --app ${CLOUDRON_APP_ID} ${GITHUB_WORKSPACE}/. ${CLOUDRON_PUSH_DESTINATION}

Be aware of the /. after ${GITHUB_WORKSPACE}.
From the cloudron cli:

cloudron push --help
Usage: cloudron push [options] <local> <remote>

push a single local file or directory to a remote directory

Options:
  --app <id/location>  App id or location
  -h, --help           display help for command

  Examples:

    $ cloudron push --app myapp file.txt /app/data/file.txt # pushes file.txt
    $ cloudron push --app myapp file.txt /app/data/         # pushes file.txt. trailing slash is important
    $ cloudron push --app myapp dir /app/data               # pushes dir/* as /app/data/dir/*
    $ cloudron push --app myapp dir/. /app/data             # pushes dir/* as /app/data/*
    $ cloudron push --app myapp dir/subdir /app/data        # pushes dir/subdir/* as /app/data/subdir/*
    $ cloudron push --app myapp . /app/data                 # pushes .* as /app/data/*

Meaning, if you set CLOUDRON_PUSH_DESTINATION: "/app/data", yes, everything in the GitHub repository will be pushed to /app/data, but be aware, this does not delete existing files.
So, if you have the file /app/data/historic.txt and this is not in your GitHub repo, after the action has run, this file will still exist.

This could be seen as inconvenient, but, let's take the following scenario:
You have the folder /app/data/static/images which holds all your static image assets and in the GitHub repo you have static/images/.gitkeep an empty folder that is still tracked by git but empty.
If I changed the GitHub Action to overwrite the CLOUDRON_PUSH_DESTINATION instead of copying into it, all the /app/data/static/images files would be deleted.

Just wanted to make you aware of that

Ah, yes, CLOUDRON_URL is a misleading variable name, changing it to CLOUDRON_FQDN.
So the documented example of my.demo.cloudron.io is correct.
I have updated the GitHub Action repo, Example Repo and Cloudron documentation (will be deployed soon) accordingly.

I have added the demo branch to demo GitHub project https://github.com/cloudron-io/github-action-test-repo and the file .github/workflows/deploy-to-my-demo-cloudron-io.yaml which is using a clear text token, url, and appid for better understanding and only deploys on the demo branch.
You can use this file as a copy-and-paste example for testing.
But be aware, the APP_ID and TOKEN might be outdated anytime if the my.demo.cloudron.io server is reset or someone deletes the app.

HeyO

Now there is this GitHub Repository: https://github.com/cloudron-io/cloudron-push-to-app which publishes this action to the GitHub Marketplace https://github.com/marketplace/actions/cloudron-push-to-app

The README should explain how to use it.
Still, this can be confusing for people who never used GitHub actions.

I have created a demo repo https://github.com/BrutalBirdie/github-action-test-repo and added the workflow according to my README.
Added an Environment:

and the secrets:

Now if I update the README.md, add a simple index.html and index.css it will be deployed to https://default-lamp.cloudron.dev/ when accessing https://default-lamp.cloudron.dev you should see some neon 404 page and you can access the README.md https://default-lamp.cloudron.dev/README.md

And in the action view you can see the executed action and logs https://github.com/BrutalBirdie/github-action-test-repo/actions/runs/19704245518/job/56447718391

This looks very fancy / flashy.
Reminds me of old movies with the typical "I'm in!" hacking stuff

To get this rolling I created a rally poll.
For everyone interested, please check what times would suit you.
Note: according to Rally there is Automatic Time Zone Conversion

https://meetup.hackradt.com/invite/82X55UL0gnZ0

Thanks @james !
Indeed, LibreChat with an RC we could do fork a package, adjust, build, install and test for release candidates.

Hello everyone

I got the idea in my head to host an app packaging "webinar" with a hands-on approach.
Would some of you people be interested in such an event?

The idea would be start with basics, like:

• getting started with docker and the cloudron cli
• changing the version of an already existing app and deploying
• customizing an app
• understanding the read-only nature of cloudron apps

The minium requirement to join would be to bring at least 1 hour of your time and being able to work with a terminal.
(Also maybe streaming this event so it can be watched live and viewed later - YouTube private stream with URL shared in the Forum?)

If you'd like this type of event please let me know here so I can gather some insights and prepare such an event.

Cheers,
~BrutalBirdie

@ccfu said in perpetual licensing:

But out of interest: How much would you be willing to pay for a perpetual license? And how much for an (optional) support contract?

I co-sign this question

HeyO @TheMeerkat
Done

https://github.com/BrutalBirdie/cloudron-foundryvtt/releases/tag/13.348

How to update was discussed multiple times

To the Horillia enthusiast
I am looking for alpha testers of the Horilla Cloudron app.

Public installation with demo data for testing

https://horilla.cloudron.app.cloudron.dev/

Login is admin:admin

I can reset this setup anytime to the default demo state if needed.

Custom private installation

You need the Cloudron CLI

Login to your Cloudron instance:

cloudron login my.$DOMAIN.$TLD

Clone the code:

git clone ssh://git@git.cloudron.io:6000/playground/horilla-app.git
cd horilla-app
git checkout develop

Install the app:

cloudron install  --location $YOUR_CUSTOM_SUBDOMAIN --image brutalbirdie/horilla.cloudron.app:0.0.11

I have added a doc.md file for common task: https://git.cloudron.io/playground/horilla-app/-/blob/develop/doc.md?ref_type=heads

IMHO!
all these chat tools started of good and over the time get afflicted by the curse of greed.
I know that Mattermost is the closest to Slack and that is why understandably it still is so popular.
But same with Rocket.Chat, stripping down the FOSS version more and more to force people into subscriptions.

When I get asked "Hey, what chat tool should we use with Cloudron?"
If you don't need a deep integration with ticket systems and such, just use Matrix/Element.

I also pay for multiple subscription services, including Cloudron.
But there is a difference in my head between them.

I would also be very happy to pay for features once and then own them.
A good example would be the module system from Freescout.
I can buy e.g. the End User Portal and then own it.
No monthly fee for having this "feature".

Or another service I use where the whole service is free and only the "expert" features that need special maintenance I can subscribe to as an extra.
But with the last example, I have the whole core functionality for free and need only to pay for the singular "expert" feature I need.
Still would prefer to pay once and then be done with it. But I also understand that certain features require very regular maintenance which I don't want to or simply can't do.
But I rather pay for the singular feature instead of one big chunk of money that cross finances everything else I don't want/use/need.

This is a touchy and complex topic in the current time of "You will own nothing and be happy".
With services and digital products, I can understand it to certain degree.
But don't get me started with physical products that turn existing features into a subscription.
Looking at you BMW trying to sell a "heated seats subscription"!
We as consumers need to be way more vocal and strict when companies try this.

Sorry, little rant from my side

@d19dotca said in Sharing custom SpamAssassin Rules:

I have also been tinkering with the spam rules again the past month, testing some things out. I’ll go into more detail with that soon with updated scores that I’m using. I wanted to do a bit more analysis of it today actually to make sure it’s in the right direction before sharing it, but I’ll likely be in a position to share it pretty soon.

Signed up, hope to see you there

@marcusquinn maybe

@jdaviescoates yes and no
I've started this business this July, and I am still operating on a mouth-to-mouth basis.
Already did hint some things here and there like https://forum.cloudron.io/post/109822
But if you want some details, you can send me a DM

I am also offering Cloudron hosting including licenses with discounts.