In the heart of amazing software development, in the city Brno, we launched a blog to share our thoughts.
When developing a plugin to cloud Jira, a usual need is to communicate with the Jira using REST API. The authentication is done using JWT and We will describe the complete implementation in this blog post.
A security audit of our customer raised the topic of antivirus scanning. So how do we solve it? There are too many options on how to integrate antivirus to the MGS. We also made a fully functional proof of concept using the open source antivirus ClamAV.
Docker images are like onions or orges and it can sometimes be a problem. Especially with VFS storage, where each layer is represented as a full filesystem. We present several ways how to squash multiple image layers to one.
As more and more web applications live on the client computer, it’s harder to update them right when you want. One of the solutions is to change resource file names after every update. Webpack can make this process straightforward.
This blog presents an example case, how an audit trail can be implemented with the MongoDB database. In fact, we implemented exactly this system in one of our older projects CRM.
There are many ways how to make sure the implemented software feature works. But sometimes, you need proof not only for yourself but also for your customer. What if the customer could monitor application functions?
Parsing Unirest response to JsonNode can lead to parsing error on Databricks if the top-level JSON structure is an array. We propose a workaround solution, which works best in custom Java libraries.
Can we use the Databricks as a runtime platform for complex applications using the standard development model with git, deployment pipelines and several independent modules / services?
The software during the development cycle will go through many stages. It usually starts as a source code in IDE, different pars will be executed in unit tests, maybe even whole components will be tested. It’s somehow packaged (compiled) and deployed to some server (staging, production,…). That is a very rough lifecycle which is not applicable in all cases, but at least during my time in CloseIT, many projects followed it.
When I started putting together my first AWS SAM project, I was confused with the project structure - as always, when I’m starting new project with new technology. You can easily make a bloated project where code is duplicated in each lambda function.
Here we go again. The last day of June and you can read interesting topics from the development world that we have read this month.
A few days ago, our first company hackathon finished successfully. But in order to define success, we have to define goals. With every new project, we evaluate what technologies to use.