Harbinger Motors just opened its medium-duty EV truck factory in Garden Grove, CA, and plans to make cost-competitive trucks by end of year.

Harbinger Motors says its EVs will beat diesel trucks in price by end of year | Electrek

Crude&#x27;s flirtation with levels above $90 are both a political and economic challenge.

Why soaring oil prices threaten consumers, and Biden

Oil prices spiked on Friday morning following reports of heightened tensions between Iran and Israel, with American intelligence reports warning of a potential attack in the next 24 to 48 hours.

Oil Prices Surge on Fears of an Imminent Iranian Attack | OilPrice.com

Israel is preparing for a direct attack by Iran on southern or northern Israel as soon as Friday or Saturday, The Wall Street Journal reported.

U.S. crude oil gains as Israel reportedly prepares for attack by Iran this weekend

Pice is a B2B Payments platform that allows Small Businesses to pay their Vendors, Rent, GST and all other spend on a single Platform

pice

Anthrax — The Outsider.

This is the second in a series of articles on edge computing, delving into the infrastructure of outdoor edge computing, the emergence of the Roadside Unit as a common building block, a real-life example of the Roadside Unit, and the way forward. You can read part 1 here . You probably walk past it or drive past it every day. But it is inconspicuous for most people. And it is evolving and becoming more intelligent. More importantly, it is becoming the common building block for outdoor edge computing applications ranging from smart city, traffic management, and V2X (Vehicle To Everything) for self-driving vehicles, etc. It is called the oad ide nit (RSU.) R S U Overview of the Roadside Unit What is an RSU? From an ntelligent ransportation ystems (ITS) perspective, it is generally described as vehicular communication systems. The original definition of RSU was established by the ederal ommunications ommission (FCC) as part of the allocation of the 5.9 GHz band for ITS. Please see below. I T S F C C edicated hort ange ommunications) “Road Side Unit (RSU). A Roadside Unit is a DSRC ( D S R C transceiver that is mounted along a road or pedestrian passageway. An RSU may also be mounted on a vehicle or is hand-carried, but it may only operate when the vehicle or hand-carried unit is stationary. Furthermore, an RSU operating under this part is restricted to the location where it is licensed to operate. However, portable or hand-held RSUs are permitted to operate where they do not interfere with a site-licensed operation. An RSU broadcasts data to OBUs ( O n b oard U nits)or exchanges data with OBUs in its communications zone. An RSU also provides channel assignments and operating instructions to OBUs in its communications zone, when required.” Figure 2. Building blocks of a Roadside Unit. Source: US Department of Transportation (USDOT) Figure 2 above shows the building blocks of an RSU. Typically, this is what we will find inside the RSU. It includes a processor that runs the applications, data storage such as memory, and communications capabilities such as 4G/LTE or 5G and GPS receiver that support secure communications with passing vehicles, other field equipment, and centers. Beyond Traffic In addition to the traffic management, the communication capabilities of the roadside unit make it a perfect choice for a lot of applications such as automatic toll collection, connected or automated vehicles, weather warnings, and smart cities, etc. Here is an example of how RSU can help to reduce gas emission and fuel consumption. As you’re approaching a traffic light, have you ever wonder how long the light will last? Should you slow down, stop, or speed up? Sounds familiar? This video shows a test of eco signal operations at UC Berkeley’s Richmond Field Station. The signal phase and timing information of a traffic signal is communicated to a vehicle over a 4G/LTE network link. Based on the vehicle’s engine and gear maps, an optimal speed trajectory is calculated by an advanced traffic signal control algorithm that allows the vehicle to pass an intersection with minimal fuel consumption. Source: Turner-Fairbank Highway Research Center (TFHRC) With RSU, signal timing, and intersection location data can be obtained using connected vehicle technologies such as 5.9 gigahertz DSRC wireless communication, a global positioning system, SPaT (Signal Phase and Timing), and onboard equipment in the vehicle. As the vehicle approached the intelligent intersection, the onboard computer received SPaT and GID (Geometric Intersection Description) information from RSU connected to the signal. The computer interpreted the data and performed velocity planning, sending a message to the display device, which informed the driver the light would change to green and suggested a safe speed for approach and departure legs at the intersection. Using connected vehicle technologies, researchers at FHWA’s Turner-Fairbank Highway Research Center (TFHRC) were able to reduce emissions and fuel consumption. This savings is based on the energy a vehicle can save by driving through green lights without stopping which means burning less fuel and reducing emissions. Based on their experiments, they see a reduction of harmful emissions by about 12 percent and fuel savings between 10 and 20 percent. Reducing emissions is just one of the many possibilities with the Roadside Unit. How do we get more of these applications from experiments to the market faster? Accelerating Roadside Unit Deployment What is the biggest challenge when it comes to deploying roadside units? New York City is one of three Connected Vehicle (CV) pilot deployment sites selected by USDOT (U.S. Department of Transportation) to demonstrate the benefits of Connected Vehicle technology. The program started back in September 2015. As you can see from Figure 3 below, it is a three-phase, 75-month program. In other words, it took almost five years to get it up and running. Figure 3. Timeline for the New York City Connected Vehicles Project. Source: ( ) https://cvp.nyc/project-status There is always a steep learning curve when new technologies are introduced and tested. Surprisingly, the biggest challenge for deploying more RSUs is not technology. In a survey conducted by the USDOT back on September 19, 2019, sixty percent of respondents cited “Funding” as the biggest challenge in deploying ITS technologies. Please see below. Figure 4. Funding is the biggest challenge for deploying more RSUs. Source: US Department of Transporation When it comes to funding, it is not just the upfront cost to purchase and deploy the roadside unit. The ongoing operations and maintenance also cost money. Many of the local governments might have funding to get started but they do not have the funding to cover the recurring costs. To start with, the cost per device varies depending on what is inside the box. I have seen numbers ranging from $1,300 to $18,000 and it does not cover the cost of deployment. The on-going operations and maintenance can cost $2,000 to $3,000 a year. Below is an example from the Georgia Department of Transportation on how much it costs per device and the deployment cost for their connected vehicles project. Again the cost will vary depending on location, usage, and what is inside the roadside unit. For example, it will probably cost more to deploy and maintain a roadside unit in a metropolitan area like New York City. Figure 5. Capital cost and associated costs in deploying and maintaining an RSU. Source: Georgia Department of Transporation ( ) https://transportationops.org/sites/transops/files/GDOT%20V2I%20Update%20-%20July%202019.pdf How do we address the funding challenge? Assuming that funding from the government is limited, getting a new source of income from the service offered by the RSU will help cover some of the costs. For example, if the RSU is being used for automatic toll collection, part of the toll fees collected can be used to cover the operating and maintenance costs. In addition to lowering the cost of the RSU, increasing the capability of the RSU to handle more functions and devices will reduce the number of RSUs required. The Remaking of The Roadside Unit For the RSU to support more functions, it has to support a broader set of hardware devices than just being a communication device. To get a glimpse of the future of the Roadside Unit, let’s look at the testbed at the Antwerp Smart Highway test site. Figure 6. What is inside the RSU at the Antwerp Smart Highway test site? Source: Federation For Fire Plus The Road Side Units are deployed along the E313 highway in Antwerp (located in Belgium) on top of the gantries (a bridge-like overhead structure with a platform supporting equipment.) On top of the RSU are the antennas for the communication modules. See Figure 6 above. Figure 7. Block diagram of the RSU. Source: Federation For Fire Plus Each RSU consists of a large electrical cabinet that houses all the different modules of the RSU. See Figure 7. These include modules for wireless communication, modules for local processing on the RSU, and modules for remote management (reduce field service operating costs.) The hardware and communication modules inside the RSU provides support for V2X radio links, such as short-range based on ITS-G5 and C-V2X with PC5 interface working on 5.9 GHz. Vehicles equipped with the V2X will be able to receive information from the RSU. And the long-range communication is based on 4G. The modular design approach of the RSU has increases the serviceability as well as making it easy to add new capabilities to the box. One thing to note here is that the RSU is using a Supermicro Mini 1U Rackmount Server to do the local processing. See Figure 8. Instead of sending data back to the data center, the processing of data can be done locally. In addition to getting faster results, it’ll also save on backhaul communication costs. Figure 8. Mini 1U Rackmount Server from Supermicro The PICe slots inside the rackmount server will allow the end customers to support more devices such as network cards and VPU (Vision Processing Unit) cards etc. A good example is traffic cameras. By bringing more VPU cards into a single server to support more cameras, it’ll reduce the number of servers required to process the data from the traffic cameras, etc. As a result, the infrastructure cost as well as installation and maintenance costs will be lowered. Way Forward Roadside units (RSUs) have a crucial role in the future of the global economy. Yes, infrastructure takes time to build. However, there are so many pressing issues we are trying to resolve e.g. traffic congestion, pollution and climate change, etc. Beyond the funding issue, security and standard are the biggest challenges. To go beyond the proof of concept and scale, businesses and governments around the world need to work together to resolve these challenges. If you have any ideas and suggestions on how to accelerate the deployment of the Roadside Unit, please share them by leaving a comment. References 1. The Intelligent Transportation Systems Joint Program Office has a wealth of information and training materials. www.its.dot.gov Intelligent Transportation Systems - Joint Program Office Home Page The Office of the Secretary of Transportation (OST-R) is dedicated solely to the advancement of the U.S. Department of… 2. Emission Reductions, Fuel Savings Demonstrated At Turner-Fairbank www.fhwa.dot.gov Emission Reductions, Fuel Savings Demonstrated At Turner-Fairbank TFHRCâ€™s intelligent intersection delivers SPaT and GID data to a test vehicle equipped with a DSRC modem, computer… 3. The webpage has an excellent summary of the Smart Highway Testbed at Antwerp and a good overview of the implementation of an end-to-end solution. www.fed4fire.eu Smart Highway The Smart Highway testbed is designed for vehicle-to-everything (V2X) communication research. The Antwerp Smart Highway…

Edge Computing Is So Fun -
Part 2: The Future  Begins with The Road Side Unit

Tokenising the Enterprise. Klingon Style.

Rails 5 Imgur Clone Welcome to the second and final part of the Rails 5 Imgur clone, in this part, we will build the image uploading, manage configurations and then deploy to Heroku. Be sure to check out the first part if you haven’t already. here First, signup and verify a new cloudinary account by going , it’s my referral link to cloudinary which will give me little bit extra space. here Let’s start by adding few more variables to our cloudinary configuration at config/initializers/cloudinary.rb Remember, the has to exactly in that folder, if you open the you’ll see in the comments written it says the config has to be there, it’s just how rails configuration works. cloudinary.rb config/application.rb Make sure your looks something like this. cloudinary.rb . . [ ] . [ ] . [ ] . . Cloudinary config do | | config config cloud_name = ENV 'CLOUDINARY_CLOUD_NAME' config api_key = ENV 'CLOUDINARY_API_KEY' config api_secret = ENV 'CLOUDINARY_API_SECRET' config cdn_subdomain = true config enhance_image_tag = trueend Go to cloudinary dashboard and you will the variables which we will use. The inclusion of increases image serving performance by getting the best cdn location and adds more functions to the built in rails method. Cloud name, API Key, API Secret cdn_subdomain enhance_image_tag image_tag Okay, here we are dynamically setting environment variables to our application. It will pick up variables for production and development environments. You really don’t wanna hard code this as it is not safe and wise to publicize your keys and other info as these are highly sensitive. This style is highly recommended for any of your rails project not just this. It’s just really a damn good practice. You might think its just a home project but if you work at a company this is really serious so, it’s better to practice from now. Secondly, and this is the most important step, setting up your variables in your environment. We are going to use the gem. Add this to your and run in your terminal to install the gem and then restart your server. dotenv Gemfile bundle gem 'dotenv-rails', groups: [:development, :test] This is by far the best, easiest and simple solution and works perfectly. Now go to project’s root directory and create a file called .env We are going to set our variables like this. export CLOUDINARY_CLOUD_NAME=export CLOUDINARY_API_KEY=export CLOUDINARY_API_SECRET= Just put the variables as it is without any quotes. And then add to your so that it doesn’t get pushed to your GitHub repo. We are going to add Heroku cloudinary add-on and set the variable in the production environment in their way. .env .gitignore Alright, our configuration part is done for now. If you wanna further know about the gem then go to their and read more. dotenv github page Finally, we are going to add code to our controller for uploading and saving images to the database. Go to your controller at and add to your & method like this. pics_controller.rb new create .**newend def @pic = Pic new def @pic = Pic**. ( . ( ). ( )) . create new params require :pic permit :image @pic saveredirect_to @picend What we are doing here is basically creating an called @ and adding the method to our model which we will use it in all over our project. Later, in the create method we are allowing it to add to the database, then save it and take it to that pic page after it’s been saved to our database. instance variable pic new Pic Now, create a & in directory new.html.erb _form.html.erb app/views/pics/ In your add this code. _form.html.erb <%= <%= <%= <%= <% <%= ** .submit %>**<% form_for @pic do | | %> f .label :image do %> f .hidden_field :image_cache %> f .file_field :image %> f end %> f end %> So, here we are creating a form for a pic to be added to our database and then we are going to display it in the web. Now, we going to implement the show page and controller. In your add this following code pics_controller.rb . ( [ ]) def @pic = Pic show find params :id end Here we are pulling the data from database by their id Create a new file in directory and this simple line to display the image to the public show.html.erb app/views/pics/ <%= image_tag(@pic.image.url, width: '100%', crop: "scale")  %> We are also scaling the image to fit in the display so, that it looks beautiful. Great, your image is displayed now we are going to display all the images to our index/ home page. Open add this following code to controller to get all the images from the database pics_controller.rb index . def @pics = Pic index allend In your add this to loop through all the images and display it to the index page. index.html.erb <% <%=  **image_tag( .image.url, width: '100%', crop: "scale")  %>**<% @pics.each do | | %> pic pic end %> Now, we are going to prettify our app a little by adding simple bootstrap css and a navigation. Go to , it’s a bootstrap material design flavor which I really like, you could use this or anything else you like. Grab the link add it to the of your right below the csrf meta tags bootstrap head application.html.erb <link rel="stylesheet" href="https://bootswatch.com/paper/bootstrap.min.css"> Now, create a named inside the directory, and add the navigation to our header partial _header.html.erb app/views/layouts/ <%= <%= <nav class="navbar navbar-default"><div class="container-fluid"><div class="navbar-header"> link_to 'Rimgur', root_path, class: 'navbar-brand' %> link_to 'New Post', new_pic_path, class: 'navbar-brand' %></div></div></nav> And then render the header to our main application page. Add this to your on top application.html.erb yield <%= render 'layouts/header' %> Now, as a final step we are going to take our app live by deploying it to heroku. For our application to work on production, we need to do some modification to our Move the to group and add for P** ** for Gemfile. gem ‘sqlite’ development pg ostgreSQL production. **group :development dogem 'sqlite3'end group :production dogem 'pg'end** Then do this following to install the gems bundle gem install bundler Git add and commit all of your files. git add .; git commit -m ‘project finished’ Create a new git repo in your account and our codebase to it. Follow the instructions on the screen to do . git remote add and push Now, we are ready to take it live. Create a new account for FREE and verify it. Then, create a new heroku app in your terminal and push it. heroku heroku create git push heroku master We are going to have migrate our schema to production for our app to work. We can do it like this. heroku run rails db:migrate Do to open the app in browser. heroku open Okay, now you are going to do the most important step for our image uploading to work. heroku addons:create cloudinary:starter Remember, we set up the environment variables for for machine, now we are going to do it for our production. cloudinary development Go to your heroku dashboard, then to your app, and then to the cloudinary dashboard to get our configurations. Now, in your terminal do this following to add the config variables. heroku config:set CLOUDINARY_CLOUD_NAME= heroku config:set CLOUDINARY_API_KEY= heroku config:set CLOUDINARY_API_SECRET= Try uploading a pic in your app and then check the cloudinary dashboard that it’s been added. Congratulations, you have successfully built a fully functional web app. Feel free to play around with it and make it more awesome. Here is the link to my github . All the code is hosted here for your reference. repo Thank you for reading it, hope you enjoyed it and will use this knowledge to build something awesome. Subscribe me if you would like to receive future posts to your inbox. LIKE & SHARE if you have liked my post. Please comment below any feedbacks, suggestions or requests. Also please visit my website .

Rails 5 Imgur Clone Tutorial…Part 2

Companies that have pioneered the application of AI at scale did so using their own in-house ML platforms (uber, LinkedIn, Facebook, Airbnb). Many vendors are now making these capabilities available to purchase off-the-shelf products. There’s also a range of open-source tools addressing MLOps. The rush to the space has created a new problem - . There are now hundreds of tools and at least 40 platforms available: too much choice This is a very difficult landscape to navigate. But organizations have to figure it out because there is an imperative to get value from ML. Let’s understand the big challenges and then we’ll introduce some new free material that aims to address these problems. Challenge #1: Overwhelming Choice Chip Huyen gathered data on the . Chip found . Evaluations don’t have to consider all of these tools provided we can narrow them down to the ones that are most relevant to us... but that’s not easy to do. ML tool scene in 2020 284 tools and the number keeps on growing Challenge #2: Blurred Categories Typically we get a picture of which software does what by putting products in categories. There are attempts to do this with the , the , and . But often ML software does more than one thing and could fit into any of several categories. Platforms are especially hard to categorise as they explicitly aim to do more than one thing. LFAI Landscape diagram MAD landscape GitHub lists Because software that does several things is hard to categorize, ML platforms all tend to end up in a single category of ‘platform’. This obscures what emphasis each platform has and also loses all of the . nuances of how different platforms do similar things in different ways Challenge #3: Shifting Landscape ML categories are hard to keep track of in part because . Feature stores, for example, haven’t been around very long but are now a significant category. This affects platforms too as platforms are introducing big new features and changing their emphasis (in part in response to what new tools appear). new categories keep appearing Challenge #4: Complex Problems ML is complex. It’s also a big field. so that means understanding regression, classification, nlp, image processing, reinforcement learning, explainability, AutoML and a lot more. Platforms do a wide range of things Challenge #5: Range of Roles and Stakeholders Not only are the problems various and complex, there’s also a . Data Scientists, ML Engineers, Data Engineers, SRE, Product Managers, Architects, Application Developers, Platform Developers, End Users etc. Different roles have different points of interaction with the software and different needs from it. range of roles involved in the ML lifecycle Challenge #6: Build vs Buy and other controversies There’s a lot of discussion of build vs buy trade-offs in the ML space. How much control do organisations need over their stack? How much does that control cost? Build vs buy is often presented as an either-or but it is more of a spectrum. This is just one of the (consider how controversial AutoML is). confusing controversies in the ML space How do we get on top of all this? We’ve launched two new resources to help. For understanding the landscape and dealing with the trade-offs we’ve launched a Guide to Evaluating MLOps Platforms: https://www.thoughtworks.com/what-we-do/data-and-ai/cd4ml/guide-to-evaluating-mlops-platforms This is available for free without any sign-up. It addresses and . how to distinguish MLOps platforms how to structure an evaluation to suit the needs of your organisation We also need to apply this knowledge and see how to compare platforms against each other. For this we’ve released an open-source comparison matrix: https://github.com/thoughtworks/mlops-platforms The matrix is structured to highlight how vendors do things in their own ways and also point to more detail in the product documentation. We’ve also included in the repository a series of profiles that describe the product directions of popular platforms concisely and in a marketing-free way. We hope you find this material helpful and welcome contributions in GitHub. Feel free to ask any questions either on or to me directly on , . github twitter linkedin Title image by chenspec on pixabay.

How to Evaluate MLOps Platforms

The Noonification: How to Create a CI/CD Pipeline Using GitHub and AWS EC2 (5/1/2024)

Hey everyone, today I want to do a tutorial on one of my favorite ways to deploy a quick REST API, using NodeJS/Express, to an Amazon EC2 server. This technique essentially enables your EC2 server to respond to changes pushed to your GitHub repository. First Things First, “Hello World” Create a new directory on your machine for a NodeJS/Express app to live. I’m calling mine rekognition Open up a terminal, and run this command to initialize a package.json npm init -y Install express.js npm i express Create a basic express server with a ‘hello world’ at the default route const express = require('express');
const app = express();
const port = 3000;

app.get('/', (req, res) => {
    res.send('Hello World!');
});

app.listen(port, () => {
    console.log(`Example app listening at http://localhost:${port}`);
}); Test to make sure you are seeing ‘Hello World!’ at http://localhost:3000/ Good job, step one complete! 💪 Next, Let’s Push Our Code to GitHub Initialize a Git repo in your directory, and make your first commit — git init
git add .
git commit -m "First commit" Create a remote repository on your GitHub account Add the new repo as the origin, and push your branch. git remote add origin <REMOTE_REPOSITORY_URL>
git push -u origin master Replace <REMOTE_REPOSITORY_URL> with the link to the remote repo that you just created. You might need to change your repository settings to use ‘master’ as the default branch instead of ‘main.’ After you do this you can delete the ‘main’ branch. Step 2: complete! We’re cooking with gas ⛽️ Let’s Go to the Cloud — Setup the Ec2 Server Here are the steps to launch your EC2 Instance: Log in to your AWS Management Console. Navigate to the EC2 dashboard, and launch a new instance.



Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Select an instance type (e.g., t2.micro if you are under the free tier). Configure instance details, add storage, and add tags as necessary. Configure a security group to allow inbound traffic on ports you’ll need (at least TCP port 22 for SSH and your application’s port, and then 3000 for web traffic). Review and launch the instance; ensure that you save the key pair used for SSH access. Now, let’s test logging into your server via SSH on a terminal: ssh ec2-user@<YOUR_SERVER_IP> -i <YOUR_PRIVATE_KEY>.pem Replace the variables there with the values you defined for your EC2 instance. If you see this you’ve connected to your server, congrats! 👏 We’re Not Done Just Yet Though — We’re Just Getting Started 😏 Let’s install NodeJS on our server:sudo yum install -y nodejs Install pm2 globally on our server via npm sudo npm i -g pm2 Install git on the server, and configure your credentials: sudo yum install git -y git config --global user.name "Your Name"
git config --global user.email "your.email@example.com" Okay, now we’re going to create a var/www/ folder if it does not already exist: sudo mkdir -p /var/www Then add ownership to our ec2-user: sudo chown -R ec2-user:ec2-user /var/www Navigate to the directory from the root of your server — not the /home folder people 👌 cd ~/var/www Now, from here, we will clone our git repository: git clone https://github.com/USERNAME/REPO_NAME.git YOUR_PROJECT_DIRECTORY Replace [USERNAME] [REPO_NAME] and [YOUR_PROJECT_DIRECTORY] with your own values. Next, we change the directory into our repository, so cd YOUR_PROJECT_DIRECTORYcan create the ecosystem.config.js file for our pm2 setup: nano ecosystem.config.js It looks like this: module.exports = {
  apps : [{
    name: "my-app",  // A name for your application
    script: "app.js",  // The script file to launch the app
    instances: "max",  // This can be set to the number of CPU cores to use, or "max" to use all available
    autorestart: true,  // Automatically restart app if it crashes
    watch: false,  // Enable/disable watching file changes for automatic restart
    max_memory_restart: '1G',  // Optional: Restart app if it reaches a memory limit
    env: {
      NODE_ENV: "development",
    },
    env_production: {
      NODE_ENV: "production",
    }
  }]
}; Cool beans, okay — once that is created and saved, let’s start up the app with pm2: pm2 start ecosystem.config.js Now, we can check that we have a ‘Hello World!’ from our server on port 3000: To make pm2 start automatically on server restarts, let’s run: pm2 save
pm2 startup To check your server is running, you can do pm2 status;  you can read the docs on pm2 here If you’ve made it this far, you are a superstar ⭐️ Integration With GitHub Actions This is the last step in our process. We’re going to create a .yml file for Github actions to update our server anytime a change is pushed to our master branch In your repository, go to the ‘Actions’ tab and create a new custom workflow. I am calling mine nodejs.yml Here is the .yml file for updating the repo and restarting pm2: name: Node.js CI/CD on Amazon Linux

on:
  push:
    branches: [ master ]

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Install dependencies
      run: npm install

    - name: Deploy to AWS EC2
      uses: appleboy/scp-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        source: "./"  # This now correctly points to the current directory
        target: "/var/www/your_project_directory"

    - name: Restart PM2 application
      uses: appleboy/ssh-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        script: |
          cd /var/www/your_project_directory
          pm2 reload all  # This command restarts your application Make sure to update ‘your_project_directory’ Lastly, you’ll need to add these environment secrets. REMOTE_HOSTthis is the IP address of your server; REMOTE_USER this is ec2-user for Amazon Linux 2 AMI, and then paste the contents of your .pem file as the SSH_PRIVATE_KEY You can do all of this in the repository settings: That’s it! We’re done yay 😁 You can test this all by changing the ‘Hello World’ message and pushing that change to your master branch; then you should see the update at http://your.ip.address:3000 It is a bit of a process to set up, but when you’re developing, it’s really nice to have an easy CI/CD pipeline automatically deploying changes to your REST API server. That way, you can quickly deploy the changes live and see them in the front end of your web/mobile application. Let me know if this was useful in the comments, and thanks for reading!! Peace out, — Wes Hey everyone, today I want to do a tutorial on one of my favorite ways to deploy a quick REST API, using NodeJS/Express, to an Amazon EC2 server. This technique essentially enables your EC2 server to respond to changes pushed to your GitHub repository. First Things First, “Hello World” Create a new directory on your machine for a NodeJS/Express app to live. I’m calling mine rekognition rekognition Open up a terminal, and run this command to initialize a package.json npm init -y npm init -y Install express.js npm i express npm i express Create a basic express server with a ‘hello world’ at the default route const express = require('express');
const app = express();
const port = 3000;

app.get('/', (req, res) => {
    res.send('Hello World!');
});

app.listen(port, () => {
    console.log(`Example app listening at http://localhost:${port}`);
}); const express = require('express');
const app = express();
const port = 3000;

app.get('/', (req, res) => {
    res.send('Hello World!');
});

app.listen(port, () => {
    console.log(`Example app listening at http://localhost:${port}`);
}); Test to make sure you are seeing ‘Hello World!’ at http://localhost:3000/ http://localhost:3000/ Good job, step one complete! 💪 Next, Let’s Push Our Code to GitHub Initialize a Git repo in your directory, and make your first commit — git init
git add .
git commit -m "First commit" git init
git add .
git commit -m "First commit" Create a remote repository on your GitHub account Add the new repo as the origin, and push your branch. git remote add origin <REMOTE_REPOSITORY_URL>
git push -u origin master git remote add origin <REMOTE_REPOSITORY_URL>
git push -u origin master Replace <REMOTE_REPOSITORY_URL> with the link to the remote repo that you just created. <REMOTE_REPOSITORY_URL> You might need to change your repository settings to use ‘master’ as the default branch instead of ‘main.’ After you do this you can delete the ‘main’ branch. Step 2: complete! We’re cooking with gas ⛽️ Let’s Go to the Cloud — Setup the Ec2 Server Here are the steps to launch your EC2 Instance: Log in to your AWS Management Console. Log in to your AWS Management Console . AWS Management Console Navigate to the EC2 dashboard, and launch a new instance. Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Navigate to the EC2 dashboard, and launch a new instance. Navigate to the EC2 dashboard, and launch a new instance. Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Select an instance type (e.g., t2.micro if you are under the free tier). Select an instance type (e.g., t2.micro if you are under the free tier). Configure instance details, add storage, and add tags as necessary. Configure instance details, add storage, and add tags as necessary. Configure a security group to allow inbound traffic on ports you’ll need (at least TCP port 22 for SSH and your application’s port, and then 3000 for web traffic). Configure a security group to allow inbound traffic on ports you’ll need (at least TCP port 22 for SSH and your application’s port, and then 3000 for web traffic). Review and launch the instance; ensure that you save the key pair used for SSH access. Review and launch the instance; ensure that you save the key pair used for SSH access. Now, let’s test logging into your server via SSH on a terminal: ssh ec2-user@<YOUR_SERVER_IP> -i <YOUR_PRIVATE_KEY>.pem ssh ec2-user@<YOUR_SERVER_IP> -i <YOUR_PRIVATE_KEY>.pem Replace the variables there with the values you defined for your EC2 instance. If you see this you’ve connected to your server, congrats! 👏 We’re Not Done Just Yet Though — We’re Just Getting Started 😏 Let’s install NodeJS on our server: sudo yum install -y nodejs sudo yum install -y nodejs Install pm2 globally on our server via npm pm2 sudo npm i -g pm2 sudo npm i -g pm2 Install git on the server, and configure your credentials: sudo yum install git -y sudo yum install git -y git config --global user.name "Your Name"
git config --global user.email "your.email@example.com" git config --global user.name "Your Name"
git config --global user.email "your.email@example.com" Okay, now we’re going to create a var/www/ folder if it does not already exist: var/www/ sudo mkdir -p /var/www sudo mkdir -p /var/www Then add ownership to our ec2-user: sudo chown -R ec2-user:ec2-user /var/www sudo chown -R ec2-user:ec2-user /var/www Navigate to the directory from the root of your server — not the /home folder people 👌 cd ~/var/www from the root of your server cd ~/var/www Now, from here, we will clone our git repository: git clone https://github.com/USERNAME/REPO_NAME.git YOUR_PROJECT_DIRECTORY git clone https://github.com/USERNAME/REPO_NAME.git YOUR_PROJECT_DIRECTORY Replace [USERNAME] [REPO_NAME] and [YOUR_PROJECT_DIRECTORY] with your own values. Next, we change the directory into our repository, so cd YOUR_PROJECT_DIRECTORY can create the ecosystem.config.js file for our pm2 setup: cd YOUR_PROJECT_DIRECTORY ecosystem.config.js nano ecosystem.config.js nano ecosystem.config.js It looks like this: module.exports = {
  apps : [{
    name: "my-app",  // A name for your application
    script: "app.js",  // The script file to launch the app
    instances: "max",  // This can be set to the number of CPU cores to use, or "max" to use all available
    autorestart: true,  // Automatically restart app if it crashes
    watch: false,  // Enable/disable watching file changes for automatic restart
    max_memory_restart: '1G',  // Optional: Restart app if it reaches a memory limit
    env: {
      NODE_ENV: "development",
    },
    env_production: {
      NODE_ENV: "production",
    }
  }]
}; module.exports = {
  apps : [{
    name: "my-app",  // A name for your application
    script: "app.js",  // The script file to launch the app
    instances: "max",  // This can be set to the number of CPU cores to use, or "max" to use all available
    autorestart: true,  // Automatically restart app if it crashes
    watch: false,  // Enable/disable watching file changes for automatic restart
    max_memory_restart: '1G',  // Optional: Restart app if it reaches a memory limit
    env: {
      NODE_ENV: "development",
    },
    env_production: {
      NODE_ENV: "production",
    }
  }]
}; Cool beans, okay — once that is created and saved, let’s start up the app with pm2: pm2 start ecosystem.config.js pm2 start ecosystem.config.js Now, we can check that we have a ‘Hello World!’ from our server on port 3000: To make pm2 start automatically on server restarts, let’s run: pm2 save
pm2 startup pm2 save
pm2 startup To check your server is running, you can do pm2 status ;  you can read the docs on pm2 here pm2 status pm2 here If you’ve made it this far, you are a superstar ⭐️ Integration With GitHub Actions This is the last step in our process. We’re going to create a .yml file for Github actions to update our server anytime a change is pushed to our master branch .yml In your repository, go to the ‘Actions’ tab and create a new custom workflow. I am calling mine nodejs.yml nodejs.yml Here is the .yml file for updating the repo and restarting pm2: name: Node.js CI/CD on Amazon Linux

