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



  • I'm wondering what the best option (available in Cloudron) would be to deploy a static website (html/images/js/css)? I'm not interested in the overhead of Lamp and we don't have an nginx-only option yet which I think would be closer to ideal. Maybe Github Pages but I'm not sure how that works exactly as I don't really care to deploy to Github first.

    ** I'm looking for speed as a primary feature

  • App Dev

    you could give surfer a try

  • Staff

    +1 for surfer. it's just a very simple node app that servers static assets. There is also a CLI tool to push/pull your static assets.


  • @echokos Github Pages is easy if you know git decently. Im half retarded and I got it running. Ping me if you want a step by step.

  • Staff

    Also, GitHub pages doesn't require GitHub or anything!

    GitHub pages, as supported by GitHub, is really just Jekyll with specific supported plugins. What we have done is to support the same static page templating using https://github.com/github/pages-gem. The idea is that if you had deployed your site to GitHub pages previously, you can now easily deploy the same site with no changes to Cloudron using this app (or viceversa). So instead of pushing to github, you can push the very same site to the pages app.


  • @girish I'd love to see a simple "how to use gitea/gogs + github pages to create a hello world website on cloudron" 🙂


  • Interesting conversation. Thanks, all.


  • @echokos Did youcome up with an answer to this. I am looking to do the same and I can deploy a LAMP stack or Surfer to do a single static site but at a cost of 256MB each. What I would like is to be able to use one Surfer or LAMP stack to serve many domains.

    EG; 10 x static sites = 2560MB of usage in Cloudron whereas anywhere else I can serve 10 static sites with less that half that.

  • Staff

    @masonbee The memory limit setting is the "maximum memory" before which the app is killed for over use. It is not "reserved memory" i.e it's not pre-allocated to the app and thus cannot be used by any other app. The "maximum memory" simply ensures that a single web app cannot bring down the whole system.