Elgato_dark/argo-cd
1
0
Fork 0
mirror of https://github.com/argoproj/argo-cd synced 2026-05-24 09:50:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Update CONTRIBUTING.md (#2494)

Browse source 
* Remove reference to argocd-ui

* Fix deployment scaling instructions

* Mention some additional env vars
This commit is contained in:
jannfis 2019-10-14 17:34:23 +02:00 committed by Alexander Matyushentsev
parent 8e60bdfe59
commit 2c88adc2ed
1 changed files with 21 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
docs/CONTRIBUTING.md
View file

@ -84,11 +84,11 @@ It is much easier to run and debug if you run ArgoCD on your local machine than
You should scale the deployments to zero: You should scale the deployments to zero:
```bash ```bash
kubectl -n argocd scale deployment.extensions/argocd-application-controller --replicas 0 kubectl -n argocd scale deployment/argocd-application-controller --replicas 0
kubectl -n argocd scale deployment.extensions/argocd-dex-server --replicas 0 kubectl -n argocd scale deployment/argocd-dex-server --replicas 0
kubectl -n argocd scale deployment.extensions/argocd-repo-server --replicas 0 kubectl -n argocd scale deployment/argocd-repo-server --replicas 0
kubectl -n argocd scale deployment.extensions/argocd-server --replicas 0 kubectl -n argocd scale deployment/argocd-server --replicas 0
kubectl -n argocd scale deployment.extensions/argocd-redis --replicas 0 kubectl -n argocd scale deployment/argocd-redis --replicas 0
``` ```
Download Yarn dependencies and Compile: Download Yarn dependencies and Compile:
@ -114,6 +114,13 @@ argocd app create guestbook --path guestbook --repo https://github.com/argoproj/
You can open the UI: http://localhost:8080 You can open the UI: http://localhost:8080
As an alternative to using the above command line parameters each time you call `argocd` CLI, you can set the following environment variables:
```bash
export ARGOCD_SERVER=127.0.0.1:8080
export ARGOCD_OPTS="--plaintext --insecure"
```
## Running Local Containers ## Running Local Containers
You may need to run containers locally, so here's how: You may need to run containers locally, so here's how:
@ -130,21 +137,19 @@ Add your username as the environment variable, e.g. to your `~/.bash_profile`:
export IMAGE_NAMESPACE=alexcollinsintuit export IMAGE_NAMESPACE=alexcollinsintuit
``` ```
If you have not built the UI image (see [the UI README](https://github.com/argoproj/argo-cd/blob/master/ui/README.md)), then do the following: If you don't want to use `latest` as the image's tag (the default), you can set it from the environment too:
```bash ```bash
docker pull argoproj/argocd-ui:latest export IMAGE_TAG=yourtag
docker tag argoproj/argocd-ui:latest $IMAGE_NAMESPACE/argocd-ui:latest
docker push $IMAGE_NAMESPACE/argocd-ui:latest
``` ```
Build the images: Build the image:
```bash ```bash
DOCKER_PUSH=true make image DOCKER_PUSH=true make image
``` ```
Update the manifests: Update the manifests (be sure to do that from a shell that has above environment variables set)
```bash ```bash
make manifests make manifests
@ -159,11 +164,11 @@ kubectl -n argocd apply --force -f manifests/install.yaml
Scale your deployments up: Scale your deployments up:
```bash ```bash
kubectl -n argocd scale deployment.extensions/argocd-application-controller --replicas 1 kubectl -n argocd scale deployment/argocd-application-controller --replicas 1
kubectl -n argocd scale deployment.extensions/argocd-dex-server --replicas 1 kubectl -n argocd scale deployment/argocd-dex-server --replicas 1
kubectl -n argocd scale deployment.extensions/argocd-repo-server --replicas 1 kubectl -n argocd scale deployment/argocd-repo-server --replicas 1
kubectl -n argocd scale deployment.extensions/argocd-server --replicas 1 kubectl -n argocd scale deployment/argocd-server --replicas 1
kubectl -n argocd scale deployment.extensions/argocd-redis --replicas 1 kubectl -n argocd scale deployment/argocd-redis --replicas 1
``` ```
Now you can set-up the port-forwarding and open the UI or CLI. Now you can set-up the port-forwarding and open the UI or CLI.