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

Support Netlify Functions for NPM Ory Cloud Integrations #22

Open
aeneasr opened this issue Mar 2, 2022 · 1 comment
Open

Support Netlify Functions for NPM Ory Cloud Integrations #22

aeneasr opened this issue Mar 2, 2022 · 1 comment
Labels

Comments

@aeneasr
Copy link
Member

aeneasr commented Mar 2, 2022

See discussions https://ory-community.slack.com/archives/C02MR4DEEGH/p1646150967822979

Basically, what we do here

function getBaseUrl(options: CreateApiHandlerOptions) {

is that we create an expressJS handler that is specific to NextJS / Vercel's edge function model. However, under the hood, it's just plain expressJS (I believe).

If we extract the configuration options and the actuall proxying

return (req: NextApiRequest, res: NextApiResponse<string>) => {

we could for sure make it work with netlify and other providers (e.g. cloudflare functions).

It's probably just a bit of fiddling to get it right!

@aeneasr aeneasr changed the title Support Netlify Functions Support Netlify Functions for NPM Ory Cloud Integrations Mar 2, 2022
Copy link

github-actions bot commented Jan 1, 2025

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale label Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant