Rockstor Rock-ons that aren't quite production grade I built for my own deployment.
As per official docs you can just copy the JSON files in this repo to /opt/rockstor/rockons-metastore on your Rockstor instance to have the definitions available.
The Rock-ons in this repo are tweaked to offer exactly the customizability I require and nothing more. This means I may have left out the configurability of some environment variables. Further the configuration flow should be streamlined for most of them to require less duplicate inputs.
| rockon | usability | working | upstreamed |
|---|---|---|---|
| funkwhale | env config and user setup is a bit cumbersome | ✔️ | |
| forgejo | easy - env v.s setup config a bit confusing | ✔️ | |
| gitea | easy - env vs. setup config a bit confusing | ✔️ | |
| huginn | not used it much yet, possibly missing an env var to add additional agents | ✔️ | |
| matrix-synapse | synapse config and database setup has to be done manually. Use the internal IP of the postgres container to tell synapse where to look (docker network bridge is your friend). Coturn can only work as a TURN server, since rockons can't map docker port ranges. I'd love to add element as a web interface, however element needs a single file mapped in. Lastly env var input is a mess due to a bug in rockstor. Restarting the rockon fails if the db container was updated with watchtower. | ✔️ | |
| auto-invite-matrix-bot | need to manually add the config to the share. | ✔️ | |
| wallabag | submitted to the official rockon registry | ✔️ | ⏲️ |
| dnscrypt-proxy | requires configuration file to be manually created in config share for best experience. | ✔️ | |
| vikunja | Uses sqlite, so not well suited for multi-user operation. In order to create an initial account, registration has to be allowed, after that you have to re-create the rockon with registration forbidden if you don't want strangers to be able to sign up | ✔️ | |
| webthings-gateway | Port entry in wizzard is just for the UI link in rockstor. The container runs in host network mode, so if you want the container to bind to different ports, use local.json, as described in the container readme. If you want to use lbuetooth or zigbee, you'll have to modify the rockon definition accordingly. | ✔️ | |
| mautrix-telegram | Pretty simple to set up, with good documentation. However, requires linking a file to the synapse homeserver's container. | ✔️ | |
| mautrix-whatsapp | Pretty simple to set up, with good documentation. However, requires linking a file to the synapse homeserver's container. | ✔️ | |
| mautrix-signal | Pretty simple to set up, with good documentation. However, requires linking a file to the synapse homeserver's container. | ✔️ | |
| synapse-admin | Simple setup, rock-on candidate, but useless without matrix-synapse rock-on. | ✔️ | |
| gotify | Simple to use, PR against registry | ✔️ | ✔️ |
| renovate | Extremely simple setup, but relies on a config file generated by the CLI tool. | ✔️ | |
| drone | Set up for usage with the gitea/forgejo rockon, provides a single runner. | ✔️ | |
| chrony | Super simple if you know a friendly neighbourhood NTP server to chain from | ✔️ | |
| zigbee2mqtt (+mosquitto) | Needs an initial config file to be manually generated. | ✔️ | |
| nextcloud-plus | Built to migrate from an existing nextcloud official + postgres setup to this. | ✔️ | |
| up-common-proxies | Simple to set up. | ✔️ | |
| calibre | ✔️ | ||
| synatainer | SImple to configure via env vars. | ✔️ | |
| bonob | Config via env vars, customized to what my setup needs. | ✔️ | |
| ntfy | Configuration via config file recommended. | ✔️ |