mirror of
https://github.com/IT4Change/Ocelot-Social.git
synced 2025-12-13 07:45:56 +00:00
7c6d5b5129
Ok, so here is the plan. Let's give both our cucumber features and your cypress tests a prominent place to live. That would be the root level folder of our application. Second, let's revive formerly dead code step by step. Ie. move code from the former location `backend/features/` to `features/` when it is ready. All edge cases should be tested with unit tests in `backend/`, see my `webfinger.spec.js` as an example.
26 lines
893 B
Markdown
26 lines
893 B
Markdown
# Minikube
|
|
|
|
There are many Kubernetes providers, but if you're just getting started, Minikube is a tool that you can use to get your feet wet.
|
|
|
|
After you [installed Minikube](https://kubernetes.io/docs/tasks/tools/install-minikube/)
|
|
open your minikube dashboard:
|
|
|
|
```text
|
|
$ minikube dashboard
|
|
```
|
|
|
|
This will give you an overview. Some of the steps below need some timing to make resources available to other dependent deployments. Keeping an eye on the dashboard is a great way to check that.
|
|
|
|
Follow the installation instruction for [Human Connection](../human-connection/README.md).
|
|
If all the pods and services have settled and everything looks green in your
|
|
minikube dashboard, expose the services you want on your host system.
|
|
|
|
For example:
|
|
|
|
```text
|
|
$ minikube service nitro-web --namespace=human-connection
|
|
# optionally
|
|
$ minikube service nitro-backend --namespace=human-connection
|
|
```
|
|
|