Nomad Rescheduling Error
While trying to redeploy one of our Nomad jobs last week, I ran into an error that I hadn't seen before.
While trying to redeploy one of our Nomad jobs last week, I ran into an error that I hadn't seen before.
For one of our customer projects, I was looking for an SFTP server. Although my Google search was unsuccessful, ChatGPT offered an interesting suggestion I had never heard of: SFTPGo.
In a recent customer project, I was looking for a way to let a legacy application send emails via Office 365 or more specifically, the MS Graph API.
As part of an AI project, I had to export data to train a tool developed for a customer. Instead of writing a script, I decided to use MySQL's built-in functions, which turned out to be a challenging experience but a valuable learning opportunity.
The growing complexity of IDEs has led me to make a shift in a different direction.
Internally we develop our own tools, that we use as CLI. To make it easier to distribute and use them, we create standalone binaries. But often the files are huge.
So let's see how we can make them smaller without losing any functionality.
In a few projects, we sometimes had the problem, that invalid JSON files were provided by the customer and not checked for errors. To prevent this, we searched for the smallest possible solution.
Recently, we've been running into a weird problem. After restarting 2 nodes in our Nomad cluster, we could not properly access GitLab via SSH anymore. Web access was working fine, also cloning via https:// worked, but not via SSH which is what most of our developers use by default.
From time to time we are in need to access resources on a different server, and if it's only for a short time. The key is here to rely on simple and readily available tools.