Skip to content

Conversation

acao
Copy link
Member

@acao acao commented Nov 27, 2019

  • update dependencies only as needed
  • add handler using aws-express-serverless (not ideal from a severless perf perspective as I understand, but it works!)
  • move code around to share with a local, normal express server
  • add build step for netlify-lambda script
  • add netlify deploy previews
  • upgrade GraphiQL version
  • switch npm scripts to use yarn
  • update docs

check out the deploy preview below if you want to see it in action 🚀 ex

@acao acao force-pushed the restore-server branch 3 times, most recently from 569d8c7 to 12c5f8f Compare November 27, 2019 20:23
@acao acao changed the title Restore server (netlify redux) Restore server (netlify functions redux) Nov 27, 2019
@acao acao force-pushed the restore-server branch 8 times, most recently from ab972fa to d8d1c03 Compare November 27, 2019 20:54
@acao acao changed the title Restore server (netlify functions redux) restore swapi server (netlify functions redux) Nov 27, 2019
@acao acao requested review from benjie and removed request for IvanGoncharov, benjie and leebyron November 27, 2019 21:01
acao added a commit to acao/graphql.github.io that referenced this pull request Nov 27, 2019
There's will be a new build for swapi-graphql at netlify once graphql/swapi-graphql#162 is merged, we can merge this to take it live 🌍 

I'm pretty sure the order of the last two rules will be fine. If the last one doesn't work, it will still work

```
/swapi-graphql/graphql https://swapi-graphql.netlify.com/.netlify/functions/index 200
```
this just 200 redirects (non permanent?) which essentially is netlify terms for what nginx is a proxy_path

so this will just make `graphiql.org/swapi-graphql/graphql` an alias for the lambda endpoint. see the PR's develop preview before it's merged if you want to see that default lambda path in action for yourself
@acao acao force-pushed the restore-server branch 2 times, most recently from ecf52b6 to 886989d Compare November 27, 2019 21:21
- update dependencies only as needed
- add handler using aws-express-serverless (not ideal but it works!)
- move code around to share with a local, normal express server
- add build step for netlify-lambda script
- add netlify deploy previews
- upgrade GraphiQL version
Copy link
Member

@orta orta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, this looks good to me - just needs to be green again. Deploy preview looks 👍

</style>
<link rel="icon" href="favicon.ico">
<link href="//cdn.jsdelivr.net/npm/graphiql@0.11.11/graphiql.css" rel="stylesheet" />
<link type="text/css" href="//unpkg.com/graphiql@0.17.0/graphiql.css" rel="stylesheet" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

quite the jump

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol, it works! yay

@acao
Copy link
Member Author

acao commented Nov 27, 2019

@orta thanks so much! this is gonna help me sleep a little better at night haha

@acao acao merged commit aebd693 into master Nov 27, 2019
@acao acao deleted the restore-server branch November 28, 2019 04:13
Dipeshwagle pushed a commit to Dipeshwagle/graphql.github.io that referenced this pull request Aug 18, 2020
There's will be a new build for swapi-graphql at netlify once graphql/swapi-graphql#162 is merged, we can merge this to take it live 🌍 

I'm pretty sure the order of the last two rules will be fine. If the last one doesn't work, it will still work

```
/swapi-graphql/graphql https://swapi-graphql.netlify.com/.netlify/functions/index 200
```
this just 200 redirects (non permanent?) which essentially is netlify terms for what nginx is a proxy_path

so this will just make `graphiql.org/swapi-graphql/graphql` an alias for the lambda endpoint. see the PR's develop preview before it's merged if you want to see that default lambda path in action for yourself
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants