ladybird VS docker-http-https-echo

You're in luck, Andreas has been hacking on that since a couple of months. They're calling the Linux version of the browser Ladybird: https://github.com/awesomekling/ladybird

LadyBird

Why not ladybird? https://github.com/awesomekling/ladybird

The page loads fine in Ladybird[1] on Arch. It's the browser purpose-built for SerenityOS[2] using a in-house HTTP/JS/TLS engine that hasn't matured to the point of practical usability yet. If I were a site administrator using some kind of weird metric to block a browser, this thing would definitely go on the blacklist.

As for a more common uncommon browser, GNOME Web (WebKit) also works fine.

Whatever is causing you to get blocked, it's not the browser engine you're using. Check your plugins, antivirus, MITM engines, and whatever else messes with your connection. It could also be a simple IP block because of a bad IP neighbour or a shared CGNAT server.

[1]: https://github.com/awesomekling/ladybird

[2]: https://serenityos.org/

Ooh, ooh.

I'm on Ubuntu, and it looks like I need to upgrade to 22.04 before I can experience the build process for myself.

https://packages.ubuntu.com/search?suite=jammy§ion=all&a...

The repo itself is shockingly tiny: https://github.com/awesomekling/ladybird. Looks like it needs https://github.com/SerenityOS/serenity as well. https://github.com/SerenityOS/serenity/tree/master/Userland/... is 100kLoC which is also surprisingly small.

I do not have a documentation, but I do disaster recovery tests from time to time. This is how you can try it out:

- download the ISO of a linux distribution, Arch is good because you have continuous updates (there is no "version")

- start it on a VM engine (VirtualBox, Hybersomething in Windows, VMWare, ...)

- from that point on - start documenting

- try to on docker install a program you know that is not too complex network-wise or just start with "hello-world" (https://hub.docker.com/_/hello-world)

- you will find that when running "docker pull hello-world", docker is not installed

- install docker on Arch according to Arch docs. DOCUMENT that step

- retry, hello-world works

- now try something like https://github.com/mendhak/docker-http-https-echo

- you will learn the basics of docker networking, read some docs or just try until you have a curl call working

- at that point you can try a program you know (nextcloud, syncting, ...), pulling it from docker hub and make it work. pay attention to two things: the network and the persistent volumes (I recommend, at least for the start, the file-based ones, not the docker ones)

- grab a beer, you are 90% done, good work

- have a close look at Caddy - this is a web server similar to apache, nginx but MUCH much better. So much better that I have no words.

- you will use it as a proxy server for your containers, so that you can get to them via https://nextcloud.yourdomain.com. It os worthwhile to get your domain even if you do not expose anything because things are much easier that way (caddy will manage the TLS part)

- now learn docker-compose and add all your dockers to it (it is a YAML description of your containers).

- add backup, this will be easier if you add this program on the OS itself (it can sure be in a container but I preferred having that part independent). I recommend Borg despite its few poor choices in the design (that are not likely to bite you at that point)

TADAM! you are done.

You are independent of th eOS, if you want to install fedora or whatever it just doe snot matter because i) all your programs are maintained by someone else (than you to the maintainers, it is nice to donate sometimes) and ii) your backup is data that is easily pluggable back to a ne instance of the software

Testing new programs is super easy (you just add them to the doclker compose YAML).

I truly recommend you try with a VM and you will quickly realize it is time to reformat your server and put everything under docker :) AMA if you have questions.