I have an alcatel lucent switch from the 90s

It’s been running 24/7 for 25 years in some companys rack and now it runs for 10 in mine.

Got it for 30$ on ebay (and a second one for 20 as a backup)

https://github.com/LinSoftWin/Photoshop-CC2022-Linux

works perfectly for me

Thanks for your effort!

Pros: it’s Linux :D

Cons: it’s Linux ;(

I recently read this super interesting and in depth blogpost about this topic:

https://nocoffei.com/?p=451

Gaben is great!

But I was thinking of the founder of Blue Systems https://en.wikipedia.org/wiki/Blue_Systems

I agree, but I’m still glad some rich people are spending tons of money to make some free and very useful apps for me.

Ideally they should be doing it like the millionaire that partially funds KDE though.

I’m using soquartz compute modules on soquartz blades, because of the nvme slot and PoE. Just one cable for each is so nice in a tiny rack. They are running dietpi and docker swarm with dokploy.

I generally recommend the pine64 stuff, but shipping and tax might be high depending on where you live :/

Somehow both your screenshots are cut off where the red circle is.

But usually if it’s not in the settings, you have to open an issue at bugs.kde.org

https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-what.html

Mine sits at about 50-60W

same but it doesn’t change with load, whether it’s idle or maxed out, it’s in that watt range

I’ve been running it for 2 years.

The swarm support integration is first class, but there is not much to do in the gui, you can add nodes and see basic info about them and thats it basically.

Most of the stuff happens in the compose files where you can define how many copies of a container you run and what nodes you want to restrict them to. etc.

I’m not sure about the moving features tbh. It should move them automatically when a node is down. In my setup I don’t use that at all, all my containers are pinned to specific nodes by feature flags (one node has lots of hdd storage, another has more ram, another has a gpu).

You can see the container logs, but you have to select “swarm” in a dropdown when the container is not on your master node.

And also when deploying a new app you have to select “Compose” and then in a further dropdown “Swarm”.

deleted by creator

I’m running dokploy in swarm mode on 3 nodes.

The only downside is the development of swarm is basically halted and some features are missing (like passing /dev devices to a container, you have to use dirty workarounds) but otherwise it just works.

Should have used agpl if they wanted to be noble.

But this is just a corpo moating strategy.

Mostly the uutils.

• MIT license isn’t nice.
• They have way more CVEs than the core utils they replace.
• They don’t have feature parity yet, so if you use some rare flags in your scripts, those will break.

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

4:25

(sorry my third party youtube frontend can’t share timestamp links)

tldw:

• more CVEs than the old core utils that have been tested and in prod for over 30years
• no feature parity, so existing stuff that uses them will suddenly misbehave, when certain flags are missing
• different license, MIT instead of copyleft, so it’s more friendly for companies to use it for profit, while abusing the work of volunteer contributors

Also netcup has really good deals during the winter holidays

The problem could be anywhere in between the internet and your server.

Ofc. it could be your routet. But I think the following is more likely:

It might also be your internet service provider that doesn’t allow those ports for inbound connections.

Or you’re behind a CGNAT so your real external ip is different from the one you think it is. (look up online how to test this)

Sounds good.

Hmm next you probably should confirm ports 80 and 443 are actually reachable from the internet.

Use an online port checker like https://canyouseeme.org/

After that you should check your apache config like somebody else already suggested. I haven’t used apache in a while but if I remember correctly:

Ensure it says: Listen 80 NOT: Listen 127.0.0.1:80

(and same with 443)

Also check your VirtualHost — it should look something like:

<VirtualHost *:80>
    ServerName yourdomain.com
    DocumentRoot /var/www/wordpress
    # ... other settings
</VirtualHost>

(and same with 443)