As far as I can see it is still just postman but the request and api definitions are stored in textfiles (and there are multiple projects that do exactly that already).
It seems to me that the blog author is talking about something beyond that.
Sounds great in theory, but without a concerte suggestion on how that might actually work and be implemented it's basically a scifi daydreaming nothingburger. (Or the pitch for the writers upcoming startup)
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.
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)
Njalla's default TTL for DNS records is 3600 seconds (1 hour). If you just created or modified the A record, it can take up to that full hour for the change to propagate across the internet, which would perfectly explain why Certbot is connecting to the right IP but failing to fetch the file (the request might be hitting an old IP or a cached null response).
Before changing any more configurations, you should verify what the rest of the internet is actually seeing for your domain right now.
Check the current DNS record
You can usedig to see exactly what IP your domain is resolving to, and importantly, the remaining TTL on that record.
From your local machine (or any computer), run:
bash
dig yourdomain.com +noall +answer
This will output something like:
text
yourdomain.com. 3412 IN A 203.0.113.45
The second column (3412) is the remaining TTL in seconds. If that number is counting down from 3600, the record is still propagating. If the IP address shown there doesn't match your server's current public IP, the change hasn't taken effect yet for that DNS server.
Check from a different perspective
To ensure it's not just your local ISP or router cache serving an old record, query an external public DNS server directly:
If these external servers show the correct IP but Certbot still fails, the DNS is fine, and the problem is somewhere in your network routing or web server config. If they show a wrong IP or no record at all, you simply need to wait for the TTL to expire.
and it can use locally run models. But have realistic expectations. If you want it to work well, you need a beefy GPU, a lot of RAM and swap. The "intelligence" is kind of limited if you run low spec models, to the point of it maybe being utterly useless.
not sure if it still works, last commit was 3 years ago (on the other hand, there was no AI vibecoding back then, so thats a plus), but it looks like it might do exactly what you're looking for
It says it's for vibecoding but I use it like I would use chatgpt and it gives useable ansers to all of my varied questions. (ofc. you always have to check for correctness, even if it's correct most of the time, which I do cause I'm paranoid)
I guess the only downside is how frigging huge it is.
I do 8 hours of dev, then 2 hours of outdoor rockclimbing and 6 hours of intense competitive video gaming every day and I can still play guitar afterwards.
Go eat some protein and build up some stamina.
(/s ... but is that what you wanted to hear? will you stop reposting now?)
I knew it ...