Live data from Hacker News

We built an air-gapped Jira alternative for regulated industries

plane.so

171–180 of 201 posts

Re: We built an air-gapped Jira alternative for regulated industries

#171

Earlier quoted context omitted.

If they also realize that having less dependencies makes deployment easier we have gone full circle.

I can't believe how many devs think dependancies are completely cost free...

I don’t get it, the dependencies are either needed or not. If needed that are either pulled from a project or written. So how are dependencies evil , is the rage against feature bloat pulling in dependencies ? Then the issue is the bloat

Re: We built an air-gapped Jira alternative for regulated industries

#172
post #121

I just learned air-gapped includes private networks. I was under the impression this strictly meant isolated non-networked computers. Was this always the case or has the term diluted over time?

Strictly speaking, air-gapped originally meant physically isolated, no network connections at all. But in practice, the definition has broadened a bit, especially in enterprise and defense settings. Today, it may include closed private networks with no internet access, still isolated, but with internal connectivity for practical reasons (like backups, logging, or internal auth).

Pfft! Truly air-gapped would be each key on the keyboard physically unconnected to anything else. True security.

Re: We built an air-gapped Jira alternative for regulated industries

#173
Running software in an airgapped environment is difficult, but the hardest thing is the install, packaging and shipping updates. I have used https://zarf.dev/ to do this for a government client, and it was an amazing experience. I highly recommend it. K8s seems heavy, but if you want to run datastores with backups (k8s operators), or highly customised environments, and automate all of that, instead of loads of bash and custom code, it shines.

Re: We built an air-gapped Jira alternative for regulated industries

#174

Earlier quoted context omitted.

If they also realize that having less dependencies makes deployment easier we have gone full circle.

instead of CI/CD pipelines and a million dependances, why don't we just put all of the containers, like, on one single VM? and just make it a linux box or whatever? (presumably read in Adam Something's voice)

The usual way to deploy such things is actually to create 1 VM for that application, install podman, and then run all those tons of containers in that VM. Because you cannot trust software vendors to not do or require stupid shit like requiring the docker socket, mounting overly broad volumes from the hosts filesystem, provide working and non-stupid compose/helm/...-files and things like that. Often the support contract also requires a specific version of a specific OS, a specific kubernetes distro or something like puppet/chef/... for deployment. Since for the multitude of software vendors and requirements, we couldn't easily fulfill all those at the same time on the same kubernetes cluster or infra, we just split it up into VMs.

Re: We built an air-gapped Jira alternative for regulated industries

#176
post #121

I just learned air-gapped includes private networks. I was under the impression this strictly meant isolated non-networked computers. Was this always the case or has the term diluted over time?

I work on an air-gapped network. The most important thing that the words "air gap" communicate is that there is no connection, nothing at all, to anything outside the network. The only way to move anything on or off are using disc drives (no USB for security reasons). The word "private network" does not really communicate that there is a physical gap of no wires at all from the computers on the network and everything else on the internet.

Re: We built an air-gapped Jira alternative for regulated industries

#177

Earlier quoted context omitted.

I can't believe how many devs think dependancies are completely cost free...

I don’t get it, the dependencies are either needed or not. If needed that are either pulled from a project or written. So how are dependencies evil , is the rage against feature bloat pulling in dependencies ? Then the issue is the bloat

Functionality is either needed or it isn't, but it doesn't need to come from an external dependency. When it does, it probably comes with functionality you didn't need too. And as soon as you have a compile/runtime dependency on external code, your compile/execution environment needs to always have access to third party code. So that's bloat and complexity. You also give up control. Hopefully it ends up saving a bunch of time over developing it internally.

Re: We built an air-gapped Jira alternative for regulated industries

#178

Earlier quoted context omitted.

I don’t get it, the dependencies are either needed or not. If needed that are either pulled from a project or written. So how are dependencies evil , is the rage against feature bloat pulling in dependencies ? Then the issue is the bloat

Functionality is either needed or it isn't, but it doesn't need to come from an external dependency. When it does, it probably comes with functionality you didn't need too. And as soon as you have a compile/runtime dependency on external code, your compile/execution environment needs to always have access to third party code. So that's bloat and complexity. You also give up control. Hopefully it ends up saving a bunc…

Hopefully an upgrade to an external library doesn't end up including another dependancy that happens to include some backdoor that steals all the credit card information in your database. Or a crypto miner in frontend code. Or introduces a bug that stops people from being able to checkout. Or the money package starts calculating slightly differently than your payments provider... Etc. etc.

Re: We built an air-gapped Jira alternative for regulated industries

#179
post #169
post #63

Earlier quoted context omitted.

What a weird time to enforce British rules for acronyms. JIRA stands for JIRA Isn't Really Awesome.

But what does the “JIRA” in “JIRA Isn’t Really Awesome” stand for?

Same thing as the “GNU” in “GNU’s Not Unix” — it’s a recursive acronym

Re: We built an air-gapped Jira alternative for regulated industries

#180

Earlier quoted context omitted.

I can't believe how many devs think dependancies are completely cost free...

I don’t get it, the dependencies are either needed or not. If needed that are either pulled from a project or written. So how are dependencies evil , is the rage against feature bloat pulling in dependencies ? Then the issue is the bloat

> I don’t get it, the dependencies are either needed or not.

Some developers' judgement about needed dependencies can be suspect though: https://news.ycombinator.com/item?id=29241943

Post reply on HN