arozos VS mkcert

Using this function and, if you have a few nodes with "ArozOS" installed, you can easily add all nodes into the Zoraxy WoL table and kick start them one by one remotely.

TL.DR. I wrote a reverse proxy system for my Web Desktop OS back in 2019, later on I added in tons of other web routing features I need like redirections, blacklist + geo-ip, Zerotier controller and so on. Finally it become the reverse proxy version of swiss knift for my distributed homelab setup.

Hope you like this project! We are continuing updating the modules of this system to better fit our use cases. If you are interested to try it out or even contribute to this project, feel frees to find the source code and give us a star 🌟 in the attached Github link below.

u/survivalmachine As mentioned in previous comments, I am working on a Web Desktop OS project in which I want to add SMB support (both client and server). I already got SMB client working based on go-smb2.

If you are a long time user of my open source web desktop system ArozOS, the chances are, you might never notice there is actually a hidden humans.txt file in your web root. Here is my system hosting on my tiny server powered by a orange pi zero 2 single board computer.

Recently, I encountered another issue when I am trying to migrate my whole Google Drive to my own ARM powered DIY NAS. The issue was that my NAS only have 512MB + 32GB (microSD card) as OS drive, while I have 2 x 512GB HDD attached to the SBC to store files. Uploading a file with size >32GB will causing the system to run out of space and crashing my ArozOS NAS OS .

I have recently been traveling to another city. That is why I brought with me my trusty NUC installed with Debian + ArozOS besides my laptop. As this is my first time loading a few TB worth of files into this system, I soon running into issues where all the files I uploaded to the NUC is hard to find and I don't know what I have uploaded to the web desktop interface. This is how the systems look like before I start traveling.

I have been working on an open source web desktop system called ArozOS for 3+ years now. In simple words, it is a web desktop system that actually do works like a real OS.

Full version of the function is over here: https://github.com/tobychui/arozos/blob/7251f4bf945f22b8a08d4dcfdcf4618baf16ac75/src/file_system.go#L506

I own a few 3D printers so I decided to write myself a system to do cloud slicing and put it on Github. This is a few screenshots showing the slicer running on ArozOS Web Desktop System

The author mentions difficulties with HTTPS and trying stuff locally.

I've had some success with mkcert [1] to easily create certificates trusted by browsers, I can suggest to look into this. You are your own root CA, I think it can work without an internet connection.

[1] https://github.com/FiloSottile/mkcert/

Solution: mkcert – Your Zero-Configuration HTTPS Enabler Meet mkcert, a user-friendly, zero-configuration tool designed for creating locally-trusted development certificates. Find it on its GitHub page and follow the instructions tailored for your operating system. For Mac users employing Homebrew, simply execute the following commands in your terminal:

Well, Certifi does not ship with your company's certificates! So requesting internal services may come with additional painful extra steps! Also for a local development environment that uses mkcert for example!

My project, getlocalcert.net[1] may be the one you're thinking of.

Since I'm also building in this space, I'll give my perspective. Local certificate generation is complicated. If you spend the time, you can figure it out, but it's begging for a simpler solution. You can use tools like mkcert[2] for anything that's local to your machine. However, if you're already using ACME in production, maybe you'd prefer to use ACME locally? I think that's what Anchor offers, a unified approach.

There's a couple references in the Anchor blog about solving the distribution problem by building better tooling[3]. I'm eager to learn more, that's a tough nut to crack. My theory for getlocalcert is that the distribution problem is too difficult (for me) to solve, so I layer the tool on top of Let's Encrypt certificates instead. The end result for both tools is a trusted TLS certificate issued via ACME automation.

1. https://news.ycombinator.com/item?id=36674224

2. https://github.com/FiloSottile/mkcert

3. https://blog.anchor.dev/the-acme-gap-introducing-anchor-part...

Looks like step-ca/step-cli [1] and mkcert [2] have been mentioned. Another related tool is XCA [3] - a gui tool to manage CAs and server/client TLS certificates. It takes off some of the tedium in using openssl cli directly. It also stores the certs and keys in an encrypted database. It doesn't solve the problem of getting the root CA certificate into the system store or of hosting the revocation list. I use XCA to create and store the root CA. Intermediate CAs signed with it are passed to other issuers like vault and step-issuer.

[1] https://smallstep.com/docs/step-ca/

[2] https://github.com/FiloSottile/mkcert

[3] https://hohnstaedt.de/xca/

We use mkcert for this, it works wonderfully.

https://github.com/FiloSottile/mkcert

mkcert: This is used to obtain a trusted TLS certificate with a custom domain name for your development machine. You can install mkcert on your development machine following the official instructions.