You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This step is optional but will avoid interference with the local InCluster kubero-ui instance.
39
37
```bash
40
38
kubectl create namespace kubero-dev
41
39
```
42
40
43
-
### Configure Kubero's environment
41
+
### 4) Prepare your local code
42
+
Fork the repository https://github.com/kubero-dev/kubero into your account.
43
+
44
+
Clone your Fork to your local disk.
45
+
46
+
### 5) Configure Kubero's environment
44
47
```bash
45
48
mv .env.template .env
46
49
```
47
50
48
-
### Start local node server
51
+
### 6) Start local node server
52
+
This will start the server part.
49
53
```bash
50
54
cd server
51
55
yarn install
52
56
yarn dev
53
57
```
54
58
59
+
Initiate the client JS part.
55
60
```bash
56
61
cd client
57
62
yarn install
58
63
yarn watch
59
64
```
60
65
61
-
### start optional services
66
+
You should be able to reach your local dev instance via http://localhost:2000
67
+
68
+
### 7) start optional services
62
69
If you need any additional services (Gitea, Github ...), just run `docker-compose up -d`, or add it to the `docker-compose.yml` file, if it is missing.
63
70
64
71
Nope. No extra database is required. All data is stored in the Kubernetes cluster.
0 commit comments