-
Notifications
You must be signed in to change notification settings - Fork 5
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
Added nitro to the frameworks #224
Conversation
Implemented the changes suggested by Costin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
docs/frameworks/nitrojs.md
Outdated
1. You might need to replace the `path` field with the path relative at **genezio.yaml** file. | ||
2. This example configuration works if **genezio.yaml** is in the same directory as your main application file. | ||
::: | ||
## 3. Test Your App Locally |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this already said starting with line 98?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is, but we are also doing this in the express doc, and I thought it was something we wanted. IMO if we delete one it should for sure be the one in lines 98, but I also see some value in having both, as a way for someone who is creating his first nitro app from scratch to acknowledge that it is working, before doing anything Genezio related.
Release Refine Tutorial
Fixed some typos
Add Fastify and other small improvs
…rted Feature/new getting started
We should first wait for genezio to be added to nitro in the following days, before pushing to prod. Just an initial draft.