Dokploy / Dokploy/dokploy

[Feature Request] Show usage example for File Mounts created in the UI

Open Beginner friendly
#5,147 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What problem will this feature address?

When creating a File Mount in the Advanced-UI, the file is stored in the services files directory. However, the UI does not show how this file should be referenced from a custom docker-compose.yml.

For example, after creating a File Mount named Caddyfile, it is not obvious that the compose entry needs to reference:

../files/Caddyfile:/etc/caddy/Caddyfile

instead of:

./Caddyfile:/etc/caddy/Caddyfile
Describe the solution you'd like

A small hint in the File Mount dialog showing the generated path and an example volume entry would make this feature much easier to discover.

Something like:

File location:
../files/Caddyfile

docker-compose example:
../files/Caddyfile:/etc/caddy/Caddyfile

would likely prevent confusion, especially since the normal Docker Compose pattern is to use relative paths from the compose file directory.

Describe alternatives you've considered

The docs clearly state that you have to use ../files/<FILENAME>, though I think it should not be necessary to read through the docs when a usage hint would clear things up immediately.

Additional context

Thanks for developing Dokploy! I really like it :)

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

Start by locating the Advanced-UI File Mount dialog and trace how the generated file name is available there. Done means the dialog shows the generated ../files/ location and a docker-compose volume example, such as ../files/Caddyfile:/etc/caddy/Caddyfile.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, typescript
Domain
devops, frontend
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.