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.

Sign up for GitHub

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

Jump to bottom

Proxy can deliver static files directly #187

Open
expcat opened this issue May 22, 2020 · 4 comments
Open

Proxy can deliver static files directly #187

expcat opened this issue May 22, 2020 · 4 comments
Labels
Deployment cookbook Base capability is there, but documentation on how to achieve the scenario is required. Priority:1 Used for divisional .NET planning single_exe Issues that apply when a shipping YARP as a single exe Type: Enhancement New feature or request User Story Used for divisional .NET planning
Projects
YARP Planning
Milestone
Backlog

Comments

@expcat
Copy link

expcat commented May 22, 2020 •
edited by samsp-msft

What should we add or change to make your life better?

Support to configure static file resources.

Why is this important to you?

Avoid using Nginx on the front end.

This is doable today if you customize the pipeline to include static files, but needs a configuration option for a stand-alone exe
@expcat expcat added the Type: Idea This issue is a high-level idea for discussion. label May 22, 2020
@Tratcher
Copy link
Member

Since we use the AspNetCore infrastructure you can already use the existing StaticFile middleware for this. Can you try this with preview1 and let us know how it works for you?

When we create a pre-built exe version of the proxy we'll want to consider how to enable static files via config.

@samsp-msft samsp-msft added Deployment cookbook Base capability is there, but documentation on how to achieve the scenario is required. Type: Enhancement New feature or request and removed Type: Idea This issue is a high-level idea for discussion. labels May 26, 2020
@samsp-msft samsp-msft added this to the 1.0.0 milestone May 27, 2020
@samsp-msft
Copy link
Contributor

Triage: Will need config for exe scenario.

@Tratcher Tratcher mentioned this issue Jun 16, 2020
Open
@samsp-msft samsp-msft mentioned this issue Jun 23, 2020
Open
@Tratcher Tratcher added this to 1.0 Backlog in YARP Planning Sep 21, 2020
@samsp-msft samsp-msft mentioned this issue Oct 21, 2020
Closed
37 tasks
@samsp-msft samsp-msft changed the title Support to configure static file resources Proxy can deliver static files directly Oct 21, 2020
@samsp-msft samsp-msft added the User Story Used for divisional .NET planning label Oct 21, 2020
@samsp-msft samsp-msft added the Priority:1 Used for divisional .NET planning label Jan 21, 2021
@karelz karelz modified the milestones: YARP 1.0.0, Backlog Mar 24, 2021
@karelz karelz moved this from 1.0 Backlog to Future in YARP Planning Mar 24, 2021
@Tratcher Tratcher mentioned this issue Apr 9, 2021
Closed
@samsp-msft samsp-msft added the samsp_list Personal tag used when reviewing issues for further discussion label Dec 9, 2021
@samsp-msft
Copy link
Contributor

Doc so we can close it

@Tratcher
Copy link
Member

Tratcher commented Dec 9, 2021

@samsp-msft this should be combine with the exe scenario.

@samsp-msft samsp-msft added the single_exe Issues that apply when a shipping YARP as a single exe label Dec 9, 2021
@karelz karelz removed the samsp_list Personal tag used when reviewing issues for further discussion label Dec 16, 2021
@Tratcher Tratcher mentioned this issue Nov 5, 2022
Merged
@Tratcher Tratcher self-assigned this Nov 14, 2022
@Tratcher Tratcher mentioned this issue Nov 23, 2022
Closed
@Tratcher Tratcher removed their assignment Nov 29, 2022
@lixiaoqiang lixiaoqiang mentioned this issue Aug 28, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Deployment cookbook Base capability is there, but documentation on how to achieve the scenario is required. Priority:1 Used for divisional .NET planning single_exe Issues that apply when a shipping YARP as a single exe Type: Enhancement New feature or request User Story Used for divisional .NET planning
Projects
YARP Planning
  
Future
Milestone
Backlog
Development

No branches or pull requests
4 participants
@Tratcher @expcat @karelz @samsp-msft