# FAQ

## Should I use CLI or Makefile commands?

We recommend the Makefile commands. These often run the `stoobly-agent scaffold` commands with other prerequisite commands and optimal flags.

These also run the scaffold commands in a Docker container to ensure dependencies are consistent across runs.

## Which Workflow does my custom container service go in?

This depends on what use-case you want to use the service for.

If you want to record requests, then you should add it to the `record` workflow first.

Then only add it to the `mock` and `test` workflows if you want unrecorded requests to go the service.

## Which Docker network does my service go in?

There are two Docker networks:

* `app.ingress`
* `app.egress`

To learn more:

{% content-ref url="/pages/hvGjzhgu6l2Nw4iB48E6" %}
[Scaffold](/core-concepts/scaffold.md)
{% endcontent-ref %}

## How to run concurrent test workflows in CI?

Ideally your CI pipelines are running on isolated hosts, but often that isn't the case.

Add the "namespace" flag to your workflow run command to avoid Docker resource conflicts. A recommended namespace name is the git commit of the branch's HEAD. Also set the Makefile option `workflow_up_extra_options="--no-publish"` so Docker ports are not published in CI.

**Note:** Namespaces are only supported by test workflows and custom workflows based on the test workflow template. Record and mock workflows do not support namespaces.

Makefile command example:

```
make -f .stoobly/services/Makefile test workflow_up_extra_options="--no-publish" options="--namespace $(git rev-parse HEAD)"
```

Scaffold run command example:

```
stoobly-agent scaffold workflow up test --no-publish --namespace $(git rev-parse HEAD)
```

## What agent version of Scaffold am I running?

Run this command to output the Docker image version of your Scaffold:

```
$ cat .stoobly/services/.Dockerfile.context | grep "FROM"

FROM stoobly/agent:2.0
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stoobly.com/guides/how-to-integrate-e2e-testing/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.