We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Just got this question on slack:
How much control (if any) do you have over deployment to your own infrastructure ( say on AWS with Lamda—or has next been designed to work with now)
now
I feel like we should document that people can use next without using now, but still give a preference to now obviously 😉
next
The text was updated successfully, but these errors were encountered:
Yeah! I think this great. Adding much more information to the README won't be working great.
So, my suggestion is create a Wiki Page(here's the link) and link it in the Deployment section. In that, we can add more about deployment tools.
Sorry, something went wrong.
No branches or pull requests
Just got this question on slack:
I feel like we should document that people can use
next
without usingnow
, but still give a preference tonow
obviously 😉The text was updated successfully, but these errors were encountered: