deploying to openshift from two different dev machines

[ralyodio]

So I do grunt build and then cd ./dist && git push to deploy. it works fine, but then when I goto my other dev machine, should I be doing cd ./dist && git pull to get the last deploy?

If I do that, and then run cd ../ && git pull && grunt build again, even though nothing has changed in the source, I still have files to deploy in ./dist for some reason.

I'm a little unclear on how to deploy to openshift from two different machines (assume 2 developers working on code). It seems when developer1 deploys, then developer2 has to deploy again the same code.

[marani]

Right, I have the same issue. In fact, same thing happens in my original local repo as well, not just the cloned repo (after first ever deploy, cd ../ && grunt build && cd ./dist && git status, everything turns red, no code changed).
With the current method, git deployment on openshift is more like simple ftp deployment rather than version control.

[ralyodio]

I think its better to just do a hard reset on the open shift repo, and then rebuild and push. My guess is the unique id for the .script.js and the .css files is randomly generated, so it will never be the same.

[marani]

It seems that's the only way now. In that way, different developers have to ensure themselves the openshift repo is exactly the build output of the latest source repo (that I guess you have somewhere else), rather than relying on version control features of git. It would be perfect if we can use openshift as source repo, grunt build on it, then point the node startup script at dist's server.js, but that might require huge changes in folder structure and so it might not work on heroku, and I'm not sure how to do that also :D.

After all, I haven't tried to push from the cloned repo, because I saw another issue. That is the dist/views/index.html file of the cloned repo, it doesn't link to the minified vendor.js, (ok for the main scripts.js). Do you have the issue as well?

[ralyodio]

I think its fine. the open shift repo should never be pulled from, just do a cd ./dist && git reset --hard before you build the app. That way you always have whatever is on production before you build.

i would always assume git pull before any build in top level app repo.

edit: I have not seen this issue you're talking about with ./dist/views/index.html. Did you run grunt build?

[JaKXz]

To answer the original question: no, you do not need to re-deploy the same code. Deployment requires a level of communication (i.e. tags) where the deployment has occurred.