More control over docker-compose content

I'm facing a situation where I'm already have a IPFS private network and a private permissioned blockchain.

My goal is to not allow FF to create its own blockchain node and use the one I have instead in native way (I mean in replacement of its own, not using connectors - I don't want an extra node in same machine )

Another thing is to use a customized IPFS node to connect in to my own network.

Some things I must do like empty the Bootsrap list of the IPFS config, add my own bootstrap, add my swarm file instead pass it from the compose (I may change it without to re run all the compose again - who knows?)

In the same way I need to make some adjusts in the Blockchain node to fit my needs.

In short, I must run some scripts before these components come up.

What I suggest is to allow to remove these pieces from the compose and run they "by hand". I don't know if I can do it using the override compose. By the way... why can't we just edit the compose instead using an override file? Is that possible to remove things from compose using the override file?

OR ....

Maybe you guys want to publish in some documents the step-by-step on how to build all the stack "by hand" ... from the docker pull to contract publishing ...all these things hidden by the FF-CLI so we may do more "granularity" ...