-
Notifications
You must be signed in to change notification settings - Fork 444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does Heroku auto update? #61
Comments
No it doesnt. You have to enable auto deployment from github on the Deploy tab of Heroku. Click Github under Deployment Method and then connect it to your fork in the next section below. But that will only keep it updated from your fork, or copy, of the crewlink-server. To keep that auto updated with the latest release of otto's main fork, I suggest using https://github.com/wei/pull |
So I'm fairly new to all this but I think I got it set. I installed the Pull app and it seems like it doesn't need any special settings, especially since CrewLink-server is my only fork. And Heroku is now pointed to my fork, which will stay up to date (it seems every couple hours or so) because the Pull app will push the update to it. If any of this is incorrect please let me know, but in my head that does seem correct. Thank you for the help! |
No problem! That's how I have it set up, but I'm new to this as well. I don't know if there's a better way to do it but seemed the simplest solution. |
As someone who normally updates his forks manually in the command line, pull looks great. It looks like it automates everything so you don't have to manually update your fork. As long as you have heroku set to auto deploy your changes, you should get automatic updates. (I haven't used heroku in a few years though so don't quote me on that.) |
Sorry if this is a dumb question. I just have a server running and I was assuming that when it's not working that it's because of an Among Us update. I just want to make sure there isn't anything specific that I need to do, or if I should just delete it and redeploy it
The text was updated successfully, but these errors were encountered: