I have an existing Rails app at heroku. I have a github account.
I'd like to use the Github Mac app to view/commit changes and push back up to Heroku. Can this be done? Or can the Github Mac client only push/sync with repos at Github? Since the remote repo is already at Heroku, I'd just assume leave it there and not create a duplicate at Github too.
But, If this can't be done. What would be the best way set this up so I can update my local repo, then push to Github, and push to Heroku? All using the Github Mac app?
Thanks
As specified in the documentation, you can use a non-GitHub remote (like Heroku) also.
Related
I have deployed a Rails 6 app to Heroku about 3 months ago. This was just a temporary website whilst I was creating the app. Now I want to push the new app to the existing Heroku app and overwrite whatever is already there, including a new database. How do I do that? The code is in a different repo locally.
HI you can do the following:
Add heroku as your remote on your new project
git push --force heroku master
connect to web console on heroku, drop database and recreate-it.
However, deleting the existing application and recreating it is simpler.
I'm trying to deploy my application to production on my laptop but i keep getting a
No application found matching remotes:
git#github.com:this_is_the_old_github_remote/Application.git
so this used to be the old remote but it was recently changed
so this makes sense but how do I fix this issue and tell it to go to the new one
There are a couple of ways to work around this issue.
Update the repository's config to have the proper URL for your remote branch.
Tell the ey cli tool which application and environment you are trying to deploy to.
The first method is probably better so you do not have to worry about this in the future.
To update your repository configuration you simply need to run git remote set-url origin https://url.to/new/repo/Applicatoin.git
Once the repository in your git configuration and the Engine Yard dashboard match, you should be able to deploy normally.
To work around this issue via the Engine Yard CLI utility, you will need to run ey deploy --app=<Application Name> --environment=<Environment Name>.
Please keep in mind, regardless of which method above you use to work around this issue, Engine Yard's automation will pull the application from the repository you configured via the dashboard.
Updating the remote on your git configuration does not update Engine Yard's configuration.
If your local copy of the repository has changes that have not been pushed to the remote repository configured at Engine Yard, the changes will not propagate to your instances.
If you continue to run into any issues deploying, please feel free to contact us via http://support.cloud.engineyard.com or in IRC on irc.freenode.net in #EngineYard.
I've recently set up bare, shared repository on a personal server and would like to push to heroku directly from there -- that is, NOT use github.
I guess I'm not sure I understand every part of the line where we add a remote:
git remote add heroku myherokuusername?#heroku.com:myherokureponame?.git
git remote add heroku git#heroku.com:taraswebapp.git # normally this
git remote add heroku tara.byte#heroku.com:taraswebapp.git
Other information:
I'm working on mac os x, and have recently installed the relevant heroku toolbelt.
my origin is: tara#192.168.1.160:/rails_projects/taraswebapp.git, where that is the static ip of my server
If you are doing the changes locally, you were once able to git push heroku master from your repo. This second bare repo on your server would be another thing completely different.
Now if you are sharing your bare repo, that'll be a different story.
Update #1:
Store your app in git from heroku docs should get you started and show you how it's done with another repo too.
Should my production Rails project use GIT? it will be easy for me to update the
servers and to push hot fixes, but what if I'll have a conflict during a pull?
and if I'll accidentally pull something wrong it make cause some downtime.
What is your advice on how to synch between the GIT repository & production?
Thanks
How about using a dedicated deployment system like Capistrano? It solves many of the issues you are trying to avoid.
Don't leave local changes on your production machines, and there is no risk of conflicts.
Production installs should pull from a dedicated branch/tag (e.g. use gitflow, production machines pull from the latest tag or simply master) - not the branch you regularly push to (develop, if you use git-flow).
In my server, what option i got is a basic unlimited server can host unlimited rails project
possible to manage gem because it is using cpanel latest version with a ssh
now my confuse is ,
how can i use the no ssh feature in the cpanel and ease my deployment ?
i don't know is that possible to use the capistrano and git with it
any guidance for this ? to make it possible to update with git push feature
i never deploy anything before ,
i tried to use heroku but i don't know why many user can make their file fit the 5mb space...
my project is now 30% at progress but the space used was 14mb...
so, i bought a cheap standard web server with cpanel . any one could help me in this case ?
usually how you guy deploy and where you deploy ?
recently one guy gave me a link for the github deployment, is that possible to make github use in the cpanel server ?
i mean like host and push the file into github and then link to the personal server ?
anyway, thx for person who reply me recently ^.^
i just develop for hobby...any cheap rails server suggest ?
Thx a lot for reply~
You could also try heroku (www.heroku.com) as a hosting platform. It has a simple deployment workflow that uses git.
Unelss you've done it already, you'll need to install git on your local machine.
Here's a bit about capistrano too.
Capistrano is basically a series of scripts (that you run from your local machine) that get your code and put it on your web server(s). You can configure capistrano to either check out your code from git on the production server, or to copy your code from your local machine.