In conclusion, the manifest contains a variety of settings and options too numerous to mention in this introductory text. Suggested further reading in the reference about the Nelson manifest answers the following common queries:
- How do I declare a dependency on another unit?
- How do I get alerted when my unit has a problem at runtime?
- How do I expose my service to the outside world?
Now that you have your
.nelson.yml as you want it, add the file to the root of your source repository, and commit it to the
master branch. Nelson will look at the repositories’
master branch when it first attempts to validate your repository is something that is Nelson-compatible. You can check the validity of your manifest definition at anytime without checking in by using the Nelson CLI:
nelson lint manifest.
Outside of this website there are also several blog posts and talks on Nelson, from design principles to implementation to the system as a whole.
- Nelson integrates Kubernetes - Timothy Perrett, December 2017
- Envoy with Nomad and Consul - Timothy Perrett, May 2017
- Nelson: Functional programming in system design - Adelbert Chang, Scale by the Bay 2018 - slides - more systems/workflow focused
- Nelson: Functional programming in system design - Adelbert Chang, Northeast Scala Symposium 2018 - slides - more implementation focused
- Persistent Data Structures in System Design - Adelbert Chang, East Bay Haskell Meetup January 2018 - slides
- Online Experimentation with Converged, Immutable Infrastructure - Timothy Perrett, HashiConf 2017 - slides
- Nelson: Rigorous Deployment for a Functional World - Timothy Perrett, Scale by the Bay 2017 - slides
- Large Scale Infrastructure Automation at Verizon - Timothy Perrett, HashiConf 2016 - slides
- Nelson: Multiregional container orchestration for Hashicorp Nomad and Lyft Envoy - Timothy Perrett, San Francisco Infrastructure as Code Meetup June 2017 - slides