Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codespaces: Auto-set WebAssembly app port to public #34

Open
Arlodotexe opened this issue Feb 17, 2022 · 3 comments
Open

Codespaces: Auto-set WebAssembly app port to public #34

Arlodotexe opened this issue Feb 17, 2022 · 3 comments
Labels
build 🔥 dev loop ➰ For issues that impact the core dev-loop of building experiments enhancement Improvement to an existing feature help wanted Extra attention is needed WASM Bugs related to working with WASM/Codespaces

Comments

@Arlodotexe
Copy link
Member

Problem

As stated in #19, Uno requires port 5000 to be made public to view the app in a Codespace. After much research, I wasn't able to find a way to automatically make this port public.

Solution

GitHub Codespaces appear to be in active development, with public ports only being added around March 2021. Since Uno requires port 5000 to be public for their WebAssembly app to run in a Codespace, this should be done automatically for user convenience.

@Arlodotexe Arlodotexe added enhancement Improvement to an existing feature help wanted Extra attention is needed labels Feb 17, 2022
@michael-hawker michael-hawker added WASM Bugs related to working with WASM/Codespaces build 🔥 dev loop ➰ For issues that impact the core dev-loop of building experiments labels Apr 5, 2022
@michael-hawker michael-hawker added this to the Initial Release milestone Apr 8, 2022
@Arlodotexe
Copy link
Member Author

Possibly useful: https://cli.github.com/manual/gh_codespace_ports_visibility

@michael-hawker
Copy link
Member

michael-hawker commented Jun 16, 2022

Possibly useful: https://cli.github.com/manual/gh_codespace_ports_visibility

Could we add this to the VS Code launch config as a post-build/pre-debug command?

@Arlodotexe
Copy link
Member Author

Could we add this to the VS Code launch config as a post-build/pre-debug command?

We wouldn't want this in the VSCode launch config since that would affect it outside codespaces, too. We'd need to add this to the devcontainer instead.

The gh cli method could work, only if they include it in codespaces out of the box (pre authenticated).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build 🔥 dev loop ➰ For issues that impact the core dev-loop of building experiments enhancement Improvement to an existing feature help wanted Extra attention is needed WASM Bugs related to working with WASM/Codespaces
Projects
None yet
Development

No branches or pull requests

2 participants