on:
  push:
    branches: [ master ]

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Install dependencies
      run: npm install

    - name: Deploy to AWS EC2
      uses: appleboy/scp-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        source: "./"  # This now correctly points to the current directory
        target: "/var/www/your_project_directory"

    - name: Restart PM2 application
      uses: appleboy/ssh-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        script: |
          cd /var/www/your_project_directory
          pm2 reload all  # This command restarts your application name: Node.js CI/CD on Amazon Linux

on:
  push:
    branches: [ master ]

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Install dependencies
      run: npm install

    - name: Deploy to AWS EC2
      uses: appleboy/scp-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        source: "./"  # This now correctly points to the current directory
        target: "/var/www/your_project_directory"

    - name: Restart PM2 application
      uses: appleboy/ssh-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        script: |
          cd /var/www/your_project_directory
          pm2 reload all  # This command restarts your application Make sure to update ‘your_project_directory’ Lastly, you’ll need to add these environment secrets. REMOTE_HOST this is the IP address of your server; REMOTE_USER this is ec2-user for Amazon Linux 2 AMI, and then paste the contents of your .pem file as the SSH_PRIVATE_KEY REMOTE_HOST REMOTE_USER ec2-user SSH_PRIVATE_KEY You can do all of this in the repository settings: That’s it! We’re done yay 😁 You can test this all by changing the ‘Hello World’ message and pushing that change to your master branch; then you should see the update at http://your.ip.address:3000 http://your.ip.address:3000 It is a bit of a process to set up, but when you’re developing, it’s really nice to have an easy CI/CD pipeline automatically deploying changes to your REST API server. That way, you can quickly deploy the changes live and see them in the front end of your web/mobile application. Let me know if this was useful in the comments, and thanks for reading!! Peace out, — Wes

