Caddy VS awesome-selfhosted

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

I think that recompiling with upgraded Go will not solve the issue. It seems Caddy imports `golang.org/x/net/http2` and pins it to v0.22.0 which is vulnerable: https://github.com/caddyserver/caddy/issues/6219#issuecommen....

Caddy [1] is a single binary. It is not minimal, but the size difference is barely noticeable.

serve also comes to mind. If you have node installed, `npx serve .` does exactly that.

There are a few go projects that fit your description, none of them very popular, probably because they end up being a 20-line wrapper around http frameworks just like this one.

[1] https://caddyserver.com/

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

So I dug a little deeper and came across this gem: Caddy. Caddy is this fantastic, extensible, cross-platform, open-source web server that's written in Go. The best part? It comes with automatic HTTPS. It basically condenses all the work our scripts and manual maintenance were doing into just 4-5 lines of config. So, stick around and I'll walk you through how to set up an automatic SSL solution with Caddy, Docker and a Node.js server.

Let's use Caddy which can act as reverse-proxy with automatic HTTPS coverage.

Even if it may be simple, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632

I personally would make the trade off of taking on more complexity so that I can have extra compatibility.

One of the most heavily used Russian software projects on the internet https://www.nginx.com/blog/do-svidaniya-igor-thank-you-for-n... but it's only marginally more modern than Apache httpd.

In light of recently announced nginx memory-safety vulnerabilities I'd suggest migrating to Caddy https://caddyserver.com/

My preferred solution is using Caddy. This will resolve the networking issues, work as a great reverse proxy, and takes care of the whole SSL process for us. We can follow the install instructions from their documentation and run these five commands:

None of these lists ever seem to be as fleshed out, up to date, or well organized as https://github.com/awesome-selfhosted/awesome-selfhosted , though imo any more attention on the self hosted scene is awesome. We're now self hosting everything at my co-op, and it's a dream. Saves us money, provides learning opportunities, potentially is getting us work (managed hosting providers asking if we can be a devshop for their clients, for example), and lets us give back to the FOSS community as we uncover bugs.

We use:

* Matrix / Synapse for comms (slack alternative) (managed hosting through etke.cc)

There are a ton of resources about HW aspects of home labs for beginners but not so much for what to run on them and why. There are lists like https://github.com/awesome-selfhosted/awesome-selfhosted but they are confusing for absolute beginners like me. Are there any good SE project guides you know?

This[1] seems like a well maintained repo.

And thank you for the pointers, we'll try to get ourselves added here :)

[1]: https://github.com/awesome-selfhosted/awesome-selfhosted

I've always felt like FOSS as a philosophy has been tangled up in trying to participate effectively in capitalism, when that was never really the point, nor really very possible unless you're lucky, nor really worth it. The origin of FOSS as I understand it from reading books like "Hackers" is from people that were mad that access was being restricted to systems and code from people that really wanted to use these systems and code, and hack them, and learn from them. I recall that one of the things Stallman likes to brag about from that time is not related to FOSS at all, but instead successfully decrypting a bunch of passwords, emailing the decrypted passwords to people, and recommending they instead set the password to an empty string instead. It was about keeping access to the system Free as in Beer.

I suppose some have argued that FOSS represents a Public Commons in the way that fields and wells and physical markets used to, but none of those things survived capitalism, so I don't see why a technological commons should be expected to either.

For me I've been thinking lately that perhaps those interested in FOSS should instead consider how we can use FOSS to detach ourselves from needing to participate in global capitalism at all. Is there FOSS technology we can use to liberate people from things they need to spend money on right now? An example could be the Global Village Construction Set: https://www.opensourceecology.org/gvcs/ a set of open source designs for things like hydraulic motors or microcombines or steam engines that you can build on your own, usually not for cheap, but for far, far cheaper than you could buy from John Deere. Here's another cool project, some guy has just been building things like solar panels and basic circuit boards on his property from very base components for years: https://simplifier.neocities.org/

Some other FOSS liberation examples:

Combining a tool like Jellyfin with Sonarr, Radarr, and etc, can liberate people from their 5 different media subscriptions. Or at least they can still buy DVDs and put them on Jellyfin to have the convenience of streaming with the media library of their own choosing.

Deploying Matrix or another FOSS communication tool can let organizations have enterprise-level communication software without paying HUGE seat-based license fees to corporations like Slack.

In fact there's many ways to liberate yourself from paid SaaS in this list: https://github.com/awesome-selfhosted/awesome-selfhosted at my co-op we self-host and deploy all our services for this reason, it saves us a TON of money.

I don't have many other examples to mind because this is something I'm actively still researching. Friends in Venezuela though especially tell me how FOSS technology can liberate in ways I wouldn't expect here with my 64gb RAM machine with the latest processor, that I can easily replace components on on a whim. Such as how they can keep all their broken down machines pieced together from junkyards running pretty ok on various linux distros, and how they can sell creative work using free tools like gimp (no, really) or darktable. Like as not they'll just pirate software, though, but apparently FOSS often runs better on shitty hardware.

Anyway my long term plan is to find or build more and more things that let people just not spend money on things anymore. That could be by making it easier to not have to throw things away anymore, or building tools to replace proprietary ones, or, idk, other ways I haven't thought of.

Dashboard in what sense? Is this what you had in mind or no?

https://github.com/awesome-selfhosted/awesome-selfhosted#per...

I often skim through various "awesome lists" (e.g. [1]) and communities interested in open source apps like r/selfhosted [2]

[1] https://github.com/awesome-selfhosted/awesome-selfhosted

[2] https://www.reddit.com/r/selfhosted/

1. https://nextcloud.com/ https://proton.me/drive https://github.com/awesome-selfhosted/awesome-selfhosted#fil...

2. Download all data locally then upload elsewhere.

3. https://help.dropbox.com/security/privacy-policy-faq#7.-How-...