In this lesson, I will walk you through triggering a workflow in a second Github repository. The most common use case is probably for triggering a single batch of tests while your code base is divided among multiple repositories. Another great use is triggering deployments of your API (in its own repo) before deploying your frontend (web app). This can be done fairly simply with a Github Action called Trigger Workflow and Wait.
If you are running a web application, you will want to know if users are experiencing errors. You will want to gather logs and gather insights. There are many tools out that can help with this and today I’m going to show you LogRocket. I like LogRocket because it only takes a few lines to setup and you can have complete customizability.
A few weeks ago there was a lot of the internet attention around the recently opened for beta project called GPT-3. Generative Pre-trained Transformer 3 (GPT-3) is an autoregressive language model that uses deep learning to produce human-like text. It is the third-generation language prediction model in the GPT-n series created by OpenAI, a for-profit San Francisco-based artificial intelligence research laboratory.
In this tutorial, I will step through the steps for accepting payments. We will use Coinbase and therefore will require a Coinbase account. I will publish lessons on using other services but because of the popularity (in my world) of Coinbase, it’s the first service I will demonstrate how to integrate with.
In this tutorial, I will step through the steps for accepting payments. We will use Coinbase and therefore will require a Coinbase account. I will publish lessons on using other services but because of the popularity (in my world) of Coinbase, it’s the first service I will demonstrate how to integrate with.
NPM helps notify you have vulnerable dependencies by printing out a message during installation. At times, this isn’t enough. It is very easy to ignore these messages and commonly security becomes a low priority. In this tutorial, I will show you how to setup a script for checking if there are vulnerabilities and a automatic way of running it using Github Actions.
In this tutorial, I walk you through setting up a simple React.js application that can be hosted on Github Pages. I really like hosting here because it’s free for me personally, and Github handles “server management”. Once I deploy my React app and verify it’s up, Github handles the traffic surges, updates, etc.
In this lesson, we setup a Jenkins CI/CD pipeline on a Digital Ocean droplet. It will trigger on push events to the master branch of a Git repository and build the project. These pipelines are excellent for validating your code changes are properly tested, and changes are instantly deployed after they’re verified. When you are trying to build a resilient system you have to ask yourself, how long is recovery if your servers go down? What’s the playbook for recovery? Using a tool like Jenkins allows this to potentially be a single click.
In this tutorial, we focus on running Github Actions on the push event for specific branches. This may be useful if you only want to test on feature branches and do a deployment if master. This was the use case for me. After the tests have passed, the the code review has been approved. It’s time to deploy to production. This is merging to master and running a series of steps. Github Actions makes it very simple to run specific actions/workflows on specific branches.
In this tutorial, I will walk you through deploying your Docker container to a Digital Ocean droplet. All commands will be manually run. You can automate this process if you would like but the purpose is for getting you up and running. My Docker container will be running a Springboot app on port 8080. I expect you to have some sort of Docker container with a basic web page (API, hello world, full web app, anything at the root).
