Carlos Martín

In this case the error is happening because the system does not have `docker-compose` installed, and `sourced-ce` tries to install a containerized alternative. The solution is to simply install docker-compose...

I'd strongly prefer not to, to be honest. We use docker images that need to be downloaded, and the main use case is going to download git repositories and metadata......

Ok, let's create an issue (in backlog? feature-idea?) if you think this a use case we will need to support. There are some things we could do in `sourced-ce` to...

To be clear, I'm against adding any possible deployment mode _by default_ to the docs, without further discussion on what we really want to support and to what extent. But...

> Once all those pieces are in place, it would be good if CE could be started up _without_ additional pulls from remote sources. This is already the case if...

> So if he installs the `docker-compose` tool (and has the other files in place as described), it should be self-contained? Yes. > srcd-ce makes calls to github to check...

> About the error getting `run.sh`, which caused this issue, I think it could be more user friendly, and point to proper docs about what was needed, why, and how...

I'm not so sure we should to use log formatted output for a CLI application.

@dpordomingo let's fix what is actually broken (contributing, anchors) and assume all changes were intentional. @vcoisne let's please follow the normal github workflow and do all future edits as pull...

Also: the ` ```text ` code blocks should be reverted to the proper syntax highlighting we had before.