Skip to main content

Welcome to my indieweb blog, this is a place where I stock Bookmarks, Articles I'm reading or on my list, short notes and longer articles about my different interests.


Looking for a new challenge | Info Aggregation, Monitoring Disinformation,Veille |
Twitter bots 4 Good | Interest in Politics, Technology
Follow me here

rmendes.net

rick@rmendes.net

rMdes_

pixel.rmendes.net

indieweb.social/@rmdes

mstdn.social/@rmdes

mendes

hyper://a4fb38e6d60f38eca1fabefa683049a0275cfafc99fb6391b08c2c378e4d5b37

Ricardo

Ricardo

Cloudron 6.1 released https://blog.cloudron.io/cloudron-6-1-released/
Another amazing @cloudron_io release!

Ricardo

Really cool Tutorial live coding : Building an App for Cloudron - Matterbridge https://www.youtube.com/watch?v=RKcH2yJiLUo

Ricardo

[TUTORIAL] Building Cloudron Apps using Urgero.org's Ubuntu VM by urgero.org

This is a neat tutorial to get Cloudron running on a VM !
the docker/cloudron build step from the tutorial can be used to build/install for cloudron any docker image that exist around !

Link

Ricardo

Todo : https://docs.cloudron.io/guides/upgrade-php-lamp/ I have a few LAMP containers that I have to upgrade to latest PHP version, that's how it's done on cloudron

Ricardo

Install Cloudron Locally

Home testing cloudron unstable apps

2 min read

A domain is required for Cloudron (even if it's local network). Port forwarding is optional (it's only required if you want your server accessible from outside).

Here's how you do it. The setup is much simpler if you have a programmatic DNS provider (like DO, Cloudflare, Route53 etc). If you don't have this already, I recommend that you setup some subdomain into say DigitalOcean's DNS. For this, you have to setup a DO account and add cloudron.domain.com into DigitalOcean domains. Then setup NS records for cloudron.domain.com to point to Digital Ocean. Please give some 30 mins for NS records to propagate. Once this done:

  • Install Cloudron on a VM
  • Domain setup
    • Put the domain as cloudron.domain.com and set it up for DO DNS
    • Click on Advanced. Here, choose the Network Interface from the drop down and provide the network interface of the VM/server. Alternately, give it the static IP (give the local IP like 192.168.1.100 or whatever it is).
    • If your main domain domain.com and the subdomain cloudron.domain.com are on different DNS providers, then you have to put the zone name as cloudron.domain.com.
  • Finish setup - that's it!

What will happen is:

  • Cloudron will get LE certs via DNS. This is why the DO DNS setup was required. Without this, you will need port 80 forwarding for LE and it gets a bit complicated.
  • Cloudron will program your DNS with A entries of the local IP. So, my.cloudron.domain.com will actually point to 192.168.1.100. It's not publicly reachable.

Let me know if that works! Or if you have more restrictions in your setup.

Source

An IndieWeb Webring 🕸💍