@@ -118,20 +118,20 @@ For more advanced scenarios like e.g. making custom MCP server code available, y
118118Example: a custom MCP server deployment via Docker image:
119119
120120``` sh
121- export MY_MCP_SERVERS=. /mcp_servers
122- export MY_TOOLBOXES=. /toolboxes
123- export MY_PERSONALITIES=. /personalities
124- export MY_TASKFLOWS=. /taskflows
125- export MY_PROMPTS=. /prompts
121+ export MY_MCP_SERVERS=" $PWD " /mcp_servers
122+ export MY_TOOLBOXES=" $PWD " /toolboxes
123+ export MY_PERSONALITIES=" $PWD " /personalities
124+ export MY_TASKFLOWS=" $PWD " /taskflows
125+ export MY_PROMPTS=" $PWD " /prompts
126126
127127if [ ! -f " .env" ]; then
128128 touch " .env"
129129fi
130130
131131docker run \
132132 --volume /var/run/docker.sock:/var/run/docker.sock \
133- --volume logs:/app/logs \
134- --mount type=bind,src=. env,dst=/app/.env,ro \
133+ --volume " $PWD " / logs:/app/logs \
134+ --mount type=bind,src=" $PWD " / env,dst=/app/.env,ro \
135135 ${MY_DATA: +--mount type=bind,src=$MY_DATA ,dst=/ app/ my_data} \
136136 ${MY_MCP_SERVERS: +--mount type=bind,src=$MY_MCP_SERVERS ,dst=/ app/ my_mcp_servers,ro} \
137137 ${MY_TASKFLOWS: +--mount type=bind,src=$MY_TASKFLOWS ,dst=/ app/ taskflows/ my_taskflows,ro} \
0 commit comments