# Create a pop up alert when deploying node in a no local configuration
**URL:** https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401
**Category:** Feature Requests
**Created:** [13 March 2024 13:08 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401 "2024-03-13T13:08:48Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Maluquinho59](https://discourse.nodered.org/u/Maluquinho59)
#### Post date: [13 March 2024 13:08 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/1 "2024-03-13T13:08:48Z")
Hello.
Nodered 3.1.6
When we are on a server (in a not local configuration) trying to deploy a code, there is no alert sent to notify a potential risk.
I think it can be benefical to add such a feature (to avoid creating important mistakes).
For exemple, i tried on /package/node\_modules/@node-red/editor-client/src/js/ui/deploy.js to modify arround line 440 with the following code :
And it result in a pop up when deploying in a no local disposition
```auto
....
let notificationButtons = [];
let notification;
if (!window.location.href.includes("localhost") && !window.location.href.includes("127.0.0.1")) {
showWarning = true;
notificationMessage = "" + RED._("You are not in localhost. Do not deploy unvalidated flow") + "
" +
"" +
RED._('deploy.confirm.confirm') +
"
";
notificationButtons = [
{
id: "red-ui-deploy-dialog-confirm-deploy-deploy",
text: RED._("deploy.confirm.button.confirm"),
class: "primary",
click: function () {
save(true);
notification.close();
}
}
];
} else if (hasUnknown && !ignoreDeployWarnings.unknown) {
showWarning = true;
notificationMessage = "" + RED._('deploy.confirm.unknown') + "
" +
'- ' + cropList(unknownNodes).map(function (n) { return sanitize(n) }).join("
- ") + "
" +
RED._('deploy.confirm.confirm') +
"
";
notificationButtons = [
{
text: RED._("deploy.unknownNodesButton"),
class: "pull-left",
click: function() {
notification.close();
RED.actions.invoke("core:search","type:unknown ");
}
},
{
id: "red-ui-deploy-dialog-confirm-deploy-deploy",
text: RED._("deploy.confirm.button.confirm"),
class: "primary",
click: function () {
save(true);
notification.close();
}
}
];
}
.......
```
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [13 March 2024 13:13 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/2 "2024-03-13T13:13:36Z")
Don't like this.
I **never** access my Node-red servers using a browser on the server itself so I'm always in a "no local configuration".
This popup, like popups in general, would be very annoying.
---
### Author:  [@Maluquinho59](https://discourse.nodered.org/u/Maluquinho59)
#### Post date: [13 March 2024 13:16 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/3 "2024-03-13T13:16:06Z")
So maybe with a setting to enable or disable this kind of popup ?
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [13 March 2024 13:25 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/4 "2024-03-13T13:25:59Z")
There is a difference in culture between WIndows and Linux hemispheres.
In WIndows it's very common to see an "Are you sure?" popup. In my experience, this results in clicking Yes without any real consideration of the question.
Contrariwise, Linux tries to do whatever you ask it to, assuming you know what you are doing.
A user generally learns to consider the consequences before clicking Go.
Neither approach actually prevents mistakes.
Fortunately Node-red respects CTRL-Z to undo.
I think it's better to only allow thoughtful and competent users to access important live servers.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [17 March 2024 13:33 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/5 "2024-03-17T13:33:12Z")
I think this may have some merit as an option in settings.js - perhaps a PR?
It certainly couldn't be a fixed feature as it wouldn't allow for the many different ways of using Node-RED.
---
### Author:  [@Maluquinho59](https://discourse.nodered.org/u/Maluquinho59)
#### Post date: [18 March 2024 14:01 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/6 "2024-03-18T14:01:12Z")
Thanks for your consideration.
Yes a setting that can be on / off to nofity if the adress is not "localhost" or something custom can be good 😉
But for sure nodered is used with a lot of different way so I don't know the best solution to implement it
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [25 March 2024 14:54 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/7 "2024-03-25T14:54:45Z")
I don't really understand the risk, is it linked to multi-user editing (two users editing at the same time)?
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [24 May 2024 14:55 UTC](https://discourse.nodered.org/t/create-a-pop-up-alert-when-deploying-node-in-a-no-local-configuration/86401/8 "2024-05-24T14:55:31Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.