Skip to content

Running superset asynchronously in non-dev #16105

Answered by nytai
anthony6401 asked this question in Q&A / Help
Discussion options

You must be logged in to vote

the docker-compose-non-dev.yml file hasn't been updated with the websocket proxy service. The motivation behind the non-dev workflow is to quickly get superset up an running. Since the websocket service requires that a docker image be built it will just make the whole process much slower. You can probably just copy in the service def from the docker-compose.yml file and it should work.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@anthony6401
Comment options

Answer selected by anthony6401
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants