You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What problem or use case are you trying to solve?
I'm trying to figure out how to edit config.toml and use it for my Docker deployment. I'm starting off from the quick installation guide.
Describe the UX of the solution you'd like
Update the documentation, perhaps a sample command, that will make the use of config.toml straightforward.
Do you have thoughts on the technical implementation?
No.
Describe alternatives you've considered
There are no alternatives. I searched diligently on how to use it, even opening a console on the container and trying to look for this config file.
I modified the quick start command by adding an additional line -v /root/config.toml:/app/config.toml
Additional context
I'm trying to expose a port on the sandbox.
I tried runtime_extra_build_args = ["-p 80:80", "-p 8080:8080"] from within config.toml.
I also tried to add -e SANDBOX_RUNTIME_EXTRA_BUILD_ARGS=["-p 80:80", "-p 8080:8080"] \ to the starter command.
Finally I tried to use host networking via -e SANDBOX_USE_HOST_NETWORK=True \which works, however this seems to cause a UI bug where the workspace files are not visible.
What problem or use case are you trying to solve?
I'm trying to figure out how to edit config.toml and use it for my Docker deployment. I'm starting off from the quick installation guide.
Describe the UX of the solution you'd like
Update the documentation, perhaps a sample command, that will make the use of config.toml straightforward.
Do you have thoughts on the technical implementation?
No.
Describe alternatives you've considered
There are no alternatives. I searched diligently on how to use it, even opening a console on the container and trying to look for this config file.
I modified the quick start command by adding an additional line
-v /root/config.toml:/app/config.toml
to no effect.
Additional context
I'm trying to expose a port on the sandbox.
runtime_extra_build_args = ["-p 80:80", "-p 8080:8080"]
from within config.toml.-e SANDBOX_RUNTIME_EXTRA_BUILD_ARGS=["-p 80:80", "-p 8080:8080"] \
to the starter command.-e SANDBOX_USE_HOST_NETWORK=True \
which works, however this seems to cause a UI bug where the workspace files are not visible.I frequently see people using it such as this one that mentions "here's my toml file", however I could not find a single result that uses config.toml for Docker deployments.
The text was updated successfully, but these errors were encountered: