Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add `.dokploy.json` local project config to skip interactive prompts

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
cli

Research direction

Start by tracing how dokploy init, app deploy, and env pull currently obtain projectId, environmentId, and applicationId from flags or interactive selection. Implement the proposed .dokploy.json lookup and flag precedence, then verify that init creates the file and existing commands avoid prompts when its values are present.

Written by the indexing model from the issue text.

Description

Currently every command requires either passing --projectId/--environmentId/--applicationId flags or going through interactive selection each time. It would be useful to have a per-directory config file that stores these defaults.

Proposed feature

A .dokploy.json file that can be placed in any project directory:

{
  "projectId": "abc123",
  "environmentId": "def456",
  "applicationId": "ghi789"
}

A new dokploy init command to create it interactively, and all existing commands would read this file (walking up parent directories) to fill in missing flags before prompting.

Example usage

$ cd ~/my-app
$ dokploy init              # select project/environment/app once
$ dokploy app deploy -y     # no prompts needed
$ dokploy env pull .env     # knows which project/environment to use

CLI flags would always take priority over .dokploy.json values.

Dominant language
TypeScript
Stars
152
Forks
46
PR merge metrics
No merged PRs in 30d

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.

More from Dokploy/cli

All issues in Dokploy/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.