Feature Description
Saved failed launch errors per project in the logs section of said project.
Problem It Solves
The one thing I miss coming from Dockge is the ability to see the reason a compose stack has failed to start. I don't believe there is anything past the error notification. Currently I have to SSH into my server and manually run docker compose up to see the errors, then go back to Arcane to modify the compose.yaml.
Proposed Solution
For example something similar to the files view in the compose view, but with automatically saved logs. (Ex: invalid image, port already in use etc). Maybe something with simplified text that looks like a tag next to the error with a simplified output for common errors (Ex. Port already in use: 8080), with raw output being easily viewable.
Alternatives Considered
No response
Additional Context
No response
Would you be willing to work on this feature?
Feature Description
Saved failed launch errors per project in the logs section of said project.
Problem It Solves
The one thing I miss coming from Dockge is the ability to see the reason a compose stack has failed to start. I don't believe there is anything past the error notification. Currently I have to SSH into my server and manually run docker compose up to see the errors, then go back to Arcane to modify the compose.yaml.
Proposed Solution
For example something similar to the files view in the compose view, but with automatically saved logs. (Ex: invalid image, port already in use etc). Maybe something with simplified text that looks like a tag next to the error with a simplified output for common errors (Ex. Port already in use: 8080), with raw output being easily viewable.
Alternatives Considered
No response
Additional Context
No response
Would you be willing to work on this feature?