Repository navigation
⚡️ Feature: Override files on git synced projects #4021
Replies: 3 comments 1 reply
|
This is exactly what I just ran into and it really should be implemented. Every project out there with an example compose file is potentially affected and unusable within Arcane itself. As for now, I need to manually clone the repo in the shell and use the plain files in Arcane, but this is a mess. |
|
I honestly can't believe this is not already a basic feature. Really basic projects I can think of have a Arcane should support overwriting any file or folder with your own contents. This feature basically makes Arcane unusable for me over my simple local Docker bash files, and I have to uninstall it for now. |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Feature Description
Add override file support to git sync projects.
Problem It Solves
Git sync projects are read only, but if you're pulling from a projects repo often times the compose examples provided are meant to be edited, or include hardcoded environment variables. This really seems like the place overrides belong since the compose itself is overwritten with every sync.
Proposed Solution
Enable creation of overrides on git synced projects.
Alternatives Considered
Manually create the compose, but that defeats the purpose of git sync.
Additional Context
No response
Would you be willing to work on this feature?
All reactions