# if your service is going to run behind nginx or any other proxy then update, proxy-path variable too in deployment.yaml, by-default it is blank.
# Example to manually create needed secrets for deployment params totally aligned with [Usage Params](https://github.com/dutchcoders/transfer.sh#usage-1)
If your service is going to run behind nginx or any other proxy in your kubernetes cluster then passing on `proxy-path` variable becomes a must to avoid to avoid errors by webend, by-default it is blank.
dont add prefix '/' for the path.
Ex: if your kubernetes ingress piece of routing yaml is like this
```yaml
...
spec:
rules:
- host: api.myhost.mysite.com
http:
paths:
- backend:
serviceName: transfersh
servicePort: 80
path: /filemanager
...
```
=> PROXY_PATH arg must be set to 'filemanager' & not /filemanager.