Susper is being improved every day. Following every best practice in the organization, each pull request includes a working demo link of the fix. Currently, the demo link for Susper can be generated by using GitHub pages by running these simple commands – ng build and npm run deploy. Sometimes this process on slow-internet connectivity takes up to 30 mins to generate a working demo link of the fix.
Surge is the technology which publishes or generates the static web-page demo link, which makes it easier for the developer to deploy their web-app. There are a lot of benefits of using surge over generating demo link using GitHub pages:
- As soon as the pull request passes Travis CI, the deployment link is generated. It has been set up as such, no extra terminal commands will be required.
- Faster loading compared to deployment link is generated using GitHub pages.
Surge can be used to deploy only static web pages. Static web pages mean websites that contain fixed contents.
To implement the feature of auto-deployment of pull request using surge, one can follow up these steps:
- Create a pr_deploy.sh file which will be executed during Travis CI testing.
- The pr_deploy.sh file can be executed after success i.e. when Travis CI passes by using command bash pr_deploy.sh.
The pr_deploy.sh file for Susper looks like this:
if [ “$TRAVIS_PULL_REQUEST” == “false” ]; then
echo “Not a PR. Skipping surge deployment.”
npm i -g surge
# Token of a dummy account
surge —project ./dist —domain $DEPLOY_DOMAIN;
Once pr_deploy.sh file has been created, execute the file in the travis.yml by using command bash pr_deploy.sh.
In this way, we have integrated the surge technology for auto-deployment of the pull requests in Susper.
- Static web publishing for the Front-End developers: https://surge.sh/
You must log in to post a comment.