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".
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.
keyboard.io has it on their model 001 and model 100
one thing about their implementation that was super convenient is jumping to quadrants. I can't really explain it well, sorry. Maybe you can find a video
Depending on where you live, going to IT events and conferences to connect to people in person is even more powerful. Ask them about their work and talk passionately about related stuff that you have some knowledge/skill in. Exchange contacts, say you're looking for work.
For example, next month is DEVWORLD in amsterdam. They always give away free tickets close to the start of the event. I'm sure there are a ton more like this around the world.
As for writing applications:
For me writing very high quality applications did the trick.
only apply to companies/positions that you are REALLY interested in
research the position
research the company
if you can find somebody that works there in a similar position, ask them some questions
use the info you gathered to show interest in your appplication
write everything yourself, no AI writing. Be a genuine human.
But you can use AI to give it the position and your application and tell it to make a hiring decision with pro/con arguments and rework it based on that
make a small demo project that shows off your relevant skills and tell them about the challanges you had and what you learned to overcome them
(About the last point: I found that talking about relevant hobby projects I did and showing the code made a huge difference)
It usually takes me about a week to write one such application. But I only sent out 3 before hearing back from 2 of the companies and getting signed on by one.
I know it's a lot more hoops then just clicking "auto apply" or "apply with AI", but the effort pays off.
Contrary to that I often see people complaining online about how they wrote 100 applications in a month and got no job interviews... yeah buddy. (And I was initially one of those people)
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".