-
Notifications
You must be signed in to change notification settings - Fork 5
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
Have a CI/CD pipeline #57
Comments
@rhoegg I'm guessing that you have something in mind that's different from our current staging site? https://techlahoma-donations-staging.herokuapp.com/ |
Maybe not, let me look at it and see if there's any value I can add |
The CI/auto-deployment stuff that you mentioned in Slack earlier would be awesome. |
Yeah makes sense. Can you send me what you do now to deploy staging and production, and how you make sure things are cool afterward? |
@rhoegg It's currently a manual push to heroku for either. I have the staging site setup as a git remote called To test a branch on the staging site I do something like:
When I'm happy with it, I merge that branch to master, and then push master to production.
On both sites to make sure things are cool, I load the site, click around, and make a (sometimes small) donation. I also run the test suite locally before most pushes. |
Right, I think I need access to the same heroku account you're using,
right? Where do you set up the DNS?
…On Thu, Mar 9, 2017, 8:24 AM Jeremy Green ***@***.***> wrote:
@rhoegg <https://github.com/rhoegg> It's currently a manual push to
heroku for either. I have the staging site setup as a git remote called
staging and the production site set up as a git remote called production.
To test a branch on the staging site I do something like:
git push staging my-branch:master
When I'm happy with it, I merge that branch to master, and then push
master to production.
git push production master
On both sites to make sure things are cool, I load the site, click around,
and make a (sometimes small) donation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACuD4yihWTZVWXNo7BdkRAUcZBa-xf0ks5rkCfDgaJpZM4MV8Kn>
.
|
@rhoegg So sorry for the delay. I somehow missed this when you last responded. If you'll DM me your heroku email address I'll invite you to both apps. I wanna say it's DNSimple where we have the DNS setup. I think @seejessicacode may be able to help us with that. |
donate.techlahoma.org points to donate.techlahoma.org.herokudns.com |
@seejessicacode where do we manage those records? |
DNSimple.com, I've just shared management permissions with your Techlahoma gmail. |
@rhoegg, this looks interesting : https://devcenter.heroku.com/articles/heroku-ci |
No description provided.
The text was updated successfully, but these errors were encountered: