Localhost:3000 Version Displayed Differently from Heroku Deployed Version - Node.js

Question

I've deployed my directory to Heroku using git push heroku master, but nothing happens.... Everything up-to-date is what the screen reads.

How can I push to Heroku the exact version that I am running locally, since the local version does the things I want?

Do you have still files to commit on your local? What is the result of `git status`? — L. Meyer, Sep 07 '18 at 07:37
Which branch are you on? ```git status``` first output line shows you the result. — Seyed Ali Akhavani, Sep 13 '18 at 05:41
Make sure your browser cache isn't stale. Assuming that has anything to do with the issue. — Patrick Roberts, Sep 14 '18 at 03:33
But how does it differ exactly? Is the css different? Or is it couple-of-commits-back different? — Tomasz Bubała, Sep 14 '18 at 07:13
@TomaszBubała there is different code in a couple places. I cleared cache etc. — maudulus, Sep 14 '18 at 17:32
@maudulus have you pushed correct branch to heroku? maybe locally you're on a different branch? — Tomasz Bubała, Sep 17 '18 at 05:55
@maudulus I wonder if you did actually build for production your app before commiting and pushing to Heroku, or you just are executing with "npm start"? Did you look in Heroku master branch which is the last commit and if it's the same that are in local? — BrunoLoops, Sep 17 '18 at 16:50
@TomaszBubała the version on my computer is different. There is functionality that works on the local version that doesn't work on the website, mainly a small, front-end feature. — maudulus, Sep 19 '18 at 15:23
@maudulus [re-releasing](https://stackoverflow.com/a/43773755/8247278) the most recently deployed code didn't have any effect? — Amir Masud Zare Bidaki, Sep 19 '18 at 16:31

score 3 · Answer 1 · answered Sep 19 '18 at 08:33

3

If you are sure that the source codes itself are not the same in these two branches, you can use force push:

# Make sure you are on your local master branch
git branch
# Make sure that your remote address is correctly set
git remote -v
# Then force push your master branch to heroku remote master branch
git push heroku master -f

force pushing a branch to a remote will force the remote branch to take on the branch’s code and git commit history

But if you don't have access to check the source code, check if Environment Variables are the same on local machine and server or not (e.g. NODE_ENV variable)

Moreover, Double check automatic deployment of heroku (if exists) as well as the node and npm version of both machines and be aware of the command you run on both machines (npm start or node . or ...) that may have different operations based on envs or so.

answered Sep 19 '18 at 08:33

Amir Masud Zare Bidaki

931
11
21

When I do this I get the `Everything up-to-date` message and it doesn't push anything. However, it is still different on the web vs localhost. I've cleared caches etc. – maudulus Sep 19 '18 at 15:20
One thing I was wondering is whether there is a way to re-push to Heroku: https://stackoverflow.com/questions/41345744/redeploy-heroku-app-without-code-changes – maudulus Sep 19 '18 at 15:30
Are you sure that the source codes of remote branch and local branch are still different? Or only the functionality of server is not the same? – Amir Masud Zare Bidaki Sep 19 '18 at 15:31
have you tried purging cache of heroku with https://devcenter.heroku.com/articles/git#build-cache -> https://github.com/heroku/heroku-repo#purge-cache ? – Amir Masud Zare Bidaki Sep 19 '18 at 15:32
It's a good idea to clone the remote branch via [heroku cli plugin](https://github.com/heroku/heroku-repo#clone) and investigate for possible differences with local one with `diff -qr dir1/ dir2/` – Amir Masud Zare Bidaki Sep 19 '18 at 15:43
@maudulus have you tried to clone the repo from git and then run it locally? (or removing node_modules dir and rerunning npm install) maybe you are using some dependencies that is not saved in `package.json` and it caused this difference :thinking: – Amir Masud Zare Bidaki Sep 19 '18 at 16:00

Vikash Dhiman · Answer 2 · 2018-09-20T11:19:42.120

2

Please check the branch or remote url of heroku.

In heroku click Deploy tab and find out the branch. Add the remote url in your local machine terminal.

1) heroku git:remote -a projectname
2) git status
3) git add .
4) git commit -m "message"
5) git push heroku master

edited Sep 20 '18 at 11:19

answered Sep 18 '18 at 20:35

Vikash Dhiman

570
5
16

isp-zax · Answer 3 · 2018-09-14T04:50:39.723

Since you are not doing anything obviously wrong, something is wrong. It is hard to say what it is exactly, without additional investigation.

I suggest that you clone your project from heroku into a new directory, then copy your local changes from your local branch (which as you said works on 3000 port) into this fresh directory and push all those changes as usual:

git add -A
git commit -m "some message"
git push

It is also a good idea to diff fresh clone with your currently working directory. If tracked files are identical, that would suggest difference between local environment and heroku container configuration.

Martin Zeitler · Answer 4 · 2018-09-19T16:22:56.437

first run git add -A to stage all changes, including deletions.

or run git add . to stage all changes, without the deletions.

then git push heroku master will push those staged changes to master and remote heroku.

this is because, while no changes were staged, there is nothing to push (both branches identical).

using a visual front-end might help to make it easier to handle. and maybe consider to setup a local staging environment (where the term staging has a different meaning, than it has within the context of git), in order to test properly, before pushing files to the live environment.

Localhost:3000 Version Displayed Differently from Heroku Deployed Version - Node.js

4 Answers4