# Deployment

## Remotely

### All services

```sh
make deploy i=inventories/my-customer
```

### MediaWorker

```sh
make deploy i=inventories/my-customer l=worker
```

### Monitor

```sh
make deploy i=inventories/my-customer l=monitor
```

### MirisManager

```sh
make deploy i=inventories/my-customer l=manager
```

### MediaServer

```sh
make deploy i=inventories/my-customer l=server
```

### MediaImport

```sh
make deploy i=inventories/my-customer l=import
```

### MediaVault

```sh
make deploy i=inventories/my-customer l=vault
```

### Celerity

```sh
make deploy i=inventories/my-customer l=celerity
```

### Wowza

```sh
make deploy i=inventories/my-customer l=wowza
```

### Postgres

```sh
make deploy i=inventories/my-customer l=postgres
```

### Netcapture

```sh
make deploy i=inventories/my-customer l=netcapture
```

## Locally

Instead of deploying all host remotely through SSH, you can also clone the envsetup repository on the server as `root` in `~/envsetup`, then enter in the directory, configure the activation or system key and run one of those commands:

```sh
make deploy i=inventories/local-server
make deploy i=inventories/local-worker
make deploy i=inventories/local-vault
```

## Known issues

- Proxy

If output trafic on the remote hosts is allowed only through a proxy, the deployment will fail.
It won't be able to locally clone repositry and get host configuration file from mirismanager.ubicast.eu.

For "remote" deployment you have to set the proxy settings in the inventory variables, in `inventories/my-customer/group_vars/all.yml`:

```yaml
---

[...]

proxy_http: http://proxy.my-customer.net:3128
proxy_https: http://proxy.my-customer.net:3128
```

For "local" deployment you have to manually set the proxy settings in the `/etc/environment` file:

```
PROXY_HTTP="http://proxy.my-customer.net:3128"
PROXY_HTTPS="http://proxy.my-customer.net:3128"
NO_PROXY="localhost,127.0.0.1,::1,mymediaserver.my-customer.net"
```