Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Uptime Kuma
  3. Free off-site monitoring with Fly.io and Uptime Kuma

Free off-site monitoring with Fly.io and Uptime Kuma

Scheduled Pinned Locked Moved Uptime Kuma
monitoring
3 Posts 2 Posters 1.9k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • fbartelsF Offline
      fbartelsF Offline
      fbartels
      App Dev
      wrote on last edited by
      #1

      Hi everyone,

      I saw a post yesterday on Reddit showing how to use the Google Cloud free tier to run Uptime Kuma. One of the alternatives for free hosting mentioned in the post was fly.io and since their tooling intrigued me I have since then started hosting Uptime Kuma on their platform (combined with notifications through Telegram to be as independent from my own infrastructure as possible).

      Their free tier includes a vm to run own code or a docker container along with 1cpu and 256mb of ram. this can be coupled with a persistent storage volume of 3gb, so plenty of resources for Uptime Kuma. In addition to this they allow usage of own domain names so you can have your status page at https://status.mydomain.com instead of on one of their subdomains.

      All you need is the following toml file to deploy the Uptime Kuma container on fly.io:

      # fly.toml file generated for mykuma
      
      app = "mykuma"
      
      kill_signal = "SIGINT"
      kill_timeout = 5
      processes = []
      
      [build]
        image = "louislam/uptime-kuma:1"
      
      [mounts]
      source="kuma"
      destination="/app/data"
      
      [env]
        PORT = "8080"
      
      [experimental]
        allowed_public_ports = []
        auto_rollback = true
      
      [[services]]
        http_checks = []
        internal_port = 8080
        processes = ["app"]
        protocol = "tcp"
        script_checks = []
      
        [services.concurrency]
          hard_limit = 25
          soft_limit = 20
          type = "connections"
      
        [[services.ports]]
          force_https = true
          handlers = ["http"]
          port = 80
      
        [[services.ports]]
          handlers = ["tls", "http"]
          port = 443
      
        [[services.tcp_checks]]
          grace_period = "1s"
          interval = "15s"
          restart_limit = 0
          timeout = "2s"
      

      The configuration refers to a volume called "kuma", which needs to be created before the app can be deployed by running flyctl volumes create kuma.

      I have written a bit more in detail about on on my blog: https://blog.9wd.eu/posts/flyio/ (first draft status, may need refinement)

      1 Reply Last reply
      13
      • girishG girish moved this topic from Discuss on
      • humptydumptyH Offline
        humptydumptyH Offline
        humptydumpty
        wrote on last edited by
        #2

        Hi Felix. Thanks for the guide. How is updating the app handled?

        fbartelsF 1 Reply Last reply
        0
        • humptydumptyH humptydumpty

          Hi Felix. Thanks for the guide. How is updating the app handled?

          fbartelsF Offline
          fbartelsF Offline
          fbartels
          App Dev
          wrote on last edited by
          #3

          @humptydumpty to reliably update i ended up always updating the docker tag to the desired version. With the tag updated you just need to run flyctl deploy again.

          1 Reply Last reply
          2
          • fbartelsF fbartels referenced this topic on
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search