feat: migration to fumadocs 14

apps/docs-v2/content/docs/core/databases/backups.mdx

@@ -0,0 +1,26 @@
+---
+title: Backups
+description: "Learn how to schedule and manage backups for your databases in Dokploy, with options for storage in S3 buckets."
+---
+
+Dokploy provides an integrated solution for backing up your databases, ensuring data safety and recovery capabilities.
+
+## Backing Up Your Database
+
+To configure database backups, navigate to the `Backup` tab within your Dokploy dashboard. Here’s what you’ll need to set up:
+
+- **Select Destination S3 Bucket**: Specify where your backups will be stored. Buckets can be configured in the `/dashboard/settings/destinations` route.
+- **Database Name**: Enter the name of the database you want to backup.
+- **Schedule Cron**: Define the schedule for your backups using cron syntax.
+- **Prefix**: Choose a prefix under which backups will be stored in your bucket.
+- **Enabled**: Toggle whether backups are active. The default setting is enabled.
+
+### Testing Your Backup Configuration
+
+To ensure your backup settings are correctly configured:
+
+1. Click the `Test` button.
+2. This will initiate a test backup to the S3 bucket you selected.
+3. Check the bucket to see the result of the test backup.
+
+This feature provides peace of mind by verifying that your backup process is set up correctly before relying on it for operational backups.

apps/docs-v2/content/docs/core/databases/connection.mdx

@@ -0,0 +1,33 @@
+---
+title: Connection
+description: "Learn how to connect to your database using Dokploy."
+---
+
+This section explains how to configure database access for applications in Dokploy, including both internal connections within your network and external connections accessible over the internet.
+
+### Internal Credentials
+
+ Used for connecting to the database from within the same network, without exposing the database to the internet.
+
+- **User**: Username for the database access.
+- **Password**: Secure password for database access.
+- **Database Name**: The name of the database to connect to.
+- **Internal Host**: The hostname or internal identifier for the database within the network.
+- **Internal Port (Container)**: The port used within the container to connect to the database.
+- **Internal Connection URL**: The full connection string used internally to connect to the database.
+
+### External Credentials
+
+Enables the database to be reachable from the internet, necessary for remote management or external applications.
+
+- **External Port (Internet)**: Assign a port that is not currently used by another service to expose the database externally.
+  
+#### Steps to Configure External Access
+1. Ensure the external port is available and not in conflict with other services.
+2. Enter the external port you wish to use to expose your database.
+3. The system will automatically generate an external connection URL, which can be used to access the database from any database management tool over the internet, like phpMyAdmin, MySQL Workbench, PgAdmin, etc.
+
+### Important Note
+
+For security reasons, internal credentials should be used for applications running within the same network or environment to prevent unauthorized access. External credentials should only be used when necessary and with proper security measures in place, such as VPNs or IP whitelisting.
+

apps/docs-v2/content/docs/core/databases/index.mdx

@@ -0,0 +1,51 @@
+---
+title: Databases
+description: "Discover how to create and backup databases easily with Dokploy, supporting a variety of database systems."
+---
+
+Dokploy simplifies the process of creating and managing databases, offering robust options for both setup and backups.
+
+## Database Support
+
+Dokploy currently supports a range of popular database systems, ensuring compatibility and flexibility for your projects:
+
+- **Postgres**: Robust, SQL-compliant and highly reliable.
+- **MySQL**: Widely used relational database known for its performance and flexibility.
+- **MariaDB**: A fork of MySQL with additional features and improved performance.
+- **MongoDB**: A NoSQL database known for its high scalability and flexibility.
+- **Redis**: An in-memory key-value store often used as a database, cache, and message broker.
+
+
+We offer multiple functionalities that you can use to manage your databases, such as:
+
+## General
+
+Actions like deploying, updating, and deleting your database, and stopping it.
+
+## Environment
+
+If you need to assign environment variables to your application, you can do so here.
+
+In case you need to use a multiline variable, you can wrap it in double quotes just like this `'"here_is_my_private_key"'`.
+
+## Monitoring
+
+Four graphs will be displayed for the use of memory, CPU, disk, and network. Note that the information is only updated if you are viewing the current page, otherwise it will not be updated.
+
+## Backups
+
+We offer automated backups for your databases, ensuring that you can recover your data quickly and easily in case of any issues, you can setup a S3 Destinations in settings to store your backups.
+
+
+## Logs
+
+If you want to see any important logs from your application that is running, you can do so here and determine if your application is displaying any errors or not.
+
+## Advanced
+
+This section provides advanced configuration options for experienced users. It includes tools for custom commands within the container, managing Docker Swarm settings, and adjusting cluster settings such as replicas and registry selection. These tools are typically not required for standard application deployment and are intended for complex management and troubleshooting tasks.
+
+- **Custom Docker Image**: You can change the Docker image used to run your database.
+- **Run Command**: Execute custom commands directly in the container for advanced management or troubleshooting.
+- **Volumes**: To ensure data persistence across deployments, configure storage volumes for your application.
+- **Resources**: Adjust the CPU and memory allocation for your application.