Uptime Monitoring
-
@mazarian just to provide some some other experience, I downloaded @atridad repo files, but I did not use
cloudron build
. I went "the long way".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
-
@timconsidine Perhaps I should change my instructions? @staff does the cloudron build command do some extra stuff that would be causing this?
-
@timconsidine Thanks for this! I'm not sure how much of my issue had to do with my Mac environment but I was able to get it all setup using Ubuntu using your method and it worked like a charm!
-
@atridad said in Uptime Monitoring:
@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. -
@timconsidine lol with packaging I'm the same way tbh. Cloudron was my first time editing or making a Dockerfile
-
@mazarian said in Uptime Monitoring:
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 alwayscloudron build --set-repository
again and it will ask you again for the repository name. The repo name should likegirish/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.