---
# System prepended metadata

title: 'Holoport management, Envoy, Nixify happs'

---

Holoport management, Envoy, Nixify happs
====

This document captures notes from a discussion about holo init and other functions for managing holoport


* nixos to manage initial state/guarantee unique id (a future need)
* using nixos for controlling state?


## Holonix not a direct fit for envoy 
* Holonix does not have facilities to build envoy. So we would create nix expressions for envoy
* We will still cooordinate/sync up pinned dependencies and document that with integration team
* Nix community does not have good tools for nodejs, so we 

build/test/release envoy with nix
===

* use nix expression to package upstream
* use nix-shell for specific application development (solely sets up env vars.can set up system dependencies that are in service of env vars)
* nix-build builds not just environment but also the entire derivation (builds an entire package on any target supporte dby nix.)
* use nixos as env where you need services (rebuild switch) to compose an entire OS with services
* Nixops (can configure servers and infrastructure much like ansible/puppet/chef, but using nix expressions, terraform for infrastructure/networking)

We can create a derivation for typescript compile

Yegor will create an npm-to-nix similar to https://gitlab.com/transumption/unstable/cargo-to-nix/blob/master/default.nix for the deps for envoy


