armand1m / armand1m/microservices
feature: Environment Rancher Catalog
- Dominant language
- No language data
- Stars
- 16
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
# Proposal
Enable the microservices project to run under Rancher using a Catalog Repository.
It is a cool feature because it allows deploy to all the services under a cluster using Cattle, the default orchestrator of Rancher.
Also, it enables an easier way to deploy all services in one click, on any environment.
## Features
Here lays the features that would be nice for the Catalog to enable:
- Environment Catalog
- [ ] Be able to receive a list of git repository to use as the services.
- [ ] Be able to extend every git repository root `docker-compose.yml` service definition automatically, and its dependencies.
- [ ] Be able to receive the services definitions and its dependencies.
- [ ] Be able to use a git repository, clone it, and simply run its `docker-compose.yml` file
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the root docker-compose.yml files and the Rancher Catalog Repository requirements described in the proposal. Define how a catalog would receive service Git repositories or service definitions, resolve dependencies, and run the resulting compose configuration. Done means the listed catalog deployment scenarios are supported and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, git
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100