https://github.com/chriskalmar/entourage

Environment bootstrapping for integration tests
https://github.com/chriskalmar/entourage

Last synced: 2 months ago
JSON representation

Environment bootstrapping for integration tests

• Host: GitHub
• URL: https://github.com/chriskalmar/entourage
• Owner: chriskalmar
• License: mit
• Created: 2019-11-13T14:30:02.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2024-10-21T09:21:49.000Z (2 months ago)
• Last Synced: 2024-10-21T13:19:42.010Z (2 months ago)
• Language: JavaScript
• Homepage: https://chriskalmar.github.io/entourage/
• Size: 1.66 MB
• Stars: 3
• Watchers: 3
• Forks: 1
• Open Issues: 28
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        


# Entourage ![CI](https://github.com/chriskalmar/entourage/workflows/CI/badge.svg)

Environment bootstrapping for integration tests

## Architecture

This project has 2 components that work together, a server and a client component.

Typically one server runs to manage multiple projects and respective versions of each project. Each CI pipeline uses then the client to init/access/destroy a profile on the server.

The server needs to run as a privileged docker container.  

Check package details page of [entourage-server](https://github.com/chriskalmar/entourage/tree/master/packages/entourage-server) for more details.

The client configuration is part of the repo that runs the integration tests later.  

Check package details page of [entourage-cli](https://github.com/chriskalmar/entourage/tree/master/packages/entourage-cli) for more details.

## TODOs

- [ ] provide functionality to run health checks

- [ ] implement container clean-up process (garbage collection)

- [ ] lock versions

- [ ] protect HTTP / WS / MQTT access with authentification

- [ ] persist server registry in redis ?