Roadmap

1. Currently reset-onboarding is triggered button is getting disabled
2. User has no info what's going in background
3. Show a alert in server-details page that reset-onboarding triggered for server

• User should able to change these attributes from admin-panel
  • Favicon
  • Logo
  • Colors
  • Typography
• This allow users to make dFlow there own

Please ensure that the Beszel version remains fixed and does not auto-update or drift due to dependency changes or upstream modifications. This is important to maintain consistency across environments and avoid unexpected behavior during builds or deployments.

• Added utility functions to check if monitoring tools are already installed and to validate Beszel configuration.
• Enhanced the installMonitoringToolsAction to handle installation logic, including project creation and service setup.
• Introduced a new queue for monitoring service deployment, separating setup from deployment logic.
• Updated the onboarding component to manage installation state and provide user feedback on success or failure.

Replace Netdata monitoring with Beszel monitoring for deployment and operational purposes, but retain all code and configurations related to Netdata in the codebase.

• Integrate Beszel monitoring as the main monitoring solution for future operations.
• Update deployment scripts and documentation to reflect the use of Beszel, indicating Netdata is no longer actively used but is still present in the code.
• Ensure Beszel monitoring is functional and meets all project monitoring requirements.
• Do not remove or modify any Netdata-related code, scripts, or configurations in the repository.
• Clearly document that Netdata code remains for legacy/reference purposes.

Acceptance Criteria:

• Beszel monitoring is implemented and fully functional.
• Netdata code and configuration remain in the codebase.
• Documentation is updated to clarify current and legacy monitoring solutions.

Many users don’t have Discord accounts. Please consider using GitHub for eligibility instead, so more people can participate.

Display a toast notification to the user when a new version of the app is available. This will encourage users to refresh and use the latest build, preventing the use of stale versions.

Benefits:

• Ensures users always have access to the latest features and bug fixes.
• Improves user experience by avoiding issues caused by outdated builds.

Acceptance Criteria:

• Detect when a new version of the app is available.
• Show a clear and actionable toast notification prompting users to refresh or reload.
• The toast should only appear when the user is on a stale build.

Enhance the cloud-init script to support skipping any setup step using configurable flags. This improves flexibility for deployments, allowing users to customize which steps are executed.

Tasks:

• Refactor cloud-init script to accept flags for each major step
• Document available flags and their effects
• Ensure correct behavior when multiple steps are skipped or combined
• Add tests for flag-based step execution

This will provide better control over the initialization process for different environments or requirements.

Implement a comprehensive metrics dashboard in the admin-panel that provides the following insights:

Dashboard Features:

• Number of new users
• Total servers attached
• Number of services deployed
• Any other useful system or operational metrics (suggest additional insights based on available data)

This dashboard should help admins easily monitor key metrics and gain actionable insights into platform activity and growth.

• Allow users to add Neon and MongoDB Atlas as database integrations.
• During new service creation, users should be able to select one of the configured integrations.
• Selected integration should be linked to the new service.

Requesting a feature that allows upgrading server resources, such as increasing RAM from 8GB to 12GB or similar. This functionality should support dynamic resource scaling without requiring full server redeployment.

Make sure login, logout, and other auth actions stay in sync between the dFlow and dFlow App. If a user logs in or out on one, it should reflect on the other.

Feature Request: Support for Environments

Requirements:

1. Allow users to create multiple environments for the same project.
2. When a new environment is created, it should include data from the database of another environment (supporting database cloning/copying).
3. The new environment should be creatable within the same server or on a different server.

Benefits:

• Enables better staging, development, and testing workflows.
• Simplifies environment management for complex projects.

Additional Notes:

• Consider access control and isolation between environments.
• Ensure that database copy procedures do not interrupt production workloads.

1. After stopping a exposed database, and restarting it back again is failing

Error response from daemon: Cannot link to a non running container: /dokku.mongo.ideologica-db AS /dokku.mongo.ideologica-db.ambassador/mongo
Error: failed to start containers: dokku.mongo.ideologica-db.ambassador

2. When stopping a exposed database, we need to un-expose it first and stop, so during restart we won't have issue
3. after restart we need to expose the old ports

1. Add support dokku k3
2. Add support to convert attached servers as master nodes
3. Add support for attaching worker nodes

1. Currently we're not support hosting plain html, css files
2. We need serve static content using this static build

• 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

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