Roadmap

The "Start Onboarding" button should be disabled when any background process is running on the server or if the package installer is not free. This prevents users from starting onboarding while the system is busy, avoiding potential conflicts or errors.

• both project, service colloection has bi-directional relationship
• when fetching project or service with depth, the payload size in increasing
• decrease the usage of payload-depth and fetch only the necessary details

🐛 Bug: Adding Domain Fails with "Invalid Field: Cloud Provider Account"

Description

When trying to add a domain to a server, an error toast appears saying:
"Invalid field: cloud provider account", even though the form appears correctly filled.

🔁 Steps to Reproduce

1. Go to the Servers tab.
2. Select a server.
3. Navigate to the Domains section.
4. Attempt to add a new domain.
5. Submit the form.
6. Error toast appears: "Invalid field: cloud provider account"

🔗 Reproduction link: Jam Recording

1. When performing any normal operations like letsencrypt configuration stream current logs by showing previous logs
2. Persist the log history

• Change the naming convention of public and private repos. to something more appropriate.
• If Github integration was not done, let users know that till will not auto deploy.
• Change the icon while installing it.

Description

When deploying a public or community template, the volumes attached to the template are not being created during deployment.

🔁 Steps to Reproduce

1. Choose any public or community template.
2. Start the deployment process.
3. Proceed with the default or required setup steps.
4. Complete the deployment.
5. Observe that volumes specified in the template are not created.

🔗 Reproduction link: Jam Recording

🧾 Expected Behavior

All attached volumes defined in the template should be created automatically during deployment.

🧪 Environment (optional)

• OS: Windows 11
• Browser: Brave
• Node Version: 20

Description

Attempting to create a service inside a project fails immediately after clicking the deploy button.

🔁 Steps to Reproduce

1. Go to a project.
2. Click on "Create Service".
3. Fill in all required service details.
4. Click on "Create".
5. On the next screen, click "Deploy".
6. Deployment fails instantly.

🔗 Reproduction link: Jam Recording

🧾 Expected Behavior

Deployment should proceed and not fail immediately if all required fields are correctly filled.

🧪 Environment

• OS: Windows 11
• Browser: Brave
• Node Version: 20

Add proper validation while creating service

1. Each deployment should have cancel button which will cancel the deployment

Update the server card UI to include the source of creation. If the server originates from Dflow Cloud, also display its validity period.

Acceptance Criteria:

• Display a new line or badge showing the server source (e.g., "Created via Dflow Cloud" or "Manually Added").
• If the server is from Dflow Cloud:
  • Show validity period (e.g., "Valid until: July 15, 2025").
• Ensure the new UI elements adapt well to different card sizes.
• Data should be conditionally rendered based on available metadata.

1. Log all the actions triggered by the user
2. Log all the success and failure scenario's
3. Create commonly used logger-function which can log to console, update log to external telemetry source, and even can be use for redis pub, sub model

• Document what all queue's that can be triggered using payload-hooks
• Change queue triggering logic to payload hooks

• no signup
• no login
• app.dflow.sh, when not logged in redirect to dflow.sh/dashboard (internal login to dflow.sh/sign-in)

If /api/auto-login?token="123456" also, checks if user exists and if dons not exists automatically creates an account for them.

If a project name and service name are not unique, don't throw error and stop the process of creation of project or service, replace the project/service name with a unique name and continue the process.

eg-1: project name => hasura already exists => new project created with hasura => automatically suffix the new project name with hasura-1 eg-2: project name => hasura, and hasura-1 already exists => new project created with hasura or hasura-1 => automatically suffix the new project name with hasura-2

• ensure we opt for DRY
• ensure sendEvent itself does the log

• to ensure compatibility with monorepo setup

• auth groups
• jsx and ts
• if any other

Identify the build errors and try to resolve any warnings or errors and ensure build looks clean.

• chokidar dependencies
• any other
• redis internal connection errors

Ensure even the same on dflow marketing website.