[GH-ISSUE #90] Shell Script for dFlow App Deployment on Customer Server #57

New issue

Open

opened 2026-03-03 10:56:26 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 10:56:26 +03:00

Owner

Originally created by @manikanta9176 on GitHub (Apr 25, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/90

Originally assigned to: @akhil-naidu, @pavanbhaskardev, @manikanta9176 on GitHub.

Objective:

Eliminate the need for customers to have a Railway account to deploy the dFlow app.

Steps:

Customer buys a VPS from a cloud platform.
Run the shell script on the VPS to deploy the following:
- dFlow app (from the GitHub repo)
- Redis
- MongoDB
Accessing the deployed app:
- The customer will need either an IP address or a domain to access the application.
Onboarding process:
- On first access, the local server (master) will be automatically created.
- Slave servers will be set up during the process.
Project and server creation:
- Customers can create projects and servers using the local server (master).
Old architecture logic:
- The remaining logic will follow the same structure as the previous architecture.

Tasks:

Install dFlow on VPS:
- Deploy and utilize dFlow on the same VPS.
Install dFlow as a Master Service:
- Deploy dFlow on a VPS, making it the master, and then create services on slave nodes.

Originally created by @manikanta9176 on GitHub (Apr 25, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/90 Originally assigned to: @akhil-naidu, @pavanbhaskardev, @manikanta9176 on GitHub. --- ### **Objective**: **Eliminate the need for customers to have a Railway account** to deploy the dFlow app. --- ### **Steps**: 1. **Customer buys a VPS** from a cloud platform. 2. **Run the shell script** on the VPS to deploy the following: - dFlow app (from the GitHub repo) - Redis - MongoDB 3. **Accessing the deployed app**: - The customer will need either an **IP address** or a **domain** to access the application. 4. **Onboarding process**: - On first access, the **local server** (master) will be automatically created. - **Slave servers** will be set up during the process. 5. **Project and server creation**: - Customers can create **projects** and **servers** using the **local server** (master). 6. **Old architecture logic**: - The remaining logic will follow the same structure as the previous architecture. --- ### **Tasks**: 1. **Install dFlow on VPS**: - Deploy and utilize **dFlow** on the same VPS. 2. **Install dFlow as a Master Service**: - Deploy **dFlow** on a VPS, making it the **master**, and then create services on **slave nodes**. ---