If you haven’t checked out the first part of this walkthrough, take a look at the link below.
In this article we’re going to walkthrough the process of setting up AWS CodePipeline to automatically deploy our code from GitHub to our existing Docker environment on Elastic Beanstalk.
We’re going to skip the build process and address this in hopefully another walkthrough, but the main focus of this is just to automate our deployments.
If you haven’t guessed, the main benefit is so that we’re not deploying things manually every time we have a new feature pushed to our GitHub repository…
I won’t dive into the benefits of TypeScript, so I’ll assume that you already have a NodeJS TypeScript application that you want to bundle as a Docker image and deploy to a hosting service that supports Docker.
Docker is the main reason.
Docker is the main reason for setting up our app because it gives us more control over the Linux environment, what is installed, what it can do, and not be at the mercy of a hosting provides own configured Linux box.
This is a step-by-step guide on deploying NodeJS TypeScript Docker image on AWS Beanstalk. …
We’re building the frontend portion of the Amazon Wishlist App to allow you to search for Amazon products on Amazon.com and then add those items to your frontend we client.
Essentially what we are building is a way to ping Amazon.com’s website to be able to retrieve information that we need on products to be able to show on our own frontend.
This is a very simple base to be able to do some interesting things with their affiliate program or take advantage of being able to find information about specific products in more detail to use for your own internal app.
Some use-cases might include:
[1, , [3, ]] -> [1, 2, 3, 4]
In most cases I see this as a formatting issue or you need to get the data transformed into another form to easily access certain attributes. …
Often when I’m working on a project, or even when I inherit and existing project, the first thing I look at is the API. It’ll give me insight as to how the payload is handled, what status codes to account for, what conventions are being followed, and more.
If you’re going to take on an existing project, it’s always a good idea to factor in an audit of the API, even if there is documentation.
Don’t always trust the API Documentation. Do an Audit.
A client may not like it, but it’s better to find out problems at the beginning…
What we’re trying to do with this tutorial is to automate our code commits being tested and automatically deployed with CircleCI.
“Boils down to saving time.”
Sometimes developers don’t run unit tests and double check their code to make sure things are working correctly.
Let’s get started! We’re going to start by doing the basic the
npx create-react-app c;
Once the app is scaffolded out, let’s try a simple test.
yarn run test --watchAll=false; # npm run test--watchAll=false;# Expected Output # yarn run v1.16.0 # $ react-scripts test…
This will help you if in order for you to perform a task you need to gather a bunch of information in a specific order. Another scenario is that you need to automate a bunch of requests in a particular sequence. I’m going to cover the three ways to do this in a recursive function.
And yes I know there might be a more efficient way to do this GraphQL but that might not solve making multiple queries to multiple APIs.
For this tutorial, we’re going to use https://jsonplaceholder.typicode.com as our means to retrieve data.
If you have ever seen a progress file uploader that exists online, like Google Drive, or other major web application, that is essential what we’re building today, but with a simpler UI, and in React.
You just need Docker for this.
Pure and simple, security. There’s a bunch of other stuff as well, but mainly security.
To start, we’re going to use Alpine, because it’s the smallest footprint, and can be a good base for security as well. …