In no trade version to one of the new features that were introduced, the new in command, it allows
you to create a settings file configured to your liking by going through a series of questions and a
restructured default settings file, which makes it easier for you to manually edit interchange settings.
And in this lecture, I'll show you both.
So at the moment, I'm using no trade version.
2.1.5 and.
If you go to the DOT Note Read Directory on the Raspberry Pi in, have a look inside, you see a bunch
of files end with Jason extention like this one and most important, you'll see a Settings file.
So this is where my note read Instance configuration go.
And this chasen file is a file that stores my flows.
The name of the JSON file in which the flows are stored is configurable, as you see in a moment.
I want to have a look at what the default settings file looks like, and it can have a look at that
here on GitHub in the note read repository.
There's the Settings JS file, and this is what a default settings file looks like.
As you can see, this Dot J.S. file contains the key value pairs, so here's the key here's a value
for that particular key.
This is what the note read at runtime will go into and read those key value pairs and configure itself
according to what it finds in this file.
So you are welcome to go in here and use a text editor and manually edit those settings.
This is a lot of information about what each one of those settings does, and that's quite OK.
So, for example, just scroll down to the bottom, say around.
Around here in this, for example, where you can configure the type of code editor that you are using,
the supported values for the Lib key are either ACE, which is a default or Monaco, et cetera.
So you can just change that manually.
In my case on my Raspberry Pi, I use them to do the editing so I can go into my settings, file using
them and just make the changes.
So I'm going to look for code editor.
Here it is, and I can go here and manually change this to Monaco.
I'm going to come out of this too, because what I want to show you is that instead of using the manual
classic way of editing the settings file, we can now use the we.
So because I've already made a bit of configuration and that I want to lose that, I advised that before
you go ahead and use the wizard to make changes to the settings file, you did two things.
First, you create a backup of your file, so simply copy your file into a new name.
In my case, it's back.
Just call it back to.
So you can always come back if you don't like what the wizard has done, you can always revert back
to the original backup now Settings Chair File.
And you should do the same thing with the flow's file, which in my case, because I didn't set a name
for the error flow's file, the default name that is used.
These flows underscore the hostname for the computer, which the note instance is running on both J
sends.
In my case, the host name is Node Red Dot Local.
So if I don't specify a default name for my Flo's file in the Settings Strategy, yes file, then that
file name will be flows on the school, then the name of the hostname.
Which, in my case, is no local.
Don't add, Jason.
You can find that information here, so for example, I'm going to look for hostname.
And that's what I've been talking about here.
This is a default name.
All right.
So it's a good idea to have a backup of your Flo's file anyway.
All right.
Having said all of that, let's go ahead and test out the wizard.
So here I am on my Raspberry Pi.
You don't need to be in the note rate directory.
It's just convenience, because that way you will be able to have a look at the updated settings file
after the end of the wizard execution.
So the command to invoke the wizard or use the note, read at command and pass the switch in it.
So this will now take you through the series of questions.
First, what is the file name for the Settings file and keep that setting strategy?
Yes, it already exists, so it is OK to overwrite it, and I've got a backup so I can always go back.
Do you want to set up user security?
So I'll go for yes, in this case, and then I will provide a username and password for my user.
And since that is going to be me, I'm going to give myself full access.
All right.
So know, at this point, I don't want to add another user.
So four projects projects again, it's a new feature in note red version two.
And at this point I'm going to say no, and I've got a separate lecture where I'll show you how these
projects are.
We don't need projects yet.
Just going to say no to this question.
Now this is where I can enter a name for Maslow's file.
So the default here is flows.
Don't Jason.
But if I go with this name, then what do we just going to do?
It's just going to configure note read to use that Jason, as the flows file in, is going to ignore
the existing file that I have already created, and it contains all the data for mixing flows.
So if I accept flows to Jason as the name for my flows file when I go back into Node two, yes and have
a look at its user interface and reload this page, none of my existing flows will appear because the
note read instance will be reconfigured to look for flows inside this file instead of my original file.
And because I want to continue working with my note, read flows that I have already created.
I'm going to opt to change this name into the name of my existing flows file, which is flows and the
school node.
Red Dot, local dot.
Jason.
OK.
And I don't need to encrypt the credentials file, so I'm going to hit enter here and skip to the next
question.
Now I can choose a theme for the editor.
Just keep everything looking the same, so continue with default.
And at this point, I can also select to use either Ace or Monaco is the text editor.
And since I'm working with no tradition to, I'll go for the new Monaco text editor.
And will also allow its functionaries to load external modules.
Say yes to that, and the Settings file is now.
Written completed so it can have a look and show use cat so that.
And there is the updated file looks like the original Polish court changes in settings.
For example, look for one that is easy to spot up here.
Last time I showed you the code editor segment.
This was said to Ace and now set to Monaco.
By the we said All right, to make these changes effective, I will need to restart the note read instance.
To do that, I say no.
Read.
Restart with a hyphen here.
OK, give it a few moments.
It's spinning in the back and and it got a few seconds for the restart process to finish.
I'll give it a go now just to refresh this page.
Not yet.
OK, here we go.
So remember that I have set user authentication security settings has changed, so I'm going to log
in with my user name and password now.
So my no trip instance is protected.
And there's my flow.
That's because I set the appropriate file name for a note, for instance, to look for flows.
Everything's here.
And you can also check out one of the other changes, for example, have a look at one of the function
modes to see the new error code.
Text editor Just now, Monica can see it's got a different style code completion as well that wasn't
available in the past and so on.
So this is Monica.
So this is what the wizard can do, where you can now configure your note read instance by going through
a series of questions and providing answers, and therefore configuring your instance of note read without
a risk of making a mistake in the configuration.
So just to wrap it up here.
Remember, before you go ahead and use the widget, create a backup copy of your settings, file and
every now and then also create a backup copy of your Flo's file just in case you need to revert back
to an earlier version of your flukes.