svrjs/svrjs-nextjs-website
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Compare commits

base: svrjs:cb0a813fdbb1c84a5cfe8489078ae7d7d836e6ad
Branches Tags
svrjs:main
svrjs:proxy
..
compare: svrjs:47f86122df654ed069c8141cc347ab94e8b1c8d7
Branches Tags
svrjs:main
svrjs:proxy

No commits in common. "cb0a813fdbb1c84a5cfe8489078ae7d7d836e6ad" and "47f86122df654ed069c8141cc347ab94e8b1c8d7" have entirely different histories.
cb0a813fdb ... 47f86122df

1 changed files with 1 additions and 35 deletions
Show stats Expand all files Collapse all files

36
pages/docs/mod-notes.md
View file

@ -103,7 +103,7 @@ Next.js integration is a mod, that enables SVR.JS to serve Next.js applications.
The webroot (_wwwroot_ _config.json_ property) serves as a Next.js application directory. It's recommended to set the owner of the Next.js application directory (around with all the files in it) as the user, on which SVR.JS is running (usually "svrjs"). Setting a `NODE_ENV` environment variable to `development` in SVR.JS configuration enables Next.js development server. The webroot (_wwwroot_ _config.json_ property) serves as a Next.js application directory. It's recommended to set the owner of the Next.js application directory (around with all the files in it) as the user, on which SVR.JS is running (usually "svrjs"). Setting a `NODE_ENV` environment variable to `development` in SVR.JS configuration enables Next.js development server.
It's also recommended to forbid the access to ".env" file, ".next" and ".git" directories, in case Next.js integration mod fails to load. You can set up _nonStandardCodes_ _config.json_ property like this: It's also recommended to forbid the access to ".env" file and ".git" directories, in case Next.js integration mod fails to load. You can set up _nonStandardCodes_ _config.json_ property like this:
```json ```json
{ {
"nonStandardCodes": [ "nonStandardCodes": [
@ -115,10 +115,6 @@ It's also recommended to forbid the access to ".env" file, ".next" and ".git" di
"scode": 403, "scode": 403,
"regex": "/^\\/\\.git/" "regex": "/^\\/\\.git/"
}, },
{
"scode": 403,
"regex": "/^\\/\\.next(?:$|[\\/#?])/"
},
...other non-standard codes... ...other non-standard codes...
], ],
...other config.json properties... ...other config.json properties...
@ -148,36 +144,6 @@ reverse-proxy-mod is a mod, that enables SVR.JS to do reverse proxy functionalit
_Notes moved to [SVR.JS documentation.](/docs/config/reverse-proxy-config)_ _Notes moved to [SVR.JS documentation.](/docs/config/reverse-proxy-config)_
_View the [change log.](/changelog/reverse-proxy-mod)_ _View the [change log.](/changelog/reverse-proxy-mod)_
## SvelteKit integration
SvelteKit integration is a mod, that enables SVR.JS to serve SvelteKit applications.
The webroot (_wwwroot_ _config.json_ property) serves as a SvelteKit application directory. It's recommended to set the owner of the SvelteKit application directory (around with all the files in it) as the user, on which SVR.JS is running (usually "svrjs").
It's also recommended to forbid the access to ".env" file, ".svelte-kit" and ".git" directories, in case SvelteKit integration mod fails to load. You can set up _nonStandardCodes_ _config.json_ property like this:
```json
{
"nonStandardCodes": [
{
"scode": 403,
"regex": "/^\\/\\.env(?:\\.local|\\.production)?(?:$|[#?])/"
},
{
"scode": 403,
"regex": "/^\\/\\.git/"
},
{
"scode": 403,
"regex": "/^\\/\\.svelte-kit(?:$|[\\/#?])/"
},
...other non-standard codes...
],
...other config.json properties...
}
```
_View the [change log.](/changelog/sveltekit-integration)_
## YellowSquare ## YellowSquare
YellowSquare is a JSGI (JavaScript Gateway Interface) engine. YellowSquare is a JSGI (JavaScript Gateway Interface) engine.