Linux Standards Violation: Incorrect Storage of Docker Volumes and Logs

To Reproduce

Description

Dokploy is storing Docker volumes and logs in the /etc/dokploy directory, which is a violation of Linux standards. Specifically, the directories /etc/dokploy/compose and /etc/dokploy/logs are used for storage, which is not in compliance with the Linux Filesystem Hierarchy Standard (FHS).

Proposal:

Update Dokploy to store Docker volumes in a directory like /var/lib/docker or a dedicated data directory.
Move logs to /var/log/dokploy or a similar directory.
Update the Dokploy configuration to reflect the new storage locations.
Rationale:

Adhering to Linux standards ensures that Dokploy integrates seamlessly with the Linux ecosystem and follows best practices for system administration. This change will also improve the overall structure and organization of the Dokploy project.

Steps to Reproduce:

• Install and run Dokploy on a Linux system.
• Verify that Docker volumes are stored in /etc/dokploy/compose and logs are stored in /etc/dokploy/logs.

Current vs. Expected behavior

Expected Behavior:

According to the FHS, /etc should only contain system configuration files, not data or logs. Docker volumes should be stored in a directory like /var/lib/docker or a dedicated data directory, and logs should be stored in /var/log.

Actual Behavior:

The current implementation of Dokploy stores Docker volumes in /etc/dokploy/compose and logs in /etc/dokploy/logs, which is not compliant with the FHS.

Provide environment information

Operating System: all linux
Dokploy version: all versions

Which area(s) are affected? (Select all that apply)

Installation, Application

Additional context

This issue is important for maintaining a clean and organized file system, adhering to established standards, and ensuring a better user experience.

i.e. It's best practices to keep the /etc/ in a git repo (pkg: etckeeper), which would have to digest userdata (volumes) & and logs which definitly do not belong there.

Start by locating the configuration and installation entry points that create or reference /etc/dokploy/compose and /etc/dokploy/logs. Trace how Docker volumes and logs are handled, including any configuration that depends on these paths. Done means data is stored under an appropriate data directory, logs under /var/log/dokploy or similar, and all references are updated without breaking installation or application behavior.