I have a sever on heroku. I'm making changes on my project (for ex. adding something inside my JSON file). I'm pushing my changes on heroku/master branch like this:
git add .
git commit -am "changes in json file"
git push heroku master
I'm getting "Everything up-to-date". When I'm reloading the server the changes that I made don't appear, it makes sense because if I'm trying to push to my heroku master brench I'm gerring "Everything up-to-date" but I'm expecting to show me the changes and to restart the server automatically.
Can you help me?
For any additional informations please ask me!
It works!
I don't know what I did to solve the problem, it solved after I made a new project following this tutorial: https://www.youtube.com/watch?v=P86N9FqNqso&list=LL69VX7JLGdfJjh-p8M1RzVw&index=2&t=0s
It might be possible due to the fact that I wasn't in the right folder, I didn't check the folder I was in, I'm not saying that that was my problem but I consider it a possibility.
It works now, thanks for helping and if you have the same problem I can suggest to you rechecking if you are in the right folder, your project folder, or check the tutorial I linked above.
Related
well I have a problem with heroku (PasS), I am launching my first project with Laravel and I'm currently making constant changes,
I understand that every change I make in development I have to use git and push heroku to send to production and also to see the changes in vue.js I have to execute a command in heroku bash, now my problem is because the changes I currently make it no longer works it is not seen in production, constantly made many commits it will be for that or for the cache I do not know the truth I hope a response please.
Sorry I do not understand you well or maybe it is because of my lack of ignorance since it is my first project that I launch to heroku, However I will detail my problem currently I have two branches: master and production, currently I always work with the master branch and also that's where I push the changes to heroku
Here I show you a message from the list of my commits in the master branch:
in conclusion :
I have created a component in vue.js and when I deployed the application to heroku, that component is not shown and as I said in heroku bash it executed "npm run dev" to show the changes in the front-end, previously it showed the changes it made but over time I stop working
And as I say I think it is for making many commits
I want to use the git-branch npm module to detect my branch in the code, but Heroku doesn't show the .git folder, so git-branch displays an error.
Is there a way to make that I can access that file?
If not, can I use a workaround, like copying the file and then restoring it, or stuff like that?
I'm auto-deploying from GitHub a Node.js app.
No, there is no way. Heroku will not send the .git folder to the build.
Even if that folder were kept, you would always see the master branch though, as it's always what you push to.
However, you can still retrieve the pushed GIT commit (not the branch) using the dyno metadata feature, which will set environment variables with various informations about your app. HEROKU_SLUG_COMMIT will be the commit you deployed.
another little issue with my current choice of IDE , Bluej. I have set it up to be able to share a project (namely to commit and push changes) using GIT,and specifically through a gitlab repository.
After the first couple of successful pushes and commits(two weeks ago), I changed some code today, tried to do exactly the same procedure, and alas, the button OK in bluej to actually push the changes, is not active!
I have checked connection by entering password, all looks fine. Also, commits are happening fine locally, but when I try to push them through the TeamWorks of Bluej, the OK button remains inactive.
ps: a restart of the program did not solve the issue.
In that case:
switch to the command-line,
go to your repository folder,
and do a git fetch + git status
That should show you why a simple git push is not possible (possibly because you need to pull first)
I am new to the world of grunt but I feel like there must be a way to do this. Hopefully I can explain my issue in a way that makes sense so you can be of assistance.
Essentially, I have a git project, including a gruntfile, that I use to start all new websites. I clone the project, delete the .git folder and setup a new project in bitbucket for it. Over time I have had to make some modifications to the gruntfile and it is annoying to go back to an old project where I hadn't made those modifications. Is there a recommended way to ensure that my template is up to date on all of my projects?
Things to note:
1) I am familiar with grunt scaffolding but I have never used it, is this the use case for it?
2) my projects live in bitbucket and are private. My initial solution to this problem was to use grunt curl and pull the latest and overwrite the previous gruntfile
3) The issue with #2 is that I would need to put my username/password in the path and can't figure out how to prompt the user, even if I do and they enter the login incorrectly bitbucket still returns something (a bad login page) and this would overwrite my gruntfile.
Thanks in advance! I appreciate anyones input
I assume you are using git with bitbucket. If that is the case you can do a pull from a master repo that contains your template grunt file in each of your project repositories for the desired effect.
See this answer for how to pull from a remote repo.
remote repo q
Since you only care about merging in changes from the Gruntfile.js you can pull it specifically from the remote template repo. I'd suggest following this pattern assuming you add the remote reference to you template repo when necessary:
From you project repo create a new branch
Pull the Gruntfile.js from the template repo
Resolve any merge conflicts
Merge with master
See the last answer on this question for how to pull a single file:
fetch a single file
In subversion I'm trying to commit a project but running into an issue.
The error I get is
Illegal repository URL ''
How come I can run update, but commit on the same tree shows that?
Try this, it worked for me:
Create a folder.
Right button over folder and create repo here.
When pop up appears select create folder structure and then open folder.
When repository browser appears you see tags branch etc, right button again and create folder but now with tool tortoise.
Update you file to folder.
After some hunting around it seems that a few other people have experienced some sort of local corruption at the top level their checked out project directory which is where I was committing from.
I followed the same procedure that was used to solve those cases which is to back up the sources. Check out the project again. Finally copy the changed files back over the freshly checked out copy. Check it builds correctly. And then commit that.
It seemed to solve it for me.