# Primero - CPIMS Deployment Issue

**URL:** <https://support.primero.org/forum/t/primero-cpims-deployment-issue/875>\
**Category:** CPIMS\
**Tags:** pakistan, v2-0\
**Created:** [October 28, 2024, 8:30am UTC](https://support.primero.org/forum/t/primero-cpims-deployment-issue/875 "2024-10-28T08:30:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ian\_brasil](https://support.primero.org/forum/user_avatar/support.primero.org/ian_brasil/32/8_2.png) [@ian\_brasil](https://support.primero.org/forum/u/ian_brasil)\
**Post date:** [October 28, 2024, 9:15am UTC](https://support.primero.org/forum/t/primero-cpims-deployment-issue/875/2 "2024-10-28T09:15:35Z")

</div>

If you are using ansible to deploy you need to make sure that always\_pull is commented out in your inventory file for the changes to be reflected.see more here

> [@Help Required Hosting V2 to Linode](https://support.primero.org/forum/t/help-required-hosting-v2-to-linode/483/2):
>
> So the variables are as follows: primero\_host is where your server will be running like [your.site.com](http://your.site.com) primero\_repo is your fork primero\_repo\_branch is the git branch you will be deploying (your changes) build\_docker\_tag is the docker tag you want to deploy (I think you can leave this as ‘’ for now) build\_docker\_container\_registry is the docker registry (I think you can leave this as ‘’ for now) primero\_configuration\_path along with primero\_configuration\_repo and primero\_configuration\_repo\_…

---

_[View the full topic](https://support.primero.org/forum/t/primero-cpims-deployment-issue/875)._
