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

Server Auto-Update #53

Open
SebastinSanty opened this issue Feb 10, 2018 · 1 comment
Open

Server Auto-Update #53

SebastinSanty opened this issue Feb 10, 2018 · 1 comment

Comments

@SebastinSanty
Copy link
Member

As discussed, we don't have access to SWD on our local networks. This calls for a need in having auto-updation of code on the server and restarting it, whenever there is a new commit in production branch. There are various ways to go about this:

  1. Using Webhooks: Using github webhooks, we can start a script on the server whenever there is a commit in the production branch. There is a bit of difficulty in implementing this, as webhooks require a public-facing domain. We can request CC to provide us a domain say swd1.bits-goa.ac.in(not sure how long the process for this will be). A workaround can be to use ngrok for creating a tunnel.

  2. Run a cron job, which checks every hour, whether there is a code update (using git fetch). But this will be a slow update.

  3. As @adiasg suggested, create a hashed url, which if hit runs a script to pull the code. This seems to be the best way to do as of now.

Please comment with your suggestions.

@aryanagarwal15
Copy link
Collaborator

@mehulmpt do you. want to take this up? Currently we don't have way to do it. But this is required as we go forward. Also we will need to put production and debug variables at the right places.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants