Open tsuf239 opened 1 year ago
CC: @skorfmann
Yes, here are a few thoughts:
/foo
and /foo/*
are two distinct behaviours)Besides from that, adding a proxy feature to the Website resource might also be nice.
rather than
let website = new cloud.Website(
path: "./static",
);
let api = new cloud.Api();
// somehow inject the URL as config (and having to deal with CORS for the API)
website.addJson("config.json", { api: api.url });
something like
let website = new cloud.Website(
path: "./static",
);
let api = new cloud.Api();
// define a known path with no CORS headaches
website.proxy("/myapi", api.url)
This stems from this example
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Totally agree with Sebastian: allowing to define proxies in the website resource directly would be awesome.
Not sure what elements can be used to provide the same functionality in the cloud providers than aws, though.
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Feature Spec
Creating a proxy wing resource that will simplify the following code: https://github.com/winglang/website-proxy could be helpful
@ainvoner FYI
Use Cases
gathering a few different domains to be under a single domain
Implementation Notes
We should probably write a blog post after achieving that easily on wing :)
Component
SDK
Community Notes