Applies the Dokku column corrections proposed by @josegonzalez in #108,
with Preview Deployments marked "Via GitHub Action" since review apps
are set up through Dokku's GitHub Action rather than built in.
The Existing Docker Swarm section only created the network and the dokploy
service, so installs failed against current versions that require the
dokploy_postgres_password and dokploy_auth_secret Docker secrets, the
dokploy-postgres service, and Traefik (issue #111). It now mirrors what
install.sh does today, minus the swarm re-initialization.
Also remove the ADVERTISE_ADDR env passed to the dokploy service in
install.sh and the docs: the app stopped reading process.env.ADVERTISE_ADDR
in February 2025, and the private-IP lookup step in troubleshooting only
existed to fill it. The recreate-service commands now also mount the auth
secret so recreated instances don't fall back to the insecure hardcoded
default, and the advertise-addr customization section documents the
ADVERTISE_ADDR env override instead of a script line that no longer exists.
The docs instruct 'curl -sSL https://dokploy.com/install.sh | sh', but on
Debian/Ubuntu sh is dash, which has no [[ or =~. The RELEASE_TAG detection
failed with 'sh: 264: [[: not found' and, since the script does not run
with set -e, silently fell through to the elif branch, so stable installs
via sh got RELEASE_TAG=<version> instead of RELEASE_TAG=latest.
Replace the bash-only test with a POSIX case statement. Verified end-to-end
on Ubuntu 20.04/24.04 and Debian 12 (dash), Alpine 3.20 (busybox ash), and
Rocky 9 / Fedora 41 (bash as sh), including the canary, latest and update
code paths. Both '| sh' and '| bash' now work.
Fixes#157
Home servers and local VMs are often not reachable on their public IP
because no port forwarding is configured, so the final install message
now also prints the private (RFC1918) IP when one is detected and it
differs from the address already shown.
Closes#152
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Documents the fix for builds and domain validation failing with DNS
errors when the provider's default resolvers misbehave inside Docker
containers (reported in Dokploy/website#146 and Dokploy/dokploy#3981).
When the GitHub request fails (unreachable network, rate limiting — common
on Proxmox homelab VMs with broken IPv6/DNS), curl -f fails but -w still
prints the attempted URL, so detect_version() returned
"https://github.com/dokploy/dokploy/releases/latest" instead of a tag.
The resulting invalid image (dokploy/dokploy:https://...) meant the dokploy
service was never created, traefik.yml was never written, and the bind
mount created it as a directory.
Accept only values that look like a release tag (v0.x.y), falling back to
"latest" otherwise, and add --connect-timeout 10 so blackholed networks
fail over in seconds instead of hanging the install.
Verified on debian:13 containers: normal network detects v0.29.10, the
DOKPLOY_VERSION override is intact, and connection-refused or blackholed
github.com now falls back to "latest" within 10s.
Fixes#126
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The install script's get_private_ip() fallback picked the first RFC1918
address from `ip addr show`, which matches the docker0 bridge (172.17.0.1)
when Docker is already installed — an address other swarm nodes can never
reach. Exclude docker0/br-*/veth* interfaces so a real host/VPN interface
wins, and fall back to the public IP when no private interface exists
(e.g. servers with only a public IP).
Verified end-to-end in Ubuntu 24.04 and Debian 13 containers (Docker
pre-installed, WireGuard-like interface, public IP on eth0), plus the
detection logic on Debian 12, AlmaLinux 9, Fedora 44 and openSUSE Leap 15.6.
Fixes#153
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Clarified instructions for setting the ADVERTISE_ADDR variable when running the installation script with sudo, emphasizing the need to pass the variable inline.
- Added warnings in the installation and troubleshooting sections to prevent confusion regarding environment variable handling with sudo.
The docs claimed the Command field appends to the default command, but
createCommand in dokploy fully replaces it with the custom command.
Update both pages to describe the override behavior.
Fixes#142
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Added instructions for installing a specific version of Dokploy using the release asset `install.sh`, emphasizing this as the recommended method for older versions.
- Included a note highlighting potential compatibility issues with the latest installation script for older versions.
- Updated the architecture documentation to reflect the removal of Redis from the Dokploy setup, ensuring accuracy in the description of the system components.
- Updated the architecture documentation to reflect the removal of the Redis database from the Dokploy setup.
- Modified the manual installation guide to eliminate Redis configuration instructions.
- Adjusted troubleshooting documentation to indicate that only three containers should be running, following the removal of Redis.
- Cleaned up the installation script by removing Redis service creation commands.
- Added a check to ensure `apt-mark` is available before holding Docker packages to prevent unintended upgrades.
- Removed the Docker version update logic from the `update_dokploy` function to streamline the installation process and avoid unnecessary complexity.
- Expanded the description of Enterprise features to include Application Authentication and Unlimited Concurrent Builds, enhancing clarity and detail.
- Added links to specific documentation sections for SSO, Custom Roles, Audit Logs, Whitelabeling, and the new features, improving navigation and user experience.
- Updated images related to the Enterprise features to ensure visual consistency and support the new content.
- Revised the "Differences" section to clarify the operational distinctions between Dokploy editions and introduced a comprehensive table summarizing features across Self-Hosted and Cloud options.
- Added a new section in the "Enterprise" documentation outlining the two flavors of Enterprise offerings, detailing their features and operational differences.
- Enhanced the overall structure and clarity of the documentation to improve user understanding of Dokploy's offerings.
- Added detailed sections for Enterprise features including SSO, Custom Roles, Whitelabeling, and Audit Logs, each with descriptive text and accompanying images for better understanding.
- Introduced new images to visually represent the configuration settings for these features, improving the overall documentation quality.
- Updated the existing documentation to include links and references to the new content, ensuring comprehensive coverage of Enterprise capabilities.
- Introduced a new documentation page titled "Interface Overview" that provides a visual tour of the Dokploy dashboard, including detailed descriptions and screenshots of major sections such as Home, Projects, Applications, Databases, and more.
- Updated meta.json to include the new "interface-overview" entry for improved navigation.
- Added multiple new images to enhance the visual representation of the dashboard features.
- Replaced outdated images with new ones for Dokploy's deployment logs, monitoring dashboards, and project management features in the comparison pages against CapRover, Coolify, Dokku, Portainer, Render, and Vercel.
- Updated alt text for images to better reflect their content and improve accessibility.
- Enhanced the visual representation of Dokploy's capabilities in industry-specific contexts, ensuring consistency across all comparison pages.
- Updated the sitemap to include new industry comparison pages for Dokploy, covering sectors such as finance, healthcare, manufacturing, and pharmaceuticals.
- Introduced new industry-specific pages detailing deployment solutions tailored for agencies, finance, healthcare, manufacturing, and pharmaceuticals.
- Enhanced the footer and header navigation to include links to the new industry pages for improved user access.
- Introduced a new comparison page detailing the differences between Dokploy and Vercel, including features, pricing, and integration options.
- Updated the competitors list to include Vercel.
- Added a link to the new comparison page in the footer for improved navigation.
- Introduced a new page comparing Dokploy and Render, highlighting key features, pricing, and integration options.
- Updated the comparison section to include Render as a competitor.
- Added a link to the new comparison page in the footer for easy navigation.
- Introduced a new documentation page for Application Authentication, detailing how to protect deployed applications with SSO using oauth2-proxy and Traefik.
- Updated the main SSO index to link to the new Application Authentication section.
- Modified meta.json to include "application-authentication" for navigation purposes.
- Introduced a new section on how Dokploy manages build and deployment concurrency per server, including configuration details and limits based on the plan.
- Updated meta.json to include the new "concurrent-builds" entry for navigation.
