default settings

[gadget78]

im not sure of how i can alter the default setting of NPM when installing,
as i want the default to be "drop connection"
for the setting of "What to show when nginx is hit from a unknown host"

[Zoey2936]

I think you mean when deploying NPMplus automatically, right? Because otherwise you can do it in the UI.

[Zoey2936]

like i change the streams template file, so port ranges are supported here by default

what do you mean exactly? prot ranges should be supported an work with npmplus for streams

[gadget78]

like i change the streams template file, so port ranges are supported here by default

what do you mean exactly? prot ranges should be supported an work with npmplus for streams

i have this added to my prerun script,
sed -i "s/{{ forwarding_port }}/\\\$server_port/g" /app/templates/stream.conf && echo " - stream port template updated to support ranges" || { echo " ** failed to update stream range fix"; true; }
so that the specific incoming "server_port" is used, and not the static "forwarding_port" ..

if i update file
backend/schema/paths/settings/get.json
within the same prerun script, so that the "value": "congratulations", is "value": "444",
would that change the initial default to 444, and not how its starts with congratulations setting ? ..

[Zoey2936]

No it would not, cirl is the only way to update the database and the files on disc

[Zoey2936]

An env will be added with the next release to change the initial value

[Zoey2936]

if you want, you can test this alpha/prerelease: https://github.com/ZoeyVid/NPMplus/releases/tag/2025-01-03-alpha (but make a backup first)

[Zoey2936]

i have this added to my prerun script,
sed -i "s/{{ forwarding_port }}/\\\$server_port/g" /app/templates/stream.conf && echo " - stream port template updated to support ranges" || { echo " ** failed to update stream range fix"; true; }
so that the specific incoming "server_port" is used, and not the static "forwarding_port" ..

So you add a port range as incomming port and the forwarding port should be the same as the client connects to? Adding $server_port as forwarding port within the ui is regex blocked right? Since with your change forwarding port will always be the same as incomming port, right? Should I maybe change the regex instead so you can directly put in $server_port as forwarding port in the ui?

[Zoey2936]

I will allow $server_port as a valid input as forwarding port in the ui

[Zoey2936]

if you want, you can test this alpha/prerelease: https://github.com/ZoeyVid/NPMplus/releases/tag/2025-01-03-alpha (but make a backup first)