# Installation

#### New! Config Builder <a href="#new-config-builder" id="new-config-builder"></a>

Customize the local deployment according to your needs:

{% hint style="warning" %}
Make sure to have Docker 27 or up. If you get an error about docker compose command not recognized, it's because your Docker version is old and not supported.
{% endhint %}

### Docker compose <a href="#docker-compose" id="docker-compose"></a>

* clone the repo:

`git clone https://github.com/intuitem/ciso-assistant-community.git`

* run the preparation script and follow the instructions:

`./docker-compose.sh`

you can also find other variants for different setups as a starting point for your specific needs.

[Remote/Virtualization](https://intuitem.gitbook.io/ciso-assistant/deployment/remote-virtualization)

[Deploy on a VPS](https://intuitem.gitbook.io/ciso-assistant/deployment/deploy-on-a-vps)

### Helm chart <a href="#helm-chart" id="helm-chart"></a>

Make sure to have Helm binary installed and switch to your cluster context.

1. add the helm repository

`helm repo add intuitem https://intuitem.github.io/ca-helm-chart/`

1. get the default values

`helm show values intuitem/ciso-assistant > my-values.yaml`

1. check and adjust them to your needs, specifically the `frontendOrigin` parameter
2. create a namesapce for your deployment

`kubectl create ns ciso-assistant`

1. install

`helm install my-octopus intuitem/ciso-assistant -f my-values.yaml -n ciso-assistant`

{% hint style="info" %}
This setup is based on the fact that Caddy will handle the TLS on your behalf. In case you're experiencing ssl related issues, you might want to patch your ingress-nginx-controller to activate the `enable-ssl-passthrough` flag.
{% endhint %}