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.
Currently every command requires either passing
--projectId/--environmentId/--applicationIdflags 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.jsonfile that can be placed in any project directory:{ "projectId": "abc123", "environmentId": "def456", "applicationId": "ghi789" }A new
dokploy initcommand 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
CLI flags would always take priority over
.dokploy.jsonvalues.