large_Deploy_On_Pipeops_be984335cd.png

medium_Deploy_On_Pipeops_be984335cd.png

small_Deploy_On_Pipeops_be984335cd.png

thumbnail_Deploy_On_Pipeops_be984335cd.png

Deploy_On_Pipeops_be984335cd.png

# Creating Servers In Naira On PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

In this section, we'll guide you through setting up your PipeOps account using one of PipeOps' own servers. Follow these steps to configure your server and seamlessly deploy your applications.

\
&nbsp;

### Step 1: Select Your Server Hosting Platform

\
&nbsp;

Whether you are just continuing your account creation process or just trying to deploy an extra server, The below guide still applies to both cases. After choosing to proceed from the previous step, you will be brought to this page.

1. You'll be prompted to choose where you want to create your server.

2. Select "**On PipeOps**" as your server creation method.

\
&nbsp;

![Choose path](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Deploy_On_Pipeops_be984335cd.png)

\
&nbsp;


### Step 2: Decide On The Physical Location Of Your Server

 

You'll then be directed to:

1. Choose a server name.

2. Select your server location. We've implemented a geo-location pricing model to ensure you're billed in your local currency, shielding you from exchange rate fluctuations.

\
&nbsp;

![Choose region](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Choose_Region_eb8ef21a43.png)

\
&nbsp;

### Step 3: Customize Your Server

After selecting the location for your server, it's time to tailor it to your specific needs. Customize your server based on these three key metrics:

\
&nbsp;


1. **VCPU (Virtual Central Processing Unit)**:

 - Choose the number of virtual CPUs to allocate to your server. This determines the processing power available for running your applications and handling tasks.

\
&nbsp;

2. **Memory**:

 - Select the amount of memory (RAM) to allocate to your server. Memory is crucial for storing and accessing data while your applications are running. Choose a suitable amount based on the requirements of your applications and workload.

\
&nbsp;

3. **Storage**:

 - Determine the storage capacity for your server, which includes both the operating system and data storage. Consider the size of your applications and the amount of data they generate to ensure you have adequate storage space. You can also choose between different storage types, such as solid-state drives (SSD) or hard disk drives (HDD), depending on performance and cost considerations.

\
&nbsp;

You can choose between the **Nova Sapa**, **Nova Pro**, **Nova Duo** and **Nova Chrono** server instances. Each instance comes with varying amounts of VCPU, Memory and storage.

\
&nbsp;


![Customize Your Server](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Choose_Specs_c908e16387.png)

\
&nbsp;

By customizing these aspects of your server, you can optimize its performance and resource allocation to meet the specific demands of your applications and workload.

 

Once you've decided on your desired server instance, PipeOps will automatically check if your credit balance covers the cost.

 

if you don't have enough credits for your desired server instance, you'll be directed to a payment portal where you can make the necessary payment to access seamless deployments with PipeOps.

\
&nbsp;

![Payment modal](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Payment_Confirmation_7fff228669.png)

\
&nbsp;

However, if your credits are sufficient, the transaction will be deducted from your credit balance without any additional charges.

\
&nbsp;

### Step 4: Payment Completion
 
After successfully making payment for your server, you'll receive a confirmation stating "Congratulations! Your subscription is active." Click on the **Done** button to proceed to the next steps in the setup process.

\
&nbsp;

### Step 5: Server Creation in Progress
 
In this next step, the platform will display the progress of your server creation on the screen.

\
&nbsp;

![Server Creation Progress](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/26/In_Progress_65b9125d74.png)

\
&nbsp;

### Step 6: Server Creation Complete

1. After the server creation is complete, a confirmation message will appear.

2. Click **Proceed** to get to the server overview page of the server you just created.

\
&nbsp;

![Server Creation Successful](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/26/Done_daa41dcdec.png)

\
&nbsp;

![Server Overview](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/26/Overview_027a244c0c.png)


\
&nbsp;

### Step 7: Proceed to project deployment

 

After successfully creating a server, you can now proceed to deploy your applications into that server. See the [Project Deployment Guide](https://docs.pipeops.io/docs/projects/project-deployment) for a comprehensive guide to getting your applications up and running with PipeOps.

Creating Servers In Naira On PipeOps

# Creating Affordable Servers On PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

In this section, we'll guide you through setting up your PipeOps account using one of PipeOps' own servers. Follow these steps to configure your server and seamlessly deploy your applications.

\
&nbsp;

### Step 1: Select Your Server Hosting Platform

\
&nbsp;

Whether you are just continuing your account creation process or just trying to deploy an extra server, The below guide still applies to both cases. After choosing to proceed from the previous step, you will be brought to this page.

1. You'll be prompted to choose where you want to create your server.

2. Select "**On PipeOps**" as your server creation method.

\
&nbsp;

![Choose path](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Deploy_On_Pipeops_be984335cd.png)

\
&nbsp;


### Step 2: Decide On The Physical Location Of Your Server

 

You'll then be directed to:

1. Choose a server name.

2. Select your server location. We've implemented a geo-location pricing model to ensure you're billed in your local currency, shielding you from exchange rate fluctuations.

\
&nbsp;

![Choose region](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Choose_Region_eb8ef21a43.png)

\
&nbsp;

### Step 3: Customize Your Server

After selecting the location for your server, it's time to tailor it to your specific needs. Customize your server based on these three key metrics:

\
&nbsp;


1. **VCPU (Virtual Central Processing Unit)**:

 - Choose the number of virtual CPUs to allocate to your server. This determines the processing power available for running your applications and handling tasks.

\
&nbsp;

2. **Memory**:

 - Select the amount of memory (RAM) to allocate to your server. Memory is crucial for storing and accessing data while your applications are running. Choose a suitable amount based on the requirements of your applications and workload.

\
&nbsp;

3. **Storage**:

 - Determine the storage capacity for your server, which includes both the operating system and data storage. Consider the size of your applications and the amount of data they generate to ensure you have adequate storage space. You can also choose between different storage types, such as solid-state drives (SSD) or hard disk drives (HDD), depending on performance and cost considerations.

\
&nbsp;

You can choose between the **Nova Sapa**, **Nova Pro**, **Nova Duo** and **Nova Chrono** server instances. Each instance comes with varying amounts of VCPU, Memory and storage.

\
&nbsp;


![Customize Your Server](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Choose_Specs_c908e16387.png)

\
&nbsp;

By customizing these aspects of your server, you can optimize its performance and resource allocation to meet the specific demands of your applications and workload.

 

Once you've decided on your desired server instance, PipeOps will automatically check if your credit balance covers the cost.

 

if you don't have enough credits for your desired server instance, you'll be directed to a payment portal where you can make the necessary payment to access seamless deployments with PipeOps.

\
&nbsp;

![Payment modal](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Payment_Confirmation_7fff228669.png)

\
&nbsp;

However, if your credits are sufficient, the transaction will be deducted from your credit balance without any additional charges.

\
&nbsp;

### Step 4: Payment Completion
 
After successfully making payment for your server, you'll receive a confirmation stating "Congratulations! Your subscription is active." Click on the **Done** button to proceed to the next steps in the setup process.

\
&nbsp;

### Step 5: Server Creation in Progress
 
In this next step, the platform will display the progress of your server creation on the screen.

\
&nbsp;

![Server Creation Progress](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/26/In_Progress_65b9125d74.png)

\
&nbsp;

### Step 6: Server Creation Complete

1. After the server creation is complete, a confirmation message will appear.

2. Click **Proceed** to get to the server overview page of the server you just created.

\
&nbsp;

![Server Creation Successful](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/26/Done_daa41dcdec.png)

\
&nbsp;

![Server Overview](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/26/Overview_027a244c0c.png)


\
&nbsp;

### Step 7: Proceed to project deployment

 

After successfully creating a server, you can now proceed to deploy your applications into that server. See the [Project Deployment Guide](https://docs.pipeops.io/docs/projects/project-deployment) for a comprehensive guide to getting your applications up and running with PipeOps.

Creating servers on pipeops

# Deployment Path Guide
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

## Choosing a deployment path

You can choose between deploying to PipeOps's servers or your preferred cloud provider (AWS, Azure, GCP) for seamless deployment tailored to your needs.


&nbsp;

## Step 1: On PipeOps

In this section, we'll guide you through setting up one of PipeOps' own servers. Follow these steps: [On PipeOps](https://docs.pipeops.io/docs/getting-started/deployment-path/on-pipeops).
\
&nbsp;

![PipeOps homepage](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Deploy_On_Pipeops_be984335cd.png)

\
&nbsp;

## Step 2: On Cloud Provider

In this section, we will show how you can set up your PipeOps account using your cloud Provider. Follow these steps to set up your account and seamlessly deploy your applications on AWS. [On Cloud Provider](https://docs.pipeops.io/docs/getting-started/deployment-path/on-cloud-provider).

\
&nbsp;

![PipeOps homepage](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/Deploy_On_Cloud_d5e1edc1a2.png)

\
&nbsp;


For any additional questions or support, please contact us at [Support Contact](mailto:support@pipeops.io)

Deployment Path On PipeOps

# User Registration Guide
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

## Getting Started with PipeOps Registration

Welcome to PipeOps! In this guide, we'll walk you through the simple and seamless registration process to get you started with our powerful deployment solutions.

\
&nbsp;

## Step 1: Visit the Home Page

Open your preferred web browser and navigate to the pipeops homepage. You can use the direct URL: [https://pipeops.io](https://pipeops.io).
\
&nbsp;

![PipeOps homepage](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/homepage_d3d284d5fd.png)

\
&nbsp;

## Step 2: Visit the Registration Page

To begin the registration process, click on the 'Deploy app' or 'Deploy a free app' button on the top right corner, or the middle of your screen. This would redirect you to the pipeops signin console. Click on the 'Create a new account here' link, and begin your registration. Or use the direct URL: [https://console.pipeops.io/auth/signup](https://console.pipeops.io/auth/signup).

\
&nbsp;

![PipeOps homepage](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/homepage1_331e37d64b.png)

\
&nbsp;

## Step 3: Sign In Options

In the 'Create an account' sign up box, you have 4 options to sign up.

- Sign up using your existing GitHub account.

- Sign up using your existing GitLab account.

- Sign up using your existing BitBucket account.

- Sign up using an email account.

In the first 3 options, you will need to enter your credentials to allow pipeops connect with your account. You also will not need to connect to that repository provider later if you already chose it as your sign up method.

\
&nbsp;

![PipeOps homepage](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/signin_b8cfb0bcd8.png)

\
&nbsp;

## Step 4: Provide Your Email Address

On the registration page, for the email option, you'll be prompted to enter your email address. This will be your primary contact for important updates and notifications related to your account. Please make sure to use a valid and accessible email address.

\
&nbsp;

## Step 5: Set a Strong Password

Create a secure password for your account. A strong password typically includes a combination of uppercase and lowercase letters, numbers, and special characters. This ensures the safety and integrity of your account. Click on 'Proceed'.

\
&nbsp;

## Step 6: Verify Your Email Address

After submitting the registration form, you will be redirected to a page requesting for your registration OTP. Check your email inbox for a verification message containing the token, paste into the box and proceed.

\
&nbsp;

![PipeOps homepage](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/otp_a12ad0250c.png)

\
&nbsp;

## Step 7: Customize Your Workspace

Before completing the registration, we want to tailor your experience with PipeOps to suit your needs. You would answer the following questions to configure your workspace:

1. **Workspace Name:**

   - This section prompts you to choose a name for your workspace. The workspace name helps you organize and distinguish your projects within PipeOps.

\
&nbsp;

![Workspace name](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/workspace_76e1748c31.png)

\
&nbsp;

2. **Your role/Job Title:**

   - Here, you can specify your role or job title, which provides context for your usage of PipeOps. Whether you're a software developer, founder, or DevOps engineer, identifying your role will help us serve you better.

\
&nbsp;

![Role](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/role_e2a25cc747.png)

\
&nbsp;

3. **Goal with PipeOps:**

   - This section helps clarify your objectives for using PipeOps. You can select from options such as exploring PipeOps features for companies or deploying a simple project to the cloud. Understanding your goals allows us to provide relevant guidance and support.

\
&nbsp;

![Goal](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/needs_c09f9b7a53.png)

\
&nbsp;

4. **Discovering PipeOps:**
    
   - This section inquires about how you found out about PipeOps. Whether through Linkedin, a goole search, or another avenue, knowing how users discover PipeOps helps us improve and reach more people.

\
&nbsp;

![Discover ](https://pub-30c11acc143348fcae20835653c5514d.r2.dev//20/25/discover_419f076830.png)

\
&nbsp;

Once you've answered these questions, your workspace will be configured accordingly, providing a personalized experience tailored to your specific requirements.

\
&nbsp;

## Step 8: Complete Registration

After customizing your workspace, you're now ready to complete the registration process. Review the information you've provided, make any necessary adjustments, and click the "Finish" button.

You are now set to proceed with deploying your server either on PipeOps or a cloud provider. Head to the [***Deployment Path***](https://docs.pipeops.io/docs/category/deployment-path) section for guidance.


User Registration Guide

large_s7.png

medium_s7.png

small_s7.png

thumbnail_s7.png

s7.png

Welcome to the streamlined integration of PipeOps with GitHub. This guide will walk you through the steps to authenticate PipeOps with your GitHub account, ensuring a seamless connection for enhanced collaboration for efficient cloud deployments.

Let's simplify your development process

\
&nbsp;

## Prerequisites:
Begin by creating your [GitHub Account](https://github.com/), if you haven't already

\
&nbsp;

## How to Configure Your GitHub Public Email

Configure your GitHub public email for a seamless authentication process. This step is essential for the authentication process and account creation. PipeOps uses this email to create your account for future authentication.

GitHub typically sets the email to private by default, but it's essential to adjust this setting to ensure a smooth and successful integration with PipeOps. By making your email public, you facilitate a more transparent and efficient collaboration between both platforms.

Now let's follow the steps below to ensure your GitHub email is set to public, allowing PipeOps to authenticate and create your account seamlessly.

\
&nbsp;

## First Step

-  The first step is to navigate to your settings
\
&nbsp;

 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s1_2e5b2504a4.png)
 
\
&nbsp;

- Select the **emails** under the Access button
\
&nbsp;

 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s2_a9c6b8c047.png) 

\
&nbsp;

- Scroll down and uncheck the *keep my email addresses private* to inactive. This will allow your verified email(s) to be Public.

\
&nbsp;

 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s3_4097b293d4.png) 

\
&nbsp;

## Second step:

- Next, Navigate to the **public profile**, still in the settings.
- On the Public Profile page, Select the verified email from the Public Email field list(s)

\
&nbsp;
 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s4_fc7030a2fb.png) 
\
&nbsp;


- Click on the update button below to update the changes.

- Allow some minutes for GitHub to sync this change to your settings.

*You have successfully updated your public email. Next let's authenticate with PipeOps*

\
&nbsp;

## Authentication from PipeOps 

Before authenticating with GitHub from the PipeOps Dashboard, let's confirm the following checkpoints below, you can refer to the above steps on how to configure them.

\
&nbsp;
 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s5_dcc948088d.png) 
\
&nbsp;

- Active GitHub account

- GitHub Public Email Configured.

\
&nbsp;

Once the above checkpoints are met, Authentication with PipeOps is a straightforward next step.

- Simply navigate to the PipeOps dashboard, where you'll find intuitive options to link different version control providers, in this case, we are using the GitHub option.

- Follow the prompts to connect securely with PipeOps and your GitHub account.

\
&nbsp;
 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s6_db80472c33.png) 
\
&nbsp;
\
&nbsp;

This user-friendly authentication process ensures you can quickly integrate PipeOps into your workflow, making cloud management a smooth and efficient experience.

- On successful authentication, you are automatically redirected to your project dashboard.


\
&nbsp;
 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s7_046ab43f32.png) 
\
&nbsp;


*You have successfully authenticated your GitHub with PipeOps*

## How to remove PipeOps Authorization from a GitHub Account.

Maintain control and security by easily revoking PipeOps authorization from your GitHub account when needed. Should the necessity arise,

- Navigate to your GitHub account settings, specifically the **Authorized OAuth apps** section.

- Here, you'll find a list of connected applications, including PipeOps. 
Select PipeOps from the list and follow the prompts to revoke its authorization or you can **revoke all** to remove access to all your applications.
\
&nbsp;
\
&nbsp;

 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/s8_963dd882e2.png) 

\
&nbsp;

This simple yet crucial step ensures that you have full control over the access granted to PipeOps, allowing you to manage your GitHub integrations securely and in alignment with your preferences.

How to Authenticate with PipeOps Using  GitHub

large_LINK THUMBNAIL.png

medium_LINK THUMBNAIL.png

small_LINK THUMBNAIL.png

thumbnail_LINK THUMBNAIL.png

LINK THUMBNAIL.png

## 502 Bad Gateway Error
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


The 502 Bad Gateway error is a common HTTP status code indicating a communication issue between web servers. It arises when a server, often acting as a gateway or proxy, receives an invalid response from another server. This guide will walk you through diagnosing and resolving the 502 Bad Gateway error for your website or web application hosted on PipeOps.
\
&nbsp;
\
&nbsp;


 ![](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/gateway_f9074e620c.webp) 


\
&nbsp;

## Step 1: Project Port
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


Before we dive in, let's verify the port your project uses. If you're deploying your project using a Dockerfile on PipeOps, you can easily find your project's port by inspecting your Dockerfile.

\
&nbsp;


 ![Guide image](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/docker_6ebac84519.webp) 


\
&nbsp;

## Step 2: Networking Port
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Once you know your project's port, let's ensure that the networking port corresponds to the one specified in your Dockerfile or project settings. To do this, follow these steps:

1. Access your project on PipeOps.
\
&nbsp;
2. Click on the "Settings" tab.
\
&nbsp;
3. Locate the "Networking" section, where you will find your project's port.
\
&nbsp;
4. If the ports don't match, update the networking port to match your project's port.
\
&nbsp;
5. Click the "Save" button to trigger a new deployment.

\
&nbsp;

![Guide image](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/networking_1a532e13eb.webp) 


\
&nbsp;

## Step 3: Environment Variable (PORT and HOST)
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


With the networking port in sync, it's time to confirm that the PORT and HOST environment variables are correctly configured. Here's how to check:

1. Access your project settings.
\
&nbsp;
2. Navigate to the "Environment Variables" tab.
\
&nbsp;
3. Verify that the PORT and HOST variables are correctly set. Ensure that the HOST is set to `0.0.0.0` to allow access from any IP address.
\
&nbsp;
4. If the PORT doesn't match your project's port, update it.
\
&nbsp;
5. Click the "Save" button to initiate a new deployment.
\
&nbsp;


![Guide image](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/env_84d983de0d.webp) 


\
&nbsp;

## Step 4: Final Verification
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


After the new deployment, revisit your project to check if it's functioning correctly:

\
&nbsp;


![Guide image](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/final_c101ba06c1.webp) 


\
&nbsp;

## Additional Tip: Checking Project Logs
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

For further debugging assistance, you can review your project's logs tab to examine the PORT and HOST settings.
\
&nbsp;


![Guide image](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/logs_aa8231b16e.webp) 


\
&nbsp;

    👍 Awesome!

    You have now fixed your Bad Gateway error. Your website or web application should be up and running smoothly.



502 Bad Gateway Error

## Django On PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

PipeOps is the ideal platform for deploying your Django applications due to its robust support. As you read on, you'll discover just how effortless it is to deploy your project.

\
&nbsp;
\
&nbsp;



## Getting Started
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

For a quick and hassle-free start, you can clone our pre-built Django template from here. This template comes with a Dockerfile that will be used during deployment. However, if you already have a project to deploy, you'll need to create a Dockerfile and copy the relevant information from our Django template Dockerfile into your project's Dockerfile.

\
&nbsp;

Here's an example Dockerfile based on our Django template:

\
&nbsp;
\
&nbsp;


```
# Set the base image to Python 3.9
FROM python:3.11.0

# Set environment variables
ENV PYTHONUNBUFFERED 1
ENV PYTHONDONTWRITEBYTECODE 1

# Set the working directory to /app
WORKDIR /app

# Copy the requirements file into the container and install dependencies
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt

# Copy the application code into the container
COPY . .

# Run database migrations
RUN python manage.py migrate

# Expose port 8000 for the Django application
EXPOSE 8000

# Start the Django development server
CMD ["python", "manage.py", "runserver", "0.0.0.0:8000"]
```

\
&nbsp;
\
&nbsp;



## Deploy Your Project
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

We assume that you've gone through our get started guide. If not, you can access it here. Once you've gone through the guide, you can proceed to connect your PipeOps account to your preferred git provider and select your project. In the image below, you'll find the necessary configurations for your Django project. After completing these configurations, you can click on the "Deploy Project" button to deploy your project.

\
&nbsp;
\
&nbsp;

![nodejs.webp](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/nodejs_5d30a33b7f.webp)

\
&nbsp;
\
&nbsp;


👍 Awesome!, You have now deployed your PHP project.

\
&nbsp;

![image_5_bhabno.png](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/image_5_bhabno_649203b253.png)

Django On PipeOps

## Node.js On PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

PipeOps is the ideal platform for deploying your Node.js applications due to its robust support. As you read on, you'll discover just how effortless it is to deploy your project.

\
&nbsp;
\
&nbsp;



## Getting Started
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

For a quick and hassle-free start, you can clone our pre-built Node.js template from here. This template comes with a Dockerfile that will be used during deployment. However, if you already have a project to deploy, you'll need to create a Dockerfile and copy the relevant information from our Node.js template Dockerfile into your project's Dockerfile.

\
&nbsp;

Here's an example Dockerfile based on our Node.js template:

\
&nbsp;
\
&nbsp;


```

FROM node:18

# Create app directory
WORKDIR /usr/src/app

# Install app dependencies
# A wildcard is used to ensure both package.json AND package-lock.json are copied
# where available (npm@5+)
COPY package*.json ./

RUN npm install
# If you are building your code for production
# RUN npm ci --omit=dev

# Bundle app source
COPY . .

EXPOSE 8080
CMD [ "node", "server.js" ]

```

\
&nbsp;
\
&nbsp;



## Deploy Your Project
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

We assume that you've gone through our get started guide. If not, you can access it here. Once you've gone through the guide, you can proceed to connect your PipeOps account to your preferred git provider and select your project. In the image below, you'll find the necessary configurations for your Node.js project. After completing these configurations, you can click on the "Deploy Project" button to deploy your project. 

\
&nbsp;

![nodejs.webp](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/nodejs_5d30a33b7f.webp)


\
&nbsp;



👍 Awesome!, You have now deployed your PHP project.


\
&nbsp;

![image_5_bhabno.png](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/image_5_bhabno_649203b253.png)



Node.js On PipeOps

## Rust On PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

PipeOps is the ideal platform for deploying your Rust applications due to its robust support. As you read on, you'll discover just how effortless it is to deploy your project.

\
&nbsp;
\
&nbsp;



## Getting Started
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

For a quick and hassle-free start, you can clone our pre-built Rust template from here. This template comes with a Dockerfile that will be used during deployment. However, if you already have a project to deploy, you'll need to create a Dockerfile and copy the relevant information from our Rust template Dockerfile into your project's Dockerfile.

\
&nbsp;

Here's an example Dockerfile based on our Rust template:

\
&nbsp;
\
&nbsp;


```

# Use a Rust base image
FROM rust:latest as build

# Set the working directory in the container
WORKDIR /app

# Copy the Cargo.toml and Cargo.lock files to the container
COPY Cargo.toml ./

# Create an empty project with the same dependencies to cache them
RUN mkdir src && \
    echo "fn main() {println!(\"if you see this, the build broke\")}" > src/main.rs && \
    cargo build --release && \
    rm -f target/release/deps/pipeops-rust*

# Copy the rest of the source code to the container
COPY . .

# Build the Rust application
RUN cargo build --release

# Create a smaller final image
FROM debian:buster-slim

# Set the working directory in the final image
WORKDIR /app

# Copy the built application from the build image to the final image
COPY --from=build /app/target/release/pipeops-rust .

# Expose the port your Rust web application listens on (change as needed)
EXPOSE 8000

# Command to run your Rust web application (adjust as needed)
CMD ["./pipeops-rust"]


```

\
&nbsp;
\
&nbsp;



## Deploy Your Project
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

We assume that you've gone through our get started guide. If not, you can access it here. Once you've gone through the guide, you can proceed to connect your PipeOps account to your preferred git provider and select your project. In the image below, you'll find the necessary configurations for your Rust project. After completing these configurations, you can click on the "Deploy Project" button to deploy your project. 

\
&nbsp;

![nodejs.webp](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/nodejs_5d30a33b7f.webp)


\
&nbsp;



👍 Awesome!, You have now deployed your PHP project.


\
&nbsp;

![image_5_bhabno.png](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/image_5_bhabno_649203b253.png)



Rust On PipeOps

## PHP On PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

PipeOps is the ideal platform for deploying your PHP applications due to its robust support. As you read on, you'll discover just how effortless it is to deploy your project.

\
&nbsp;
\
&nbsp;



## Getting Started
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

For a quick and hassle-free start, you can clone our pre-built PHP template from here. This template comes with a Dockerfile that will be used during deployment. However, if you already have a project to deploy, you'll need to create a Dockerfile and copy the relevant information from our PHP template Dockerfile into your project's Dockerfile.

\
&nbsp;

Here's an example Dockerfile based on our PHP template:

\
&nbsp;
\
&nbsp;


```
# Use an official PHP runtime as the base image
FROM php:7.4-apache
FROM php:7.4-apache
# Set the working directory in the container
WORKDIR /var/www/html
# Copy the application code to the container
COPY . /var/www/html
# Install any necessary PHP extensions or dependencies
RUN apt-get update && \
    apt-get install -y \
        # Add any additional dependencies here
    && rm -rf /var/lib/apt/lists/* \
    && docker-php-ext-install mysqli pdo pdo_mysql \
    && a2enmod rewrite
# Expose port 80 for the Apache web server
EXPOSE 80
# Define environment variables if needed
# ENV MY_ENV_VAR=value
# Start the Apache web server
CMD ["apache2-foreground"]
```

\
&nbsp;
\
&nbsp;



## Deploy Your Project
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

We assume that you've gone through our get started guide. If not, you can access it here. Once you've gone through the guide, you can proceed to connect your PipeOps account to your preferred git provider and select your project. In the image below, you'll find the necessary configurations for your PHP project. After completing these configurations, you can click on the "Deploy Project" button to deploy your project.

\
&nbsp;
\
&nbsp;

![nodejs.webp](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/nodejs_5d30a33b7f.webp)

\
&nbsp;
\
&nbsp;


👍 Awesome!, You have now deployed your PHP project.

\
&nbsp;

![image_5_bhabno.png](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/image_5_bhabno_649203b253.png)

PHP On PipeOps

## Flask On PipeOps
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
\
&nbsp;

PipeOps is the ideal platform for deploying your Flask applications due to its robust support. As you read on, you'll discover just how effortless it is to deploy your project.

\
&nbsp;
\
&nbsp;



## Getting Started
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

For a quick and hassle-free start, you can clone our pre-built Flask template from [here](https://github.com/pipeops-dev/pipeops-flask). This template comes with a Dockerfile that will be used during deployment. However, if you already have a project to deploy, you'll need to create a Dockerfile and copy the relevant information from our Flask template Dockerfile into your project's Dockerfile.

\
&nbsp;

Here's an example Dockerfile based on our Flask template:

\
&nbsp;
\
&nbsp;


```

# Set the base image to Python 3.9
FROM python:3.11.0

# Set environment variables
ENV PYTHONUNBUFFERED 1
ENV PYTHONDONTWRITEBYTECODE 1

# Set the working directory to /app
WORKDIR /app

# Copy the requirements file into the container and install dependencies
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt

# Copy the application code into the container
COPY . .

# Expose port 5000 for the Flask application
EXPOSE 5000

# Start the Flask development server
CMD ["python", "manage.py", "0.0.0.0:5000"]

```

\
&nbsp;
\
&nbsp;



## Deploy Your Project
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

\
&nbsp;

We assume that you've gone through our get started guide. If not, you can access it [here](https://docs.pipeops.io/developers). Once you've gone through the guide, you can proceed to connect your PipeOps account to your preferred git provider and select your project. In the image below, you'll find the necessary configurations for your Flask project. After completing these configurations, you can click on the "Deploy Project" button to deploy your project.

\
&nbsp;

![nodejs.webp](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/nodejs_5d30a33b7f.webp)


\
&nbsp;



👍 Awesome!, You have now deployed your PHP project.


\
&nbsp;

![image_5_bhabno.png](https://pub-30c11acc143348fcae20835653c5514d.r2.dev/image_5_bhabno_649203b253.png)



Flask On PipeOps

## PipeOps Deployment Support

The table below contains a comprehensive list of Pipeops-compatible frameworks, including their compatible build methods for deployment and corresponding run commands.

\
&nbsp;

| Frameworks    | Build Method                        | Run Command                           |
| :------------ | :--------------------------------- | ------------------------------------ |
| Django        | Paketo, Heroku, Dockerfile          | `python manage.py runserver`          |
| Ruby on Rails | Dockerfile, Heroku, Paketo          | `bin/rails server`                    |
| Flask         | Paketo, Heroku, Dockerfile          | `python {{the file}}`                 |
| Express       | Dockerfile, Heroku, Paketo, Node    | `node {{the file}}`                   |
| React         | Paketo, Heroku, Dockerfile, Node    | `npm dev`, `yarn dev`, `pnpm dev`     |
| Angular       | Dockerfile, Heroku, Paketo, Node    | `ng serve`                            |
| Laravel       | Paketo, Heroku, Dockerfile          | `php artisan serve`                   |
| Spring        | Dockerfile, Heroku, Paketo          | `java -jar target/{{project-name}}.jar`|
| ASP.NET       | Paketo, Heroku, Dockerfile          | `dotnet watch`                        |
| Vue.js        | Dockerfile, Heroku, Paketo, Node    | `npm dev`, `yarn dev`, `pnpm dev`     |
| FastAPI       | Paketo, Heroku, Dockerfile          | `python {{the file}}`                 |
| Gin           | Dockerfile, Heroku, Paketo          | `go run {{the file}}`                 |
| Fiber         | Dockerfile, Heroku, Paketo          | `go run {{the file}}`                 |
| Next.js       | Paketo, Heroku, Dockerfile, Node    | `npm dev`, `yarn dev`, `pnpm dev`     |
| Nuxt.js       | Dockerfile, Heroku, Paketo, Node    | `npm dev`, `yarn dev`, `pnpm dev`     |
| Nest.js          | Paketo, Heroku, Dockerfile, Node    | `npm run start`                       |
| Solid.js      | Dockerfile, Heroku, Paketo, Node    | `npm run dev`                         |

Guides