@jdaviescoates yea exactly
Also, a lot of YouTube coverage on that with millions in the view counts.

Done
https://git.cloudron.io/playground/teamspeak6-server

Quick test - copy and paste this into your local terminal:

cd /tmp/
git clone https://git.cloudron.io/playground/teamspeak6-server.git
cd teamspeak6-server
cloudron install --location ts --image brutalbirdie/com.ts6server.cloudronapp:0.0.1

Installed on the demo server: https://my.demo.cloudron.io/#/app/b3c583c4-18f1-4b47-94a0-e2f7bcf5496f/info (temporary until uninstalled or demo server resets)
If you'd like to connect, you need the TeamSpeak 6 Client and you can use the FQDN to connect: ts.demo.cloudron.io

• Main Page: https://www.teamspeak.com/en/
• Git: https://github.com/teamspeak/teamspeak6-server
• Licence: https://github.com/teamspeak/teamspeak6-server/blob/main/LICENSE.md
• Dockerfile: No
• Demo: X

• Summary: This TeamSpeak 6 Server Beta repository contains the latest beta version of the TeamSpeak 6 Server software, offering early access to improvements and bug fixes. This beta release is intended for testing and feedback before the stable version launch.

• Notes:
  Current Discord controversy drives people back too TeamSpeak.
  Why not offer the Version 6 as well.

I took a quick look.
An installation test revealed one problem.
The start.sh file in the repo does not have the execute permission bit set leading to the following error when installing the app:

App installation error: Installation failed: (HTTP code 400) unexpected - failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/app/pkg/start.sh": permission denied

I have created a PR that you can merge to fix this issue:
https://github.com/stalecontext/filestash-cloudron-app/pull/1

@murgero
Are you talking about the CUR?
Very happy to see this comming to Cloudron!

Updated the app to version 13.351.

• GitHub: https://github.com/BrutalBirdie/cloudron-foundryvtt/releases/tag/13.351
• Dockerimage: https://hub.docker.com/repository/docker/brutalbirdie/foundryvtt.cloudron.app/tags/0.1.1/sha256:3f1c96849458265eecb4edea58532f686eb644eda1f4533b3995bd007a9e7f9a

Update:

cloudron update --app $YOUR_APP_LOCATION --image brutalbirdie/foundryvtt.cloudron.app:0.1.1

Big Love @d19dotca

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