Improved instructions & docker permissions fix #1174
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a direct consequence of these two #1172 and #1173.
It changes the following:
Dockerfile
that runs withcompiler/build.sh
.README.md
.README.md
to improve readability.ui/README.md
about having to set the server's address to0.0.0.0
to expose it to the world.README.md
that highlights:Important
When running the server, you may see some docker warnings about missing containers. You can safely ignore them. You shouldn't see any docker containers running most of the time. This is normal. You don't need to spawn or kill any containers yourself. The backend manages that itself.