Dokploy / Dokploy/dokploy

Who's Using Dokploy? Share Your Story!

Open
#1,946 19 comments 20 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Hey everyone,

We're always looking to improve Dokploy and make it the best deployment tool out there. A huge part of that is understanding who's using Dokploy and how it's helping you. We'd love to hear your experiences, learn about your projects, and get your valuable insights!

If you're using Dokploy, please consider sharing a bit about your setup and journey in the comments below. It's incredibly helpful for us and also a cool way for the community to see what everyone's building!

Tell Us About Your Dokploy Setup:

To help us get a clear picture, please try to answer these questions:

  1. What were you using before Dokploy? (e.g., direct SSH, other CI/CD tools, vercel, heroku, manual deployments, etc.)
  2. Roughly how many services have you created with Dokploy? (e.g., 5-10, 20+, 1-2, etc.)
  3. Your Business/Project:
  • Name: (e.g., "My Awesome App," "Creative Solutions LLC")
  • Link: (Optional, but great if you want to share!)
  • Brief Description: What does your service/business do?
  • Contact: (e.g., GitHub handle, email, Twitter)
  1. What's your favorite thing about Dokploy right now?
  2. What do you think Dokploy needs to become a true "all-in-one" tool for you? (Be specific!)
  3. Share your setup: If you use physical servers and want to share some images that would be great).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Read the 19-comment thread first to understand the responses and expectations; completion is not defined beyond collecting user stories and feedback in the comments.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.