Suggestions for supported appliances

[alb-pal]

trafficstars

This is a very promising project that goes well with the ipv6rs service, which I may not have heard about were it not for Cloudseeder.

Looked at your websites and did not see anything about another place to make suggestions, so I hope it is OK to file one here as an issue.

There are two services that I think would be great to have as appliances, which I self-host currently on a VPS but would love to have streamlined (and more local) in Cloudseeder to use with ipv6rs instead if possible:

• Meshcentral (https://github.com/Ylianst/MeshCentral) for coordinating remote access to computers even if they do not have public addresses
• any self-hosted VPN option (Wireguard would be good!)

Thanks!

[ipv6rs]

Thank you!

These are excellent suggestions and we will add it to our queue to add as appliances. Keep in mind that, with IPv6rs, you will only be able to serve over IPv6 as Wireguard does not support Server Name Indication (SNI) as it is not using TLS at all, thus we are unable to blindly forward that traffic over our reverse proxy.

I will keep this open and update when support for these arrive!

[alexkaeh]

Amazing project, I was looking into self hosting an RSS feed reader. These appear to be the two popular self-hosted options:

• FreshRSS
• Miniflux (very minimalist UI)

[ipv6rs]

While it's not a VPN @alb-pal we incorporated an HTTPS proxy which may be less easy to detect. It's the Shrimp ( https://github.com/ipv6rslimited/shrimp ) which is packaged on Cloud Seeder!

[ipv6rs]

https://www.youtube.com/watch?v=iLA5oOOlK6o

This video shows the double hop, one-hop controlled, proxy in action by the way!

[ipv6rs]

@alexkaeh We have added Miniflux! Please enjoy!

[blaisep]

Is there an API or SDK for building cloudseeder appliances? I would imagine something like FlatPak or Snap .... I want to package Forgejo instead of Gitea, for example.

[dev-ipv6rs]

Hi @blaisep

We are using Podman to build each appliance using a standard Dockerfile.

You can add your own custom appliances to Cloud Seeder by creating a sideload.json file in ~/.ipv6rs This is in the same format as the ~/.ipv6rs/appliances.json file.

With your custom Forgejo appliance, it might look like this:

[
  {
    "title": "Forgejo",
    "short": "forgejo",
    "version": 1,
    "description": "My Forgejo Appliance",
    "requirements": "Requires:\n\n- IPv6rs WG Configuration\n- DNS AAAA record pointed to your IPv6rs IP\n- DNS A record pointed to your IPv6rs gateway IP",
    "action": "~/.ipv6rs/appliances/forgejo/config.json"
  }
]

As Forgejo is a fork of Gitea, I copied the ~/.ipv6rs/appliances/gitea dir to ~/.ipv6rs/appliances/forgejo and replaced line 21 in the Dockerfile with: wget https://codeberg.org/forgejo/forgejo/releases/download/v10.0.1/forgejo-10.0.1-linux-${arch} -O /usr/bin/forgejo && \

I replaced all other instances of "gitea" with "forgejo" in the Dockerfile, target.sh, install.sh and config.json files. I made sure to match case, so GITEA_WORK_DIR became FORGEJO_WORK_DIR. If you're using windows then you'll also need to edit the install.ps1 file.

And in this instance that was enough to get a working Forgejo appliance.

Let me know if you have any questions!