I'm currently researching the best method for running a static website from Docker.

The site consists of one single HTML file, a bunch of CSS files, and a few JS files. On server-side nothing needs to be preprocessed. The website uses JS to request some JSON files, though. Handling of the files is doing via client-side JS, the server only need to - serve the files.

The website is intended to be used as selfhosted web application and is quite niche so there won't be much load and not many concurrent users.

I boiled it down to the following options:

1. BusyBox in a selfmade Docker container, manually running httpd or The smallest Docker image ...
2. php:latest (ignoring the fact, that the built-in webserver is meant for development and not for production)
3. Nginx serving the files (but this)

For all of the variants I found information online. From the options I found I actually prefer the BusyBox route because it seems the cleanest with the least amount of overhead (I just need to serve the files, the rest is done on the client).

Do you have any other ideas? How do you host static content?

Basically the title.

When I open lemmy.ml it says “posts, subscribed, oredered by new” on top:

But almost none of the posts shown are from my subscribed communities and they’re not ordered by new.

There are even posts from communities shown that I have on my block list.

Any idea how to fix that?

Since the new version was deployed to lemmy.ml which allows blocking instances I tried to block an instance.

When opening the drop down and enter the name/url of the instance (or even a part of its name) the list is then filled with a seemingly random list of instances but not the instace I searched for.

I tried in a desktop browser (Chrome on Windows) and in a mobile browser (Vivaldi Mobile, which uses Chromium as base), same behavior.

Since I don't use GitHub I report it here.

Currently I’m planning to dockerize some web applications but I didn’t find a reasonably easy way do create the images to be hosted in my repository so I can pull them on my server.

What I currently have is:

1. A local computer with a directory where the application that I want to dockerize is located
2. A “docker server” running Portainer without shell/ssh access
3. A place where I can upload/host the Docker images and where I can pull the images from on the “Docker server”
4. Basic knowledge on how to write the needed Dockerfile

What I now need is a sane way to build the images WITHOUT setting up a fully featured Docker environment on the local computer.

Ideally something where I can build the images and upload them but without that something “littering Docker-related files all over my system”.

Something like a VM that resets on every start maybe? So … build the image, upload to repository, close the terminal window, and forget that anything ever happened.

What is YOUR solution to create and upload Docker images in a clean and sane way?

In opposition to this post ... Name your most favorite upsides of software being federated.

Basically the title. When writing .. it is converted to …. Also every string being any amount of dots is also being converted to …, even when it makes no sense.

.. -> ..
../relative/path/file.txt -> ../relative/path/file.txt
................................... (used as visual separator) -> ...................................

Automatically changing ... to the otherwise hard to type ellipsis symbol … is a good idea, but everything else should, not be changed.

Are we still doing ancient memes?

I can't help but feel overwhelmed by the sheer complexity of self-hosting modern web applications (if you look under the surface!)

Most modern web applications are designed to basically run standalone on a server. Integration into an existing environment a real challenge if not impossible. They often come with their own set of requirements and dependencies that don't easily align with an established infrastructure.

“So you have an already running and fully configured web server? Too bad for you, bind me to port 443 or GTFO. Reverse-proxying by subdomain? Never heard of that. I won’t work. Deal with it. Oh, and your TLS certificates? Screw them, I ship my own!”

Attempting to merge everything together requires meticulous planning, extensive configuration, and often annoying development work and finding workarounds.

Modern web applications, with their elusive promises of flexibility and power, have instead become a source of maddening frustration when not being the only application that is served.

My frustration about this is real. Self-hosting modern web applications is an uphill battle, not only in terms of technology but also when it comes to setting up the hosting environment.

I just want to drop some PHP files into a directory and call it a day. A PHP interpreter and a simple HTTP server – that’s all I want to need for hosting my applications.