mirror of
https://github.com/Dokploy/website.git
synced 2026-07-07 23:15:30 +02:00
4bca945f3c
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>
Contributing
Hey, thanks for your interest in contributing to Dokploy! We appreciate your help and taking your time to contribute.
Before you start, please first discuss the feature/bug you want to add with the owners and community via github issues.
We have a few guidelines to follow when contributing to this project:
Commit Convention
Before you create a Pull Request, please make sure your commit message follows the Conventional Commits specification.
Commit Message Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Type
Must be one of the following:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- chore: Other changes that don't modify
srcortestfiles - revert: Reverts a previous commit
Example:
feat: add new feature
Pull Request
- The
mainbranch is the source of truth and should always reflect the latest stable release. - Create a new branch for each feature or bug fix.
- Make sure to add tests for your changes.
- Make sure to update the documentation for any changes Go to the docs.dokploy.com website to see the changes.
- When creating a pull request, please provide a clear and concise description of the changes made.
- If you include a video or screenshot, would be awesome so we can see the changes in action.
- If your pull request fixes an open issue, please reference the issue in the pull request description.
- Once your pull request is merged, you will be automatically added as a contributor to the project.
Thank you for your contribution!
Docs
To run the docs locally, run the following command:
pnpm run docs:dev
To build the docs, run the following command:
pnpm run docs:build
Website
To run the website locally, run the following command:
pnpm run website:dev
To build the website, run the following command:
pnpm run website:build