https://github.com/ejsdotsh/ejsb

e.j.'s system builder
https://github.com/ejsdotsh/ejsb

ansible ansible-project api automation go homelab jsonnet network-automation python

Last synced: 29 days ago
JSON representation

e.j.'s system builder

• Host: GitHub
• URL: https://github.com/ejsdotsh/ejsb
• Owner: ejsdotsh
• Created: 2022-10-31T17:37:42.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2026-04-11T00:15:05.000Z (about 2 months ago)
• Last Synced: 2026-04-11T01:17:45.150Z (about 2 months ago)
• Topics: ansible, ansible-project, api, automation, go, homelab, jsonnet, network-automation, python
• Language: Jinja
• Homepage:
• Size: 384 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          


# ejsb - e.j.'s system builder

[![Build Status](https://img.shields.io/github/actions/workflow/status/ejsdotsh/ejsb/build.yaml?branch=main&logo=github)](https://github.com/ejsdotsh/ejsb/workflows)

[![Latest Release](https://img.shields.io/github/v/release/ejsdotsh/ejsb?logo=github)](https://github.com/ejsdotsh/ejsb/releases)

[![License](https://img.shields.io/github/license/ejsdotsh/ejsb?color=blue)](./LICENSES/MPL-2.0.txt)

[![Contributors](https://img.shields.io/github/contributors/ejsdotsh/ejsb?logo=github)](https://github.com/ejsdotsh/ejsb/graphs/contributors)

> `ejsb` is a grandiose name for a simple command-line tool for ad-hoc management of my personal infrastructure.

## Description

What began as a personal fork of [Ansible-NAS](https://ansible-nas.io/) to replace FreeNAS, became an ad-hoc collection of learning, experimentation, and opinionated tooling that i've written to manage my personal infrastructure. This project is about learning and documenting what i've done to share knowledge.

***...caution, this is a work in progress, breaking changes ahead...***

### ejsb

- a simple command-line tool written in Go, using Cobra, Viper, and Go-Resty

### asb

- [asb](asb): various Ansible playbooks and roles

## Requirements

- Go

- Python

## Acknowledgements

- from Dave Barroso's most-excellent [Building Scalable Tooling](https://www.dravetech.com/presos/building_scalable_tooling/slides.html) presentation (*emphasis mine*):

  > ### Why do we want automation?

  >

  > #### Reliability

  >

  > - Does our software do what we claim it does?

  > - Can we change it without breaking anything?

  > - Test the interactions with the system from a user perspective *first*, then add tests to simulate (fixed) bugs

  >

  > #### Consistency

  >

  > - Avoid cognitive overhead which can lead to bugs, wasted time, and bikeshedding

  > - Adopt frameworks and best practices

  >   - ***Choose a framework and stick by it unless strictly necessary***

  >   - If you need external services, standardize and adopt them across the board (i.e., databases, message buses, etc)

  >   - Adopt a coding style (or an opinionated linter) to minimize arguments about style (i.e., black)

  > - The goal is to be able to collaborate on multiple projects without having to pay a very expensive context switch cost or waste time arguing about tabs vs spaces or MySQL vs postgres

  >

  > #### Maintainability

  >

  > - Readability

  >   - Code is read more often than it is written so optimize for reading

  > - Abstractions

  >   - Break down your code into different layers of abstraction

  >   - Each abstraction should be concerned about solving the problem presented in its layer

  >   - Each abstraction should provide a stable contract so other abstractions can consume it

  >   - Abstractions are good for the separation of concerns

  >     - Given the request of deploying a service, can my software identify which parts need to be configured and which parameters need to be set?

  >     - Given the right input, is my service generating the correct configuration?

  >     - Given some configuration, is my library able to deploy it correctly to the device?

  > - Developer's tooling

  >   - A developer should have tooling to:

  >     - Help write code

  >       - autocompletion, inline documentation, refactoring, etc...

  >     - Inspect and explore what the program is doing during its execution

  >     - Observe how the system behaves in production

  >

  > ### Speed is not a goal but a consequence

- [khuedoan/homelab](https://github.com/khuedoan/homelab)

- [Ansible-NAS](https://ansible-nas.io/)

- [Ansible for DevOps](https://github.com/geerlingguy/ansible-for-devops)

- [DebOps](https://docs.debops.org/en/stable-3.0/)

## License

This project is licensed under the Apache-2.0 and MPL-2.0 Licenses — see the LICENSE files for details.



Made with ❤️ by e.j. sahala