v4.10.0

[lukevella]

What's Changed

🚀 Introducing the Rallly CLI

This is the first version of Rallly that supports the new Rallly CLI, which installs and manages your instance as a fully bundled stack (app + PostgreSQL + Garage object storage + Traefik reverse proxy with automatic Let's Encrypt).

curl -fsSL https://get.rallly.co | bash

The installer walks you through configuration, generates secrets, and brings everything up. Day to day operations go through:

./rallly.sh start | stop | restart | status | logs | update | backup

📖 Installation guide · Management guide · Migration guide

Important

If you're already running a self-hosted instance and would like to migrate to the new Rallly CLI, follow the migration guide.

✨ New Features

• Version tile in the control panel showing the running version and whether an update is available (✨ Add version tile in control panel #2355, ✨ Add updates api route #2351, ✨ Add instanceId to InstanceSettings (RAL-1156) #2348)

🐛 Bug Fixes

• Send poll response confirmation email in the respondent's locale (🐛 Send poll response confirmation email in respondent's locale #2356)

⚡ Performance

• Optimize invite page queries (⚡️ Optimize invite page queries #2350)

Full Changelog: v4.9.2...v4.10.0

---

This discussion was created from the release v4.10.0.

[cleverer]

While it's nice to see easy setup for beginners, i really dislike it when projects use a cli to start and manage docker compose stacks… it makes it really painful to use them in a GitOps environment and makes it impossible to use a supported install method on Kubernetes.

In my case, I have all my services in git repos which then are used as submodules in a master repo, more or less automating my deployments… and i plan on migrating everything to a self hosted kubernetes.

I do appreciate that external services are still supported as first class citizens (my Ceph/RadosGW is a different level of service than a bundled Garage). However, as someone that paid for the self-hosted license, i would really appreciate that a plain Docker image is still also a fully supported installation method and does not have braking changes in environment variables for example.

I would prefer a proper Helm chart bundling al the dependencies than a cli tool. Element Server Suite does this exceptionally well: their "beginner" installation guide is using k3s and guiding the user to install the helm chart, while still allowing experienced or professional users to run it according to DevOps best practices.

Is this still the case, or is everyone expected to use the rallly CLI now?.

[cleverer]

Ah just realized, that is still supported, if a bit hidden: https://support.rallly.co/self-hosting/configuration#running-the-image-directly

Could you clarify your plans regarding that use case?

[lukevella]

My motivation for introducing the CLI is to make setup and maintenance easier. Not everyone has the know how to set up an object store for example and now this comes bundled and wired up without any configuration needed.

Additionally, there will very likely be more services added in the future as the project grows. I've always hesitated to do this because I know adding more services has a significant impact to self-hosters. However the new CLI makes this less of a problem because you can simply run ./rallly.sh update and it will pull the latest compose config with any new services added and already configured.

So if you want the best experience, my recommendation is to use the CLI. If you know what you're doing you're welcome to use the image directly.