Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f

I think this happenned because the docker repository was specified incorrectly when you did cloudron build. You can always cloudron build --set-repository again and it will ask you again for the repository name. The repo name should like girish/cloudron-uptime-kuma or something like that. The first part is your handle on docker hub (or equivalent). The second part is the repository name. In docker terminology, a repo is something that holds many images.

@timconsidine Perhaps I should change my instructions?

errr, I'm not qualified on that !
I blunder about, find what works for me and tend to stick to that.

docker build -t <myrepo>/<appname>:<tag> .  
docker push <myrepo>/<appname>:<tag>
cloudron install --image <myrepo>/<appname>:<tag>

NB the trailing dot on 1st line
With this the build/install was seamless
Kuma now working brilliantly and I have deleted my UptimeRobot account.

thanks again @atridad

Any docker wizards here who might have some insight?

I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.

I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.

Any help would greatly be appreciated!

Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f

invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
See 'docker build --help'.
node:child_process:903
    throw err;
    ^

Error: Command failed: docker build  -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile  /Users/michael/Downloads/cloudron-uptime-kuma-app
    at checkExecSyncError (node:child_process:826:11)
    at execSync (node:child_process:900:15)
    at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5)
    at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9)
    at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31)
    at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14)
    at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18)
    at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12)
    at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) {
  status: 125,
  signal: null,
  output: [ null, null, null ],
  pid: 9877,
  stdout: null,
  stderr: null
}

Just looked at Zabbix - thank looks amazing! Are we getting that as an App?

Upvote!
https://forum.cloudron.io/post/1211

• status.brandlight.org
• status.healthshop.net

Statping's OK but the red-marks for a whole day when there's only been an out of hours reboot looks worse than things really are.

twilio.com or bulksms.com both good for cheap SMS if needed, although you'd think free Push notifications would be preferrable.

Just looked at Zabbix - that looks amazing! Are we getting that as an App?

Monitoring tool: UptimeRobot
Status page tool: InStatus

Side topic... Using Webhooks notifications inside UptimeRobot to the InStatus service status page, the Webhooks allow for custom responses and component statuses too which is super nice. Of course nobody really checks my status page unless I sent out major maintenance notifications, lol, but I offer it anyways and find it a fun project to work on. Tip: Include your status page URL in the Cloudron custom maintenance page when apps are unavailable. The Status Page project make me feel (and possibly look) like a much bigger company than I really am. haha. My clients like it though, as they know I communicate through the Status Page whenever any maintenance is being done which impacts them at all.

PS - I realize I went a little off-topic there with the status page component, but I am just really happy about the solution and want to also send some possible customers his way too, much like how I like to point customers to Cloudron when possible.

https://www.zabbix.com/documentation/current/manual/installation/install_from_packages/debian_ubuntu