How to Create a CI/CD Pipeline Using GitHub and AWS EC2

GitHub এবং AWS EC2 ব্যবহার করে কিভাবে একটি CI/CD পাইপলাইন তৈরি করবেন

So erstellen Sie eine CI/CD-Pipeline mit GitHub und AWS EC2

Cómo crear una canalización de CI/CD utilizando GitHub y AWS EC2

Comment créer un pipeline CI/CD à l'aide de GitHub et AWS EC2

GitHub और AWS EC2 का उपयोग करके CI/CD पाइपलाइन कैसे बनाएं

GitHub と AWS EC2 を使用して CI/CD パイプラインを作成する方法

GitHub 및 AWS EC2를 사용하여 CI/CD 파이프라인을 만드는 방법

Como criar um pipeline de CI/CD usando GitHub e AWS EC2

Как создать конвейер CI/CD с помощью GitHub и AWS EC2

GitHub ve AWS EC2 Kullanılarak CI/CD Ardışık Düzeni Nasıl Oluşturulur

Cách tạo quy trình CI/CD bằng GitHub và AWS EC2

如何使用 GitHub 和 AWS EC2 创建 CI/CD 管道

PIECHAIN Demo: Exploring a Practical Blockchain Interoperability Framework

পাইচেন ডেমো: একটি ব্যবহারিক ব্লকচেইন ইন্টারঅপারেবিলিটি ফ্রেমওয়ার্ক অন্বেষণ করা

