-
Notifications
You must be signed in to change notification settings - Fork 44
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
Address feedback from Under the Xray session #602
Conversation
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
2 similar comments
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
@@ -104,7 +120,7 @@ This command: | |||
- Creates a port-forward from localhost to port 3000 inside the container so you can navigate to the app's frontend UI | |||
- Streams container logs to your terminal | |||
|
|||
Access the application by opening [http://localhost:3000](http://localhost:3000) in a browser: | |||
Access the application by opening [http://localhost:3000](http://localhost:3000) in a browser. If you are using codespaces, you can get the demo app url from the ports tab in VSCode. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember having trouble looking for the port tab to get the remote localhost url. not sure if there's anything we can do to make this more clear?
Co-authored-by: jasonviviano <[email protected]>
Co-authored-by: Will <[email protected]>
Co-authored-by: Will <[email protected]>
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
1 similar comment
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
… info before proceeding to copy code or run cmds Signed-off-by: Will Tsai <[email protected]>
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
{{< tabs "Codespaces" "Kubernetes Cluster" >}} | ||
|
||
{{% codetab %}} | ||
Use [Codespaces](https://github.com/features/codespaces) to launch a pre-configured container with Radius installation on a k3d cluster |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still don't think we should put Codespaces as the first option. There's a 75% chance a reader will get a "404 not found" error when they click the button, and then when they hit that they'll then need to apply for GitHub access, which may take up to a couple hours. When users drop into the first app experience we don't want them to click a button and then have to wait before they can proceed.
I think we should 100% make it the primary experience once we go public, but we're not ready yet.
|
||
{{% codetab %}} | ||
|
||
> *If you don't have a preferred way to create Kubernetes clusters, you could try using [k3d](https://k3d.io/), which runs a minimal Kubernetes distribution in Docker.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this note
@@ -92,7 +108,7 @@ In addition to starting Radius services in your Kubernetes cluster, this initial | |||
|
|||
## 4. Run the app | |||
|
|||
Use the `rad run` command to run the app in your environment: | |||
Use the below command to run the app in your environment, then access the application by opening [http://localhost:3000](http://localhost:3000) in a browser. If you are using codespaces, you can get the demo app url from the ports tab in VSCode. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once we add Codespaces support we should find a better way to handle opening the app instead of saying "from the ports tab".
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://wonderful-plant-020417a1e-602.westus2.azurestaticapps.net |
Closing this in favor of #680 to merge changes directly to v0.23 |
Thank you for helping make the Radius documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Addresses #586
Auto-generated description
🤖 Generated by Copilot at 7692f3e
Summary
🚀📝🔖
This pull request enhances the getting started documentation for Radius by adding a new option to use Codespaces for launching a containerized environment, and by adding markers to the
app-with-redis-snippets.bicep
file to facilitate code copying.Walkthrough
app-with-redis-snippets.bicep
file to point to the entire container definition (link, link, link)Issue reference