Projects
A Project represents anything you deploy on Dadisiweb — a website, web app, API, background service, or database-backed application. Each project runs in its own isolated environment.
Project Types
When creating a project, you choose how it runs:
- Static Project
Used for HTML, CSS, and JavaScript sites that don’t need a server.
Examples: Landing pages, portfolios, documentation sites. - Service Project
Used for applications that run a server or backend process.
Examples: Next.js, Node.js APIs, Django apps, Laravel, Flask.
Core Project Settings
- Project Name
A human-readable name for your project (e.g.landing-page,api-server). This is how you identify it in the dashboard. - Root Directory
The folder that contains your app inside the uploaded ZIP or GitHub repo.
Example:/,/frontend,/apps/web - Runtime
Defines how your project runs.
Examples: Node.js, Python, PHP
Build & Run Commands
- Build Command
Runs once during deployment to prepare your app.
Examples:npm install,npm run build - Run Command
Starts your application server.
Examples:npm start,python app.py
Resource Tier
The tier defines how much CPU, memory, and bandwidth your project gets. Higher tiers support heavier traffic and workloads.
Monitoring & Logs
- Logs
View live application output, errors, and startup logs. - Usage
Monitor CPU, memory, and bandwidth usage for your project.
Environment Variables
Environment variables store secrets and configuration values.
Examples:
DATABASE_URLAPI_KEYNODE_ENV=production
Deployments
- Deploy – First time deployment.
- Redeploy – Restart and redeploy after code or config changes.
- Stop / Restart – Control your running service.
Projects with Databases
Some projects connect to a database. Database details are managed in the project settings.
- Database Name – Logical name of your database.
- Database URL / Connection String
Used by your app to connect to the database. - Supported DBMS
- PostgreSQL
- MySQL
- MariaDB