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
The main idea is to be able to turn on/off some features with .env or via package.json:
.env
package.json
... "henri" { "frontend": false, "backend": true, "socketio": false, "rest": true }
Similar options in ,env file or via environment variables:
HENRI_OPTS="frontend=false;backend:true;socketio:false;rest:true"
Defaults to true if missing.
true
So, if you want to deploy multiple backends without nextjs overhead (?!?) or vice-versa, this can be done easily.
backend: false would disable mostly everything but Next.js
backend: false
Is this necessary? Are there use cases? cookies would not be parsed and SSR partially broken without data injection...
The text was updated successfully, but these errors were encountered:
If you don't define something in the configuration, it will not load (next, socketio, rest, auth)
Sorry, something went wrong.
No branches or pull requests
The main idea is to be able to turn on/off some features with
.env
or viapackage.json
:Similar options in ,env file or via environment variables:
Defaults to
true
if missing.So, if you want to deploy multiple backends without nextjs overhead (?!?) or vice-versa, this can be done easily.
backend: false
would disable mostly everything but Next.jsIs this necessary? Are there use cases? cookies would not be parsed and SSR partially broken without data injection...
The text was updated successfully, but these errors were encountered: