Skip to content
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

[QUESTION] Developing during production? #949

Closed
amilner42 opened this issue Jun 20, 2019 · 4 comments

Comments

@amilner42
Copy link

commented Jun 20, 2019

Hello. I couldn't find docs on the recommended setup for developing while the github-app is in production? You'd have the webhook-url in your github-app settings directed towards your deployed instance of probot, so how would you develop locally?

All I have in mind now is just creating a copy of the repo, and having 2 repos, one for prod and one for local development, and constantly copying changes over from the local dev repo to the production repo. Is this the recommended way to develop locally on a github app in production?

@issue-label-bot

This comment has been minimized.

Copy link

commented Jun 20, 2019

Issue-Label Bot is automatically applying the label question ❓ to this issue, with a confidence of 0.98. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@stale

This comment has been minimized.

Copy link

commented Aug 19, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 19, 2019

@stale stale bot closed this Aug 26, 2019

@zeke

This comment has been minimized.

Copy link
Member

commented Aug 26, 2019

Hey @amilner42. Sorry nobody responded to this issue. It seems that most people will create multiple GitHub Apps for this. One for production, and one for staging/development. You should be able to develop in one repo, deploying your changes to a branch to your staging environment, or running those changes locally and development. If you want to use a single GitHub App for both staging and development, you can swap out the App's webhook URL to point to your smee.io webhook URL (for development) or your deployed app (for staging).

@amilner42

This comment has been minimized.

Copy link
Author

commented Aug 28, 2019

Thank you @zeke

That is the conclusion I came to as well, to just create 2 github-apps once you are in production and can no longer change the webhook url because it would stop webhooks for users in production.

Appreciate the follow-up!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.