- Added advanced installation options for specifying versions and custom network configurations in the installation documentation.
- Updated the manual installation guide to include secure password generation for PostgreSQL using Docker Secrets.
- Included Proxmox LXC considerations and emphasized the use of Docker Secrets for managing sensitive data.
- Improved troubleshooting section with detailed steps for recreating services and managing environment variables.
- Modified the command to alter the PostgreSQL user password in the security script to use the 'dokploy' user with the database specified, enhancing security by utilizing Docker Secrets for password management.
- Changed the PostgreSQL user command in the security script to use the 'postgres' user instead of 'dokploy' for password updates, ensuring proper permissions during execution.
- Removed output redirection from the PostgreSQL user password update command in the security migration script to ensure visibility of potential errors during execution.
- Removed the POSTGRES_PASSWORD environment variable from the Docker service update command to enhance security by relying solely on Docker Secrets for password management.
- Introduced a new Bash script for configuring secure database credentials in Dokploy installations.
- The script generates a random password, checks for existing configurations, and updates the PostgreSQL and Dokploy services to use Docker Secrets for enhanced security.
https://github.com/Dokploy/dokploy/issues/3449
- Updated version detection logic to fetch the latest stable version from GitHub if no version is specified.
- Improved usage instructions for clarity regarding version options.
- Added $endpoint_mode to dokploy-postgres service creation
- Added $endpoint_mode to dokploy-redis service creation
- Updated warning message to reflect services (plural) instead of service (singular)
- Ensures all Docker services work correctly in LXC containers with dnsrr endpoint mode
Co-authored-by: Siumauricio <47042324+Siumauricio@users.noreply.github.com>
- Upgraded @types/react and @types/react-dom to version 19.2.2 in package.json and pnpm-lock.yaml.
- Updated React and React-DOM versions to ^19.2.0 in apps/website/package.json.
- Adjusted hast-util-to-jsx-runtime version to ^3.20.0 in apps/website/package.json.
- Refactored CodeBlock component to simplify code formatting and highlighting logic.
- Modified shared component to use updated imports for React and JSX runtime.
- Replaced the deprecated 'domains' property with 'remotePatterns' in the Next.js configuration for image handling.
- Adjusted the margin of the blog post link to improve layout consistency.
- Included a callout in the Docker Compose documentation to inform users about the necessity of the `--with-registry-auth` flag when deploying with Docker Stack and private registries.
- Explained the implications of not using the flag, including potential authentication errors on worker nodes. Resolved https://github.com/Dokploy/dokploy/issues/3111
- Removed 'other' option from inquiryType in ContactFormData interfaces across contact form and API.
- Updated email recipient logic to use a single variable for clarity.
- Adjusted related components to reflect the changes in inquiryType options.
- Updated Next.js version from 16.0.8 to 16.0.10 in apps/docs/package.json and apps/website/package.json.
- Adjusted related dependencies in pnpm-lock.yaml to reflect the new version.
- Revised the Privacy Policy to include detailed information on data collection, usage, and user rights.
- Added a link to the Privacy Policy in the footer navigation for improved accessibility.
- Introduced a Callout component to highlight the critical security issue of Docker bypassing UFW firewall rules.
- Provided solutions for integrating Docker with UFW and configuring cloud provider firewalls for enhanced security.
- Introduced a Callout component to highlight the importance of manual storage cleanup for workers and associated nodes in Dokploy.
- Provided guidance on configuring remote servers for automatic cleanup and clarified that no setup is needed when adding a node as a remote server. https://github.com/Dokploy/dokploy/issues/3195
- Added a note regarding the necessity of including `dokploy-network` in all services when not using Isolated Deployments to ensure connectivity.
- Enhanced the documentation to provide clearer guidance on network configurations in Docker Compose setups.
- Changed the link and description in the core documentation to focus on Docker Compose instead of Traefik.
- Updated the content to provide guidance on using Docker Compose with Dokploy.
- Temporarily disabled the Slack notification feature in the contact form submission process.
- Retained the structure for potential future reactivation while ensuring email notifications remain functional.
- Added a new Slack notification feature to alert sales or support channels upon contact form submissions.
- Implemented a `notifySlack` function to format and send messages to Slack using a webhook.
- Enhanced error handling to ensure email notifications proceed even if Slack notifications fail.
- Introduced a new ContactForm component to streamline user inquiries with validation and submission handling.
- Added ContactFormModal to encapsulate the contact form in a modal dialog, enhancing user experience.
- Updated the Pricing component to include a button that opens the contact modal for enterprise inquiries.
- Refactored the ContactPage to utilize the new ContactForm component, simplifying the code and improving maintainability.
- Updated TypeScript configuration to include additional type definitions for better type safety.
- Included a new environment variable, TZ, for setting the timezone in Dokploy installations.
- Added a section detailing how to update the timezone using a Docker command, enhancing user guidance for server configuration.
Fix this question https://github.com/Dokploy/dokploy/issues/2688
- Included a new 'goodies' entry in the meta.json file to enhance the organization of documentation topics.
- This addition aims to streamline user navigation and access to relevant resources within the documentation.
- Changed development server ports for both the docs and website applications to avoid conflicts.
- Expanded the Railpack documentation to include a section on specifying the Railpack version, detailing how to pin, upgrade, or maintain stable versions for consistent builds.
- Added a callout for invalid version specifications to improve user guidance.
- Expanded the validation section for Deployment and Build Servers, detailing specific components required for each server type.
- Added callouts to clarify the roles of Deployment and Build Servers, emphasizing their distinct configurations and functionalities.
- Improved overall structure and clarity of the validation process, ensuring users understand the prerequisites for successful server setup.
