Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature/OIDC #14

Merged
merged 18 commits into from
Apr 23, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
148 changes: 109 additions & 39 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

77 changes: 77 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
# Vicky

Vicky, which is the babysitter of Timmy, Cosmo and Wanda, is a CD tool for environments with many constraints and dependencies that usually cannot be represented.


## Components

Vicky consists out of multiple components to make a spreaded deployment possible.

+ vicky
+ Main Task Scheduler
+ vicky-worker
+ Task Worker, can run multiple times.
+ dashboard
+ Web-UI
+ vicky-cli
+ CLI

Each component can be developed and deployed individually.

## Concepts

We use an etcd cluster to sync state between multiple instances of Vicky. Vicky will do leader election, so at each time only one instance is active. We try to make Vicky as resilient to network and other failues as possible but it is not our main goal, yet.
All data in the etcd is stored under `vicky.wobcom.de/` in YAML format.

## Development Setup

We need to start at least a `vicky` instance, S3 storage and etcd to run anything.

### Storage & Database & Certificates

#### docker-compose

+ Generate TLS client certificates for etcd authentication
+ `nix run .\#generate-certs`
+ Certificates are located at `certs`
+ Enter `deployment`
+ Start docker-compose collection
+ `docker-compose up -d`

#### devenv

TODO @yu-re-ka: Add Information

### Vicky

+ Copy `vicky/Rocket.example.toml` to `vicky/Rocket.toml`
+ `Rocket.example.toml` contains the correct configuration to run with the provided development environment.
+ Edit `vicky/Rocket.toml`
+ Add own machine token to configuration
+ This is needed for `vicky-worker` later.
+ Add OIDC authentication provider to configuration
+ Enter `vicky`
+ Run `cargo run --bin vicky`


### Vicky Worker

+ Copy `vicky-worker/Rocket.example.toml` to `vicky-worker/Rocket.toml`
+ Edit `vicky-worker/Rocket.toml`
+ Add `machine_token` from last step into this configuration.
+ Enter `vicky-worker`
+ Run `cargo run --bin vicky-worker`

### Dashboard

+ Enter `dashboard`
+ Install Dependencies
+ `npm ci` in `dashboard` Folder
+ Run `npm run start`

### CLI

TODO: Add Content for CLI configuration and development.



Loading
Loading