Automatic Deployment With Github Actions


    In this video we will setup automatic deployments using Github Actions.

    Anson’s YouTube Channel:

    Github Actions Page:

    0:00 – Introduction & Demo
    3:07 – Setting up Github Actions
    4:07 – Setting up Workflow File
    8:07 – Setting up Github Action Runner
    14:37 – Setting up NGINX
    21:09 – Pointing domain to our Server
    22:17 – React Routing with NGINX
    22:52 – Setting up Expressjs API
    30:14 – Proxy Passing with NGINX
    39:04 – Setting up Server Block
    40:53 – Securing our Website


    Previous articleCI CD Pipeline Using Jenkins | Continuous Integration and Deployment | DevOps Tutorial | Edureka
    Next articleKubernetes Vs Docker | Difference between Kubernetes and Docker | Kubernetes Training | Edureka


    1. I have implemented ci/cd successfully following this tutorial….but i'm facing a problem regarding env variable….my project depends on .env file and as i can't keep the env file in my repo obviously….so how can i generate .env file from github action so everytime i push i don't have to create .env file manually?

    2. Does the solution break if the build step will not success? For te react app, when GA detect push, the runner will purge the local files and try to build the app. If the build fails, the files will be broken and nginx will serve broken site. Am I wrong? Or the react cares about broken builds and do not touch the output directory until it is sure that the build will work?

    3. Thank you very much! I had already my server in the root of my instance, and the /actions-runner folder is created in there as well, then when you make your first "deploy" with the actions, it creates again the repo within the /actions-runner folder. So i had to kill all processes from the server i had before, remove it and then i was able to see the actual server attached to the action deploys runining with the changes made on the master branch. Just in any case you guys have the same issue