PIECHAIN-Demo: Erkundung eines praktischen Blockchain-Interoperabilitätsrahmens

Demostración de PIECHAIN: Explorando un marco práctico de interoperabilidad de Blockchain

Démo PIECHAIN : Explorer un cadre pratique d'interopérabilité de la blockchain

PIECHAIN डेमो: एक व्यावहारिक ब्लॉकचेन इंटरऑपरेबिलिटी फ्रेमवर्क की खोज

PIECHAIN デモ: 実用的なブロックチェーン相互運用性フレームワークの探究

PIECHAIN 데모: 실용적인 블록체인 상호 운용성 프레임워크 탐색

Demonstração PIECHAIN: Explorando uma estrutura prática de interoperabilidade Blockchain

Демонстрация PIECHAIN: изучение практической структуры взаимодействия блокчейнов

PIECHAIN Demosu: Pratik Bir Blockchain Birlikte Çalışabilirlik Çerçevesini Keşfetmek

Bản trình diễn PIECHAIN: Khám phá Khung tương tác Blockchain thực tế

PIECHAIN 演示：探索实用的区块链互操作性框架

pice

pice.one

-- employees

Since n.d.

COMPANY RANKING

PICE

EVERGREEN INDEX #8409

pice WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

pice

pice.one

-- employees

Since n.d.

COMPANY RANKING

PICE

EVERGREEN INDEX #8409

RELATED COMPANIESRANK

STORIES ABOUT PICE

pice WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!