Go to file
Mauricio Siu 1e9e51f9fe
Some checks failed
Build Docker images / build-and-push-image-docs (push) Has been cancelled
Build Docker images / build-and-push-image-website (push) Has been cancelled
docs: add manual rollback feature instructions to deployment documentation
2025-06-22 09:17:20 -06:00
.github chore: remove husky integration and related scripts from the project 2025-04-17 16:44:11 -06:00
apps docs: add manual rollback feature instructions to deployment documentation 2025-06-22 09:17:20 -06:00
.dockerignore feat: add monorepo 2024-10-27 22:16:31 -06:00
.gitignore feat: add monorepo 2024-10-27 22:16:31 -06:00
.nvmrc feat: add monorepo 2024-10-27 22:16:31 -06:00
biome.json feat: migration to fumadocs 14 2024-11-09 21:15:20 -06:00
Dockerfile.docs refactor: update node 2025-02-02 21:57:11 -06:00
Dockerfile.website refactor: update node 2025-02-02 21:57:11 -06:00
filestructure.txt feat(i18n): add Spanish language support and update language selector components 2025-04-29 17:31:24 +02:00
LICENSE.MD feat: add monorepo 2024-10-27 22:16:31 -06:00
package.json chore: remove husky integration and related scripts from the project 2025-04-17 16:44:11 -06:00
pnpm-lock.yaml chore: remove husky integration and related scripts from the project 2025-04-17 16:44:11 -06:00
pnpm-workspace.yaml feat: migration to fumadocs 14 2024-11-09 21:15:20 -06:00
README.md Merge pull request #45 from pompydev/spelling 2025-06-20 06:52:21 +02:00

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 src or test files
  • revert: Reverts a previous commit

Example:

feat: add new feature

Pull Request

  • The main branch 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