Roadmap
Loading roadmap...
Loading roadmap...
Moves traefik configuration from fileProvider to etcd, uses cloudflare origin-certificate & custom-hostnames instead of letsencrypt resolver
Everytime when service is deployed a new certificate is generated using the wildcard domain, Cloudflare origin-certificate resolves that single certificate for entire wild-card domain. We now can use Cloudflare DDOS, WAF and BOT protection.
serviceName.serverHostname.up.domain.com -> serviceName-serverHostname.up.domain.cometcd instead for fileProvider
- Use cloudflare origin certificate instead on letsencrypt resolver#499 opened by pavanbhaskardev
Log user actions (account creation, server onboarding, project deployment, etc.) with timestamps and metadata. Build activity collection with dynamic activity types, tracking utility, and server actions for retrieval.
#493 opened by manikanta9176
#492 opened by pavanbhaskardev
Currently we're using letsencrypt for SSL certificate generation
#489 opened by pavanbhaskardev
create-flags while creating database: https://github.com/dokku/dokku-mongo?tab=readme-ov-file#create-a-mongo-service#488 opened by pavanbhaskardev
Currently, auto-login functionality does not work when sessions are enabled in the PayloadCMS configuration. Auto-login should support session-based authentication.
#485 opened by pavanbhaskardev
Currently, users cannot restore a backup to a newly created database. There is also no validation to prevent restoring a backup file of the wrong type (e.g., restoring a MongoDB backup to a PostgreSQL database).
#484 opened by pavanbhaskardev
The current backups UI does not display the database backup type, and backups for deleted services are grouped as deleted services, causing loss of detailed information.
#483 opened by pavanbhaskardev
Make as Default button always disabled in Domains. Reproduction link Generate default Domain in onboarding getting undefined.up.dflow.sh if connection type is SSH#432 opened by jagadeesh507
#425 opened by pavanbhaskardev
Currently, the GitHub App deployment is triggered for the x-github-event: push. To improve deployment automation, we need to also trigger deployments when a fork-sync event occurs.
Proposed Solution:
fork-sync event.fork-sync is received, similar to how it works for push events.Motivation:
Additional Context:
#422 opened by pavanbhaskardev
Synchronize Dokku actions performed on the server with the website. The solution should:
#417 opened by manikanta9176
Provide a secure way for users to access the server terminal through the platform. This should include authentication and appropriate permission controls to ensure only authorized access.
#416 opened by manikanta9176
Implement a feature to enable users to add new Dokku plugins through the system interface. This should allow for easier integration and management of Dokku plugins directly from the platform.
#415 opened by manikanta9176
Description:
Implement a Redis-based caching layer for storing server details in dFlow. The cache should automatically revalidate when:
This will reduce database queries, speed up UI/API responses, and keep data fresh without manual cache resets.
Acceptance Criteria:
Benefits:
#414 opened by charanm927
Description:
Enable dFlow to connect databases hosted on separate servers via Tailnet (Tailscale network). By default, create all user databases on dFlow-managed servers and connect services to them securely using Tailnet. This approach improves security, performance, and simplifies DB networking without exposing databases to the public internet.
Acceptance Criteria:
Benefits:
#413 opened by charanm927
Description:
Extend dFlow to support provisioning and managing external databases from popular hosted providers, allowing users to install and connect their databases outside dFlow-managed servers. This will give users flexibility in choosing specialized DB hosting while still integrating fully with their dFlow projects.
Acceptance Criteria:
Benefits:
#412 opened by charanm927
Description:
Move the dFlow marketing website from its current hosting setup to run entirely on the dFlow App infrastructure. This will consolidate hosting, simplify deployment workflows, and allow us to manage the marketing site using the same platform as other dFlow projects.
Acceptance Criteria:
Benefits:
#411 opened by charanm927
Description:
Migrate all previous projects hosted on Railway to dFlow by creating and using a dedicated ContenQL account. This migration should ensure all project configurations, environment variables, and services are replicated in dFlow while maintaining service availability during the transition.
Acceptance Criteria:
Benefits:
#410 opened by charanm927
Description:
Create a migration script that allows users to seamlessly move their existing projects from Railway to any dFlow instance (cloud or self-hosted). The script should fetch project configurations, environment variables, and service definitions from Railway, then recreate them in dFlow with minimal manual input.
Acceptance Criteria:
Benefits:
#409 opened by charanm927
Description:
Add functionality to migrate databases (internal or external) from one server to another within dFlow. This will help teams move workloads, scale infrastructure, and perform maintenance without manual DB export/import steps.
Acceptance Criteria:
Benefits:
#408 opened by charanm927
Description:
Add the ability to configure and run backups for external databases connected to dFlow projects. This will allow teams to securely back up MySQL, PostgreSQL, MongoDB, and other external DB instances to supported storage providers (S3, Backblaze, etc.) without relying on server-level scripts.
Acceptance Criteria:
Benefits:
#407 opened by charanm927
Description:
Add automated and on-demand cleanup tools for Docker, Dokku, and dFlow resources to free up space, remove unused data, and maintain optimal server performance. This will help prevent bloated environments and reduce potential deployment issues.
Acceptance Criteria:
Docker Cleanup:
Dokku Cleanup:
dFlow Cleanup:
Benefits:
#405 opened by charanm927
Description: Integrate Ansible-based configuration management into dFlow to standardize and automate server setup, deployment tasks, and environment consistency. This will help ensure reproducible environments across all servers and reduce manual configuration errors.
Acceptance Criteria:
Benefits:
#401 opened by charanm927
Currently, the default monitoring in the project does not include any alerting mechanism. To improve system reliability and user awareness, add alert functionalities to the default monitoring setup.
This feature will help users proactively manage their workflows and maintain system health by providing visibility to Beszel alerts.
#390 opened by manikanta9176
Create a centralized JSON file that defines and fixes the versions of all third-party packages used across the project, including beszel (hub and agent), netdata, dokku, buildkit, railpack, dokku plugins, and others.
Managing package versions manually can lead to inconsistencies and unexpected behavior across servers. A single JSON file will allow us to:
This feature will provide greater reliability and efficiency for both maintainers and users when updating server environments.
Packages to include (not exhaustive):
Please discuss additional package candidates and implementation details as needed.
#387 opened by manikanta9176
#384 opened by pavanbhaskardev