- 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.
- Added sections on Docker Swarm and registry-based rollback mechanisms, explaining their functionalities and differences.
- Included prerequisites and steps for enabling registry-based rollbacks, enhancing user control over application versions.
- Improved clarity with callouts emphasizing important considerations for both rollback methods.
- Updated the structure to provide a comprehensive guide for users on managing application rollbacks effectively.
- Standardized import statements across various components to use double quotes for consistency.
- Updated component files to ensure proper formatting and adherence to coding standards.
- Enhanced overall code readability by aligning code structure and improving comment clarity.
- Made minor adjustments to ensure all components follow the same coding conventions, improving maintainability.
- Added a new SearchDialog component to enhance user experience for searching documentation.
- Updated the layout to include the SearchDialog within the RootProvider for improved accessibility.
- Enhanced the search API to support tag filtering based on the first slug, allowing for more refined search results.
- Added a new section on securing servers with UFW (Uncomplicated Firewall) after Tailscale setup.
- Included detailed steps for enabling UFW, configuring default rules, and allowing Tailscale traffic.
- Emphasized the importance of verifying SSH access over Tailscale before restricting public access.
- Provided warnings about Docker's interaction with UFW and recommended solutions for maintaining security.
- Introduced a new guide on using Tailscale to securely access Dokploy applications and servers through a private network.
- Updated meta.json to include the new Tailscale guide in the documentation structure.
- The guide covers setup, configuration, and security benefits of using Tailscale, emphasizing zero-config VPN features and private service access.
- Added commands for using specific Dokploy versions with curl and bash, enhancing clarity on installation options.
- Updated the install.sh script comments to reflect new usage instructions for setting the DOKPLOY_VERSION environment variable.
- Revised the description for the API documentation to specify it as a RESTful API reference for programmatic access to Dokploy.
- Updated the CLI documentation description to clarify it as a command-line interface for managing Dokploy from the terminal.
- Enhanced the Core documentation description to provide essential guides for deploying and managing applications, databases, and server configurations.
- Added important notes regarding the use of Docker named volumes for volume backups, clarifying that bind mounts are not supported.
- Updated the Docker Compose section to differentiate between bind mounts and named volumes, including guidance on when to use each method.
- Included a comparison table to help users choose the appropriate volume method based on their needs.
- Enhanced callouts to emphasize the implications of using bind mounts versus named volumes for data persistence and backup functionality.
- Introduced a new webhook notification provider in the meta.json file.
- Updated the overview documentation to include webhook notifications as a supported method.
- Created a detailed guide for configuring and testing webhook notifications, including JSON payload examples and production setup recommendations.
- Updated the permissions section to define three distinct user roles: Owner, Admin, and Members, each with specific capabilities and limitations.
- Enhanced the description of permissions available to Members, detailing actions they can perform.
- Improved clarity on project permissions and the ability to assign access at the environment level for granular control.
- Enhanced the schedule jobs section to clarify the execution context for Server and Dokploy Server Jobs, emphasizing their interaction with Docker commands.
- Introduced a new Lark notifications guide, detailing setup steps and configuration for receiving notifications in the Dokploy panel.
- Updated the overview of notification providers to include Lark, ensuring comprehensive coverage of available options.
- Introduced a new section detailing the use of external build servers for application compilation and deployment.
- Explained the benefits of using build servers, including resource optimization and isolation from production environments.
- Provided a step-by-step overview of the build, push, and deploy phases when using a custom build server.
- Added important callouts regarding the limitations and required configurations for using build servers.
- Introduced a new section detailing the configuration of build time arguments and build-time secrets for Dockerfile builds.
- Explained the importance of using build-time secrets for sensitive information and provided links to relevant Docker documentation.
- Added a callout emphasizing best practices for handling sensitive data during the build process.
- Added a new section explaining how Dokploy automatically adds Traefik labels to Docker Compose files during deployment.
- Included example Docker Compose configurations to illustrate the default and final states after domain configuration.
- Highlighted the functionality of the Preview Compose feature for users to verify modifications before deployment.
- Emphasized important notes regarding domain settings and their impact on deployment behavior.
- Introduced a comprehensive guide on how domains are managed differently for Applications and Docker Compose.
- Included specific configurations for each method, highlighting key points such as redeployment requirements and hot reloading capabilities.
- Added YAML examples for Applications and outlined the use of Traefik Docker Labels for Docker Compose, enhancing user understanding of domain configurations.
- Clarified the functionality of Isolated Deployments, emphasizing automatic network handling.
- Added a warning callout regarding installation type considerations for custom installations, detailing potential issues after system restarts and the need for manual redeployment.
- Enhanced the Randomize Compose section with important notes on system restart implications and recommended approaches for different installation types.
- Added a new section for troubleshooting in meta.json to improve user navigation.
- Expanded the Docker Compose documentation to include two methods for domain configuration: using Dokploy Domains (recommended) and manual configuration with Traefik labels.
- Included detailed steps and callouts for both methods, emphasizing best practices and important considerations for users.
- Updated the example tutorial to clarify the manual configuration process and highlight Docker Stack requirements.
- Added detailed descriptions for two types of remote servers: Deployment Servers and Build Servers.
- Included functionalities and benefits of each server type to enhance user understanding.
- Clarified the configuration process for using build servers in application settings.
- Introduced a new guide for configuring a custom build server, detailing the setup process, prerequisites, and usage.
- Updated meta.json to include the new build server documentation entry, enhancing the overall structure of the remote servers section.
- Renamed the existing instructions file to better reflect its focus on deployment servers.
- Expanded the documentation on managing memory and CPU resources for applications, including detailed explanations of memory and CPU limits and reservations.
- Added user-friendly examples and formats for input values, ensuring clarity on how to set resource constraints.
- Included important reminders regarding the relationship between memory and CPU reservations and limits.
- Updated the file mount description to clarify its persistence across deployments.
- Introduced a new meta.json file to structure the Applications documentation.
- Included pages for advanced topics, build types, preview deployments, rollbacks, zero downtime, and going production.
- Introduced comprehensive guides for setting up Cloudflare Tunnels and deploying applications on AWS EC2.
- Updated meta.json to include new guide entries, enhancing the documentation structure.
- Removed outdated EC2 instructions to streamline content and improve clarity.
- Changed the title of the remote servers documentation from 'Remote Servers' to 'Introduction' for better clarity.
- Removed an unnecessary entry from the meta.json file to streamline the documentation structure.
- Updated the comparison table to reflect support for Cloudflare Tunnels and added Custom Build Server.
- Enhanced the description in the remote server instructions for clarity and detail.
- Updated the package name from 'docs-new' to 'docs' in apps/docs/package.json.
- Removed obsolete scripts related to 'docs-new' from the root package.json to streamline the documentation setup.
- Enhanced API documentation with new MDX files and improved structure.
- Updated OpenAPI specifications to reflect recent changes and added new components.
- Refined global CSS and layout configurations for better styling and user experience.
- Added various images and icons to enrich the visual aspects of the documentation.
- Updated package dependencies to ensure compatibility with the latest features.
- Upgraded Next.js from 15.0.3 to 16.0.7 in apps/docs and apps/website.
- Updated @next/third-parties from 15.4.5 to 16.0.7 in both apps.
- Adjusted related dependencies to ensure compatibility with the new Next.js version.
- Added a new section detailing the required ports (80, 443, and 3000) for Dokploy installation.
- Included a warning about the necessity of ensuring these ports are free before installation to prevent errors.
- Introduced guidance on resolving 404 errors related to Traefik routing for services created from templates and Docker Compose.
- Explained the differences in routing configuration between Applications and Templates/Compose Services.
- Provided a step-by-step solution for configuring domains and redeploying services to ensure changes take effect.
- Updated the section on securing the installation by enabling HTTPS, including a reference to the Domains documentation for SSL/TLS configuration.
- Added a warning about the importance of having a working domain with HTTPS before disabling IP:port access.
- Clarified the steps to disable IP:port access after verifying domain functionality.
- Updated various files to ensure consistent code formatting, including adjusting indentation and spacing.
- Refactored components and utility functions for better readability and maintainability.
- Removed unnecessary newlines and ensured consistent use of single quotes for strings across the codebase.
- Introduced a new script to fix OpenAPI schema issues, including adding a missing Authorization security scheme and addressing empty response schemas.
- Updated the build process to run this script before generating documentation, ensuring a more robust and accurate OpenAPI specification.
- Deleted multiple outdated API documentation files to streamline the documentation structure.
- This cleanup aligns with recent efforts to maintain an organized and efficient documentation system.
- Copied openapi.json to the docs public folder for easier access.
- Updated paths in generated documentation files to reference the new location of openapi.json.
- Ensured all references to openapi.json are consistent across documentation files.
