# \[Feedback Wanted\] How do you use the Manage Palette

**URL:** <https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787>\
**Category:** Core Development\
**Tags:** editor\
**Created:** [30 October 2024 10:49 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787 "2024-10-30T10:49:09Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [30 October 2024 10:49 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/1 "2024-10-30T10:49:09Z")

</div>

Hi all,

The palette receives features to improve its use.

I would need your feedback for the following question.

**How do you install or update several modules at once** :

_Poll ([view on site](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/1))_

Thank you for your help 🙂

EDIT: Don't forget to vote for this [poll](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/23) too 😈

---

<div class="post-metadata">

**Author:** ![greengolfer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/greengolfer/32/28276_2.png) [@greengolfer](https://discourse.nodered.org/u/greengolfer)\
**Post date:** [30 October 2024 10:51 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/2 "2024-10-30T10:51:46Z")

</div>

Click and wait. If it fails for whatever reason I don’t pile up multiple upgrades.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [30 October 2024 11:16 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/3 "2024-10-30T11:16:32Z")

</div>

For updating, I click on the button for each node offering updates.

Then I sit and wait wondering "Why isn't there a display (not "view the log") of which one it's currently working on?

And finally "Why isn't there a button to restart Node-red and save me having to ssh to the device and doing it by hand"?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [30 October 2024 11:23 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/4 "2024-10-30T11:23:26Z")

</div>

For multiple installations, I just do them all - I don't wait. The log shows any failures anyway.

For updates, I really would wish for an obvious "Update all" button to appear when there are updates available.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [30 October 2024 11:24 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/5 "2024-10-30T11:24:11Z")

</div>

> [@jbudd](#):
>
> I click on the button for each node offering updates.

So you trigger several updates (at the same time) then you wait while looking at the log?

> [@jbudd](#):
>
> Why isn't there a button to restart Node-red

NR cannot reload its dependencies without a reboot. I don't remember the underlying reason.

> [@TotallyInformation](#):
>
> For updates, I really would wish for an obvious "Update all" button to appear when there are updates available.

This is the reason for the life of this subject 😉

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [30 October 2024 11:24 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/6 "2024-10-30T11:24:38Z")

</div>

> [@jbudd](#):
>
> And finally "Why isn't there a button to restart Node-red and save me having to ssh to the device and doing it by hand"?

If you capture the PID in settings.js, you can use that to kill the current running instance in a flow. If using systemd, it will restart itself.

Alternatively, you can change the sudo settings to allow Node-RED to issue a passwordless restart:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/9/39aaecb0086a81b836ed57b27efa22a26c74dacc.png)

Obviously either way has some risks though.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [30 October 2024 11:30 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/7 "2024-10-30T11:30:55Z")

</div>

To complete the reason for this subject is that I had initially planned a checkbox in front of each module in order to select the modules to update. But Nick pointed out to me that it is equivalent to clicking on the "update" button of several modules at the same time.

 ![Capture d’écran 2024-10-29 à 23.16.12](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/f/4f58810e37d8a7095290f033bb54f9ead680e4e1.png)

What is planned is an "Update all" button, I'm looking for a kind of progress bar.

PS: a filter selects only the modules to update. So the image is not quite correct 🫣

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [30 October 2024 11:38 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/8 "2024-10-30T11:38:33Z")

</div>

> [@TotallyInformation](#):
>
> If you capture the PID ... kill the current running instance in a flow. If using systemd, it will restart itself.
> 
> Alternatively ... allow Node-RED to issue a passwordless restart:

Indeed one can make a flow to restart Node-red, which makes it harder to understand why Node-red can't [easily] do the same thing ...

> [@GogoVega](#):
>
> I'm looking for a kind of progress bar.

Trouble with a progress bar is that some updates take a lonnnnng time so "Update 2 of 4" would be better than "25% complete".  
A list of queued updates with a tick (or cross) as each is completed would be great.  
cf The Linux install script showing a tick as each task completes (bash, not NR of course)

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [30 October 2024 11:47 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/9 "2024-10-30T11:47:10Z")

</div>

> [@jbudd](#):
>
> "Update 2 of 4"

That's what I had in mind - to the right of the "Update all" button

> [@jbudd](#):
>
> A list of queued updates with a tick (or cross) as each is completed would be great.

Do you have an example of a sketch?

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [30 October 2024 12:01 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/10 "2024-10-30T12:01:00Z")

</div>

I have some nodes that I not update due to legacy issues, these nodes function great on the machine they are on, but if updated no longer work.

It may be an idea to add a do not update checkbox/flag that removes them from the update all.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [30 October 2024 12:08 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/11 "2024-10-30T12:08:34Z")

</div>

That's why I put the checkboxes in.

I'm afraid Nick's answer will be to either click "update all" or click every "update" button.

Instead of the checkbox, I also thought about clicking on the element (Control held down) to select it. The element will have a different background color to said selected.

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [30 October 2024 12:13 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/12 "2024-10-30T12:13:07Z")

</div>

I am talking about a permanent flag (do not update) that survives a browser reload etc, then the update all is useful, as the flagged nodes will not update. Otherwise update all becomes a useless button that I and maybe others would never use as it would cause issues.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [30 October 2024 12:23 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/13 "2024-10-30T12:23:09Z")

</div>

I understood what you wanted.

Thinking about it a bit more, it would be more useful to apply this flag to the filter than the checkboxes that amount to clicking on each module.

So I'll keep your suggestion 🙂

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [30 October 2024 12:52 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/14 "2024-10-30T12:52:37Z")

</div>

Would it be possible for an admin to pin the subject to get as much feedback as possible. Thanks 😘

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [30 October 2024 13:02 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/15 "2024-10-30T13:02:24Z")

</div>



---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [30 October 2024 13:16 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/16 "2024-10-30T13:16:49Z")

</div>

If this will be rolled out, the "Update all" button will be attractive enough that the one may freely not even think about that there is one limping node which you don't want to update. Specially if you have many instances with pretty same set of nodes but minor differences ...  
That will hit for sure.  
The "Are you sure" message with checkbox "don't show again" may do..

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [30 October 2024 13:42 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/17 "2024-10-30T13:42:40Z")

</div>

Usually I tend to only update 1 or 2 nodes via the UI. The main time I want to update multiple is when I am also updating the whole system - so doing OS updates, patches, nodejs updates and so on - so I usually do them all from the command line with a simple `npm update` instead - as I will need to restart the app - or reboot anyway.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [30 October 2024 14:49 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/18 "2024-10-30T14:49:45Z")

</div>

> [@jbudd](#):
>
> Indeed one can make a flow to restart Node-red, which makes it harder to understand why Node-red can't [easily] do the same thing ...

Well, I think the main issue is that there are many ways to run Node-RED and so many ways to restart it. How would Node-RED know which to use? Is it worth trying to build that logic into Node-RED?

---

<div class="post-metadata">

**Author:** ![RvG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rvg/32/96613_2.png) [@RvG](https://discourse.nodered.org/u/RvG)\
**Post date:** [30 October 2024 15:15 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/19 "2024-10-30T15:15:20Z")

</div>

As a tester for the set of (now) 14 nodes my employer is developing, which gets updated regularly using our internal catalogue, I'd like an 'Update all' very much 🙂

I currently get a dialog for each one that tells me Node-RED wil require a restart. I wouldn't need a confirmation list of nodes that require this, a single message would be enough, but maybe someone else needs could want that?

In general, a new dialog "you're going to update 14 nodes" would be nice even when no restart is needed. Getting two dialogs would be OK as well (one integrated dialog would be better), but might be confusing depending on the wording.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [30 October 2024 17:04 UTC](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787/20 "2024-10-30T17:04:09Z")

</div>

I have always updated all available updates in one go.

However it did catch me out on one occasion as one of the updates had not finished before I restarted, which then broke things 😕

So what you are suggesting @GogoVega would be very welcome.

[Next page](https://discourse.nodered.org/t/feedback-wanted-how-do-you-use-the-manage-palette/92787.md?page=2)