# How to install node red and recognizer

**URL:** <https://discourse.nodered.org/t/how-to-install-node-red-and-recognizer/82249>\
**Category:** General\
**Created:** [22 October 2023 07:50 UTC](https://discourse.nodered.org/t/how-to-install-node-red-and-recognizer/82249 "2023-10-22T07:50:51Z")\
**Posts on this page:** 1\
**Showing post:** 58

<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:** [28 October 2023 13:00 UTC](https://discourse.nodered.org/t/how-to-install-node-red-and-recognizer/82249/58 "2023-10-28T13:00:04Z")

</div>

> [@dceejay](#):
>
> node-red-start - easier to type alias for above that also then tails the log file so you see what is happening. This is the recommended way to do it.

I find tailing the log file a pain in the tail! 😄  
But on the occasions when I do want to see the output, eg after a reinstall, I find `node-red` does the job.

> [@dceejay](#):
>
> node-red start - starts Node-RED as the local user with a parameter ( the flow file name) of start. Def wrong way to do it.

I almost always use `sudo systemctl restart nodered`.  
But if you search through this forum you can find many examples of people saying they ran `node-red start`

If as a beginner you do run `node-red start` you get an empty editor, no sign that you made a mistake. If you deploy it creates a flowfile called start (not start.json) and now _you must always use_ `node-red start` to see your flows.

Perhaps the node-red script would be better if it accepted a flag -f flowfilename and to avoid breaking changes, a warning if a parameter was used as the flow file name without this flag?

ps See [this thread](https://discourse.nodered.org/t/raspberry-pi-hangs-up-at-node-red-start/3181) for an example of mutual misunderstandings around the start-up command

---

_[View the full topic](https://discourse.nodered.org/t/how-to-install-node-red-and-recognizer/82249)._