WEBVTT

00:00.000 --> 00:10.840
Our next speaker is Jose Miguel, and he's talking about his six months with Nick's

00:10.840 --> 00:13.880
and Devon, round of applause for the speaker.

00:13.880 --> 00:18.920
Good morning, and welcome to this talk.

00:18.920 --> 00:26.960
I'm Jose Miguel, thank you for the introduction, I work for the software engineer for

00:26.960 --> 00:30.360
the website's scalar in Valencia and Spain.

00:30.360 --> 00:36.920
I've been on Nick's use for Nick's use for more than four years, actually I started

00:36.920 --> 00:39.440
just before the pandemic.

00:39.440 --> 00:46.640
So while I was in lockdown, it was challenging just to do interviews with soon, without knowing

00:46.640 --> 00:51.960
how to properly set up my computer, but fortunately those times have gone.

00:51.960 --> 00:56.000
You can find me on social networks with J.M.D.F.

00:56.000 --> 01:06.840
This talk is about what I did for the last, now more than six months, migrating

01:06.840 --> 01:15.320
a Linux project that I have set up on Nick's source into a MacBook OS X because by company

01:15.320 --> 01:21.600
policy, I was not allowed to use it because we needed to run some private

01:21.600 --> 01:26.600
software that was available on Linux.

01:26.600 --> 01:33.360
The second motivation that I had was I need to spend a lot of time on OS X, but I don't want

01:33.360 --> 01:38.360
to miss Nick's source.

01:38.360 --> 01:45.480
Some context, it was not the first time I had to work with MacBook, I tried the other

01:45.480 --> 01:52.600
people at a package manager for OS X, like Homebrew, MacBooks, like a source that is

01:52.600 --> 01:58.440
natively for net BSD, but it also works on OS X, but I wasn't particularly happy

01:58.440 --> 02:05.880
with that experience, I always found some problems that I didn't like too much, because

02:05.880 --> 02:12.440
I was happy on Nick's and Nick's source, I knew that there was an option to run it for

02:12.440 --> 02:17.160
Darwin, OS X platform, I decided to give it a go.

02:17.160 --> 02:23.800
For some time, I was having a second life at work where we have the official repository,

02:23.800 --> 02:29.040
but I was reproducing that repository with Nick's.

02:29.040 --> 02:34.920
I started working with GoLang and Node.js projects, and that was relatively straightforward.

02:34.920 --> 02:41.720
Just follow with the official documentation in the Nick's website, I also allow to work

02:41.720 --> 02:46.440
with the typical Nick's here, let's see it there.

02:46.440 --> 02:53.600
So now I wanted to reuse as much as possible, because I invested some time on getting that

02:53.600 --> 02:55.600
done.

02:55.600 --> 03:00.720
Yeah, I was happy with the simple setup, because it was relatively straightforward to jump

03:00.800 --> 03:05.680
into different projects, nowadays we need to work with different technologies, it's not

03:05.680 --> 03:10.720
likely in the old days where I used to spend almost of your time doing C development or

03:10.720 --> 03:17.920
Java or .NET, and now we need to do kind of that development, but also do some operations,

03:17.920 --> 03:20.800
some infrastructure, it's a great city there.

03:20.800 --> 03:28.720
Yeah, what I had, I wanted to be portable, not only from Linux laptop, but Macbook, also, I wanted

03:28.800 --> 03:33.600
to share it with MacoLix.

03:33.600 --> 03:36.120
So the journey has started.

03:36.120 --> 03:46.520
Yes, first thing is, I need the Nick's, for that, I decided to go, that was my second

03:46.520 --> 03:47.520
time.

03:47.520 --> 03:53.160
With the 10-minute assistance installer, previously I used the official Nick's installer,

03:53.240 --> 04:01.560
but I had problems with OSX, and that particular case was a Mac mini running in the

04:01.560 --> 04:08.280
interlocutor, because every minute I upgrade, I had almost just to start from scratch.

04:08.280 --> 04:14.800
The upgrade didn't work smoothly, I had to jump into rescue mode, etc., so I wasn't very happy.

04:14.800 --> 04:19.080
The terminus assistance started, they promised that they survived the upgrades, and that's

04:19.240 --> 04:20.080
true.

04:20.080 --> 04:26.080
I did two upgrades with no issues.

04:26.080 --> 04:37.080
Then, I went for a mini-monset app, getting the smaller configuration to get a working

04:37.080 --> 04:39.080
Nick's station.

04:39.080 --> 04:44.080
That's in mind, because I wanted to encourage MacoLix to use it.

04:44.080 --> 04:50.680
The good thing about Nick's is that it can call if with your existing setup.

04:50.680 --> 04:55.080
So if you are used to a way of working, like, I don't know, using the social with plenty

04:55.080 --> 05:01.080
of plugins, you don't need to port it into the Nick's configuration, just keep it that

05:01.080 --> 05:06.640
way, and slowly, the more comfortable you feel with the tune, you can slowly narrate it,

05:06.640 --> 05:14.040
and benefit from the features that Nick's provides.

05:14.040 --> 05:20.040
Yeah, just running the command is I applied a configuration, I have Macbook on a working

05:20.040 --> 05:23.040
state.

05:23.040 --> 05:28.400
Because I think it's really fast, honestly, it was done in 10 minutes when normally setting

05:28.400 --> 05:36.200
up a new laptop when I was changing projects to half a day or a day, this time I decided

05:36.200 --> 05:40.040
just to go for a home manager to manage my user configuration.

05:40.040 --> 05:47.040
Previously on Nick's, I was happy with the standard configuration, just system white.

05:47.040 --> 05:56.040
I was trying different approaches like Stowe or Chamois, similar tools, just to manage

05:56.040 --> 05:59.040
my dot files.

05:59.040 --> 06:03.040
But because I finished it after 10 minutes, I decided to leave.

06:03.040 --> 06:08.040
I have the rest of the afternoon, and probably MacoLix or MacoLix are not going to complain,

06:08.040 --> 06:11.040
because it looks like I'm working.

06:11.040 --> 06:16.040
So I left home manager in the next hour, and I have to say that is straightforward.

06:16.040 --> 06:20.040
Yes, follow the destruction, to get it working.

06:20.040 --> 06:27.040
And most of the time you spend it just broke with the documentation, finding the right option

06:27.040 --> 06:33.040
to get what you want to map or to configure.

06:34.040 --> 06:41.040
Please, Nick, so you said, I was, I knew about DRAMF.

06:41.040 --> 06:49.040
Honestly, you don't need to use it, but I highly recommend it, because it simplifies your life a lot.

06:49.040 --> 06:59.040
It can replace NVM, all those funny scripts to manage different projects, versions, etc.

07:00.040 --> 07:06.040
Also, it saves me a lot of time, because I don't need to repeat this in common,

07:06.040 --> 07:09.040
like load source, these environments, etc.

07:09.040 --> 07:11.040
With DRAMF, I got that for free.

07:11.040 --> 07:14.040
And I wanted to keep it.

07:19.040 --> 07:24.040
It's a sort of found ways working with Nick, because the submission before,

07:24.040 --> 07:27.040
the hello world is always very easy to follow.

07:28.040 --> 07:31.040
We're not part of the goal and not the knowledge projects.

07:31.040 --> 07:34.040
It was relatively straightforward.

07:34.040 --> 07:40.040
But as soon as we, I learned it on more complex projects where we had to mix different languages,

07:40.040 --> 07:47.040
the documentation was not clear enough, so that they can invest that time,

07:47.040 --> 07:52.040
but I'm going to have a very hard time convincing people to use it.

07:53.040 --> 07:59.040
So, just posting for the different solutions I discovered about DRAMF,

07:59.040 --> 08:05.040
looked on paper like the right solution, the clarity,

08:05.040 --> 08:08.040
if possible, composable development environments with Nick.

08:08.040 --> 08:13.040
So something like working with Docker, without Docker.

08:13.040 --> 08:17.040
So there were some.

08:18.040 --> 08:22.040
Well, of course, you need to store different in it,

08:22.040 --> 08:25.040
but because I have home manager, I just added that package,

08:25.040 --> 08:27.040
I play the configuration, and I got it.

08:27.040 --> 08:35.040
I market an optional, because I don't use that particular command as frequently as in the beginning,

08:35.040 --> 08:39.040
because I just ported most of the projects we are working with.

08:39.040 --> 08:44.040
But we need to modify that file.

08:44.040 --> 08:49.040
In it, it's going to create several files like techniques,

08:49.040 --> 08:58.040
a flag, and a lock file, and a M3RC for learning special variables.

08:58.040 --> 09:04.040
And I'll leave a comment every time you load the environment,

09:04.040 --> 09:06.040
just pay attention to the messages.

09:06.040 --> 09:11.040
Because, for example, when I was working with our telephone player,

09:11.040 --> 09:15.040
it was not for free, because it was the time to change the licenses.

09:15.040 --> 09:19.040
So it stopped working, stack trace,

09:19.040 --> 09:22.040
yeah, we can occupy most of the display.

09:22.040 --> 09:24.040
But there is a very clear message that,

09:24.040 --> 09:27.040
okay, it seems that this software is not free,

09:27.040 --> 09:29.040
so you need to do this.

09:29.040 --> 09:31.040
Follow the example and it works.

09:31.040 --> 09:34.040
For example, when they upgrade a new version, it's said that,

09:34.040 --> 09:37.040
okay, you need to upgrade your inputs, just run this command,

09:37.040 --> 09:40.040
and it's going to work again.

09:40.040 --> 09:46.040
So, when you run the finit,

09:46.040 --> 09:51.040
or you have the modify version of that file,

09:51.040 --> 09:54.040
they have done a very good work,

09:54.040 --> 09:57.040
just document in the different options.

09:57.040 --> 10:00.040
But I'm going to focus on the ones that have been more relevant to us

10:00.040 --> 10:02.040
for the last months.

10:02.040 --> 10:03.040
Oh, packages.

10:03.040 --> 10:07.040
But that's the key, is you declare essentially your dependencies.

10:08.040 --> 10:11.040
It has been a pain in some projects,

10:11.040 --> 10:15.040
because people didn't update the gridmfile,

10:15.040 --> 10:17.040
so the data, the dependency,

10:17.040 --> 10:19.040
they don't say anything about it,

10:19.040 --> 10:21.040
which is covered in the hardware,

10:21.040 --> 10:23.040
is just expecting that line,

10:23.040 --> 10:25.040
you can see everything that you need.

10:25.040 --> 10:30.040
And because if you don't want to use the event,

10:30.040 --> 10:35.040
and need, okay, you can find those software on your own,

10:35.040 --> 10:37.040
and install it, it should work.

10:37.040 --> 10:39.040
Because one motivation that I had is,

10:39.040 --> 10:43.040
until doing a full migration,

10:43.040 --> 10:46.040
we don't want to force people to use this tool.

10:46.040 --> 10:48.040
We want them to be productive,

10:48.040 --> 10:51.040
and keep working the way they're doing.

10:54.040 --> 10:57.040
I'll further mention that those packages

10:57.040 --> 11:00.040
can be listed on the set.nixors.org,

11:00.040 --> 11:05.040
just make sure that it's available for the Joraki architecture.

11:05.040 --> 11:08.040
Another thing, language is,

11:08.040 --> 11:10.040
I love that that one,

11:10.040 --> 11:13.040
because previously on the package section,

11:13.040 --> 11:16.040
I had to list all the different tooling,

11:16.040 --> 11:18.040
like I want to use this language.

11:18.040 --> 11:20.040
I don't know.

11:20.040 --> 11:24.040
Ok, it's all ok, it's all ok,

11:24.040 --> 11:26.040
or they have this built tool, okay,

11:26.040 --> 11:28.040
added the tool.

11:29.040 --> 11:31.040
Now I need the link,

11:31.040 --> 11:32.040
etc.

11:32.040 --> 11:35.040
So, it becomes a very long list.

11:35.040 --> 11:38.040
With language, it's just enabled.

11:38.040 --> 11:40.040
The default option,

11:40.040 --> 11:42.040
normally quite good.

11:42.040 --> 11:44.040
Then you get the compiler,

11:44.040 --> 11:46.040
everything that I mentioned for free.

11:46.040 --> 11:49.040
I do need to care about it anymore.

11:49.040 --> 11:53.040
And of course, on the official event website,

11:53.040 --> 11:55.040
you can find extra options,

11:55.040 --> 11:57.040
like let's say that you need a particular version,

11:57.040 --> 11:59.040
or a particular package,

11:59.040 --> 12:01.040
or some flux, etc.

12:01.040 --> 12:04.040
If they are supported, you can use it.

12:04.040 --> 12:06.040
With that way,

12:06.040 --> 12:08.040
so very cleanly,

12:08.040 --> 12:11.040
the problem of working with different languages,

12:11.040 --> 12:15.040
without digging too much into the next language.

12:15.040 --> 12:18.040
And scripts.

12:18.040 --> 12:21.040
That's an intersection that I like a lot.

12:21.040 --> 12:25.040
You can see them as kind of areas.

12:25.040 --> 12:28.040
So you put a fancy name or something that is meaningful,

12:28.040 --> 12:30.040
and you don't need to worry too much about the details,

12:30.040 --> 12:32.040
or what's doing behind.

12:32.040 --> 12:34.040
Most of our players,

12:34.040 --> 12:37.040
we have, we maintain make files.

12:37.040 --> 12:40.040
That has been worked very well,

12:40.040 --> 12:44.040
because you have a clear way of what you need to do.

12:44.040 --> 12:46.040
We highlighted the main task,

12:46.040 --> 12:49.040
typically make build or make run.

12:49.040 --> 12:50.040
For the rest,

12:50.040 --> 12:53.040
the make file was relatively easy to expect.

12:53.040 --> 12:55.040
We wanted to keep that thing.

12:55.040 --> 12:57.040
But with scripts,

12:57.040 --> 13:01.040
I was able just to mimic that behavior.

13:01.040 --> 13:03.040
Just following,

13:03.040 --> 13:07.040
I had that they have on the official documentation.

13:07.040 --> 13:10.040
I was able just to print automatically,

13:10.040 --> 13:11.040
all the scripts.

13:11.040 --> 13:13.040
So when you land on the project,

13:13.040 --> 13:14.040
you load the environment,

13:14.040 --> 13:15.040
and then you see that they,

13:15.040 --> 13:19.040
okay, this is the important task that I need to do,

13:19.040 --> 13:21.040
or to follow, to work on this project.

13:22.040 --> 13:26.040
I highly recommend you to invest some time on it.

13:28.040 --> 13:30.040
Services.

13:30.040 --> 13:31.040
Services.

13:31.040 --> 13:34.040
Well, it's provides an abstraction

13:34.040 --> 13:38.040
to work with different tools like it can be

13:38.040 --> 13:41.040
a database, a QC system, a web server,

13:41.040 --> 13:43.040
a city that is support,

13:43.040 --> 13:44.040
the event,

13:44.040 --> 13:47.040
supports plenty of the most common services

13:47.040 --> 13:48.040
of this kind of tooling.

13:48.040 --> 13:50.040
Here I'm providing an example.

13:50.040 --> 13:53.040
We are for this project.

13:53.040 --> 13:56.040
I want a gross SQL database.

13:56.040 --> 13:59.040
I want to launch a web server,

13:59.040 --> 14:03.040
because probably serving some kind of front-end stuff.

14:05.040 --> 14:07.040
With this aspect,

14:07.040 --> 14:10.040
I was able just to sort the typical program

14:10.040 --> 14:15.040
that a 3 developer was managing this tooling in a different way.

14:15.040 --> 14:17.040
If they know how to do it, it's okay.

14:17.040 --> 14:19.040
But eventually there are some problems that they,

14:19.040 --> 14:23.040
or I need your help because this is not working for me.

14:23.040 --> 14:25.040
Let's dig into the problem.

14:25.040 --> 14:28.040
What's the version that you are using?

14:28.040 --> 14:31.040
Why are you installing this way?

14:31.040 --> 14:36.040
I wanted to stop supporting customized setups

14:36.040 --> 14:40.040
and just to provide a standard for everyone.

14:40.040 --> 14:42.040
The collaborative,

14:42.040 --> 14:45.040
it works the same way on Linux,

14:46.040 --> 14:48.040
or transparent Linux on OS X,

14:48.040 --> 14:52.040
because previously when I was on Linux,

14:52.040 --> 14:56.040
most of these services are managed with systemD,

14:56.040 --> 14:58.040
probably all my colleagues,

14:58.040 --> 14:59.040
the way I use it,

14:59.040 --> 15:00.040
dedicated the message scripts,

15:00.040 --> 15:01.040
etc.

15:01.040 --> 15:03.040
So everyone was on their own.

15:03.040 --> 15:05.040
With this approach,

15:05.040 --> 15:08.040
everything is working on the same way.

15:08.040 --> 15:12.040
We didn't find any surprises.

15:16.040 --> 15:18.040
Benefits.

15:18.040 --> 15:20.040
Okay.

15:20.040 --> 15:23.040
Tom, just 30,000 over there,

15:23.040 --> 15:25.040
is that all your works,

15:25.040 --> 15:29.040
when you have derived inable.

15:29.040 --> 15:32.040
Otherwise, you need to run the venture,

15:32.040 --> 15:35.040
which is going to land you on an isolated environment

15:35.040 --> 15:37.040
with Vashil,

15:37.040 --> 15:40.040
only access to the dependency that you have

15:40.040 --> 15:42.040
declared on the package section,

15:42.040 --> 15:43.040
etc.

15:44.040 --> 15:46.040
So, yeah.

15:48.040 --> 15:50.040
You're going to miss all the customization

15:50.040 --> 15:51.040
that you have outside,

15:51.040 --> 15:52.040
but it's okay.

15:52.040 --> 15:55.040
We want you to have a very simple project.

15:55.040 --> 15:58.040
Well, the reproducible

15:58.040 --> 16:02.040
in the sense that if a friend or colleague

16:02.040 --> 16:04.040
clones the repository,

16:04.040 --> 16:09.040
they're going to see the same behavior,

16:09.040 --> 16:11.040
the launch of the web server,

16:11.040 --> 16:13.040
then you're going to start

16:13.040 --> 16:15.040
as soon as it's not colliding with a

16:15.040 --> 16:19.040
a port or anything similar.

16:19.040 --> 16:21.040
Well, that gave us a

16:21.040 --> 16:23.040
push improvement,

16:23.040 --> 16:25.040
because instead of waiting,

16:25.040 --> 16:29.040
several tens of minutes to get something in

16:29.040 --> 16:30.040
working is,

16:30.040 --> 16:32.040
you just do the,

16:32.040 --> 16:35.040
the equivalent of our make build

16:35.040 --> 16:39.040
in less than a minute of working.

16:40.040 --> 16:41.040
So,

16:41.040 --> 16:42.040
set it in half.

16:42.040 --> 16:43.040
I have instructions.

16:43.040 --> 16:45.040
Yeah, I think that in the event

16:45.040 --> 16:47.040
they have done a very good work,

16:47.040 --> 16:50.040
just crafting that

16:50.040 --> 16:52.040
five,

16:52.040 --> 16:55.040
where you only can

16:55.040 --> 16:56.040
about services,

16:56.040 --> 16:58.040
scripts, two link packages,

16:58.040 --> 17:00.040
but you,

17:00.040 --> 17:03.040
they are high in the complexities of the next language.

17:03.040 --> 17:07.040
And,

17:07.040 --> 17:11.040
I like that.

17:11.040 --> 17:12.040
Just over there,

17:12.040 --> 17:14.040
we got the,

17:14.040 --> 17:17.040
we have provided the enough context

17:17.040 --> 17:18.040
to work on the project.

17:18.040 --> 17:20.040
You don't need to keep it on your head,

17:20.040 --> 17:21.040
which is,

17:21.040 --> 17:22.040
which is,

17:22.040 --> 17:23.040
tiring,

17:23.040 --> 17:28.040
prone to error.

17:28.040 --> 17:29.040
Unfortunately,

17:29.040 --> 17:30.040
there were some bad parts,

17:30.040 --> 17:32.040
as well.

17:33.040 --> 17:34.040
On next packages,

17:34.040 --> 17:36.040
they have done an amazing work,

17:36.040 --> 17:40.040
14 and making plenty of software to be available.

17:40.040 --> 17:44.040
But not all packages are available for OSX,

17:44.040 --> 17:45.040
or for the architecture,

17:45.040 --> 17:47.040
or the platform working in.

17:47.040 --> 17:48.040
Particularly,

17:48.040 --> 17:49.040
I had a bad time,

17:49.040 --> 17:51.040
because I needed to use a tool

17:51.040 --> 17:53.040
to do some scan on,

17:53.040 --> 17:56.040
Linux images.

17:56.040 --> 17:59.040
It was only available on Linux.

17:59.040 --> 18:00.040
So,

18:00.040 --> 18:02.040
I couldn't use Mac for that.

18:02.040 --> 18:05.040
Give me the skills to try to get back to Linux,

18:05.040 --> 18:06.040
but for 12,

18:06.040 --> 18:08.040
video work.

18:08.040 --> 18:11.040
When you go to this,

18:11.040 --> 18:12.040
for example,

18:12.040 --> 18:14.040
on the set.nix.org,

18:14.040 --> 18:17.040
and you find your package on the overview,

18:17.040 --> 18:20.040
they mention the architecture,

18:20.040 --> 18:24.040
and the platforms that packages is available.

18:24.040 --> 18:26.040
All the different versions.

18:26.040 --> 18:27.040
Yeah,

18:27.040 --> 18:29.040
it seems that the package,

18:29.040 --> 18:31.040
that's over,

18:31.040 --> 18:35.040
or this process on the other channels.

18:35.040 --> 18:37.040
In this situation,

18:37.040 --> 18:38.040
it was,

18:38.040 --> 18:41.040
we don't know exactly the record,

18:41.040 --> 18:44.040
but we wanted to use the latest version of go.

18:44.040 --> 18:48.040
We knew that it was available on the,

18:48.040 --> 18:50.040
available on the next channel,

18:50.040 --> 18:52.040
but for those of them,

18:52.040 --> 18:55.040
about just two minor versions behind.

18:56.040 --> 18:57.040
Photonative was,

18:57.040 --> 18:59.040
after a couple of weeks.

18:59.040 --> 19:01.040
So,

19:01.040 --> 19:03.040
I try to make it as fast as I go.

19:03.040 --> 19:05.040
Time for questions.

19:05.040 --> 19:06.040
All right.

19:06.040 --> 19:07.040
Thank you.

19:07.040 --> 19:08.040
Thank you.

19:12.040 --> 19:14.040
We still have a bit more time for questions.

19:14.040 --> 19:16.040
ahead of that,

19:16.040 --> 19:19.040
the speaker for the next talk,

19:19.040 --> 19:22.040
the remote execution with back to Claudio Blake.

19:22.040 --> 19:23.040
All right.

19:23.040 --> 19:26.040
We're going to try to have somebody talk to you in the break now,

19:26.040 --> 19:28.040
or maybe during the next talk.

19:28.040 --> 19:29.040
All right.

19:29.040 --> 19:30.040
Thank you.

19:32.040 --> 19:33.040
Okay.

19:33.040 --> 19:34.040
Yeah.

19:34.040 --> 19:35.040
Okay.

19:35.040 --> 19:37.040
So, is there a question?

19:37.040 --> 19:38.040
Yeah.

19:38.040 --> 19:40.040
You mentioned there are relatives around services,

19:40.040 --> 19:41.040
like post-grads.

19:41.040 --> 19:42.040
He's really different.

19:42.040 --> 19:45.040
What happens if I have two questions here, actually?

19:45.040 --> 19:47.040
What happens if I have one question?

19:47.040 --> 19:51.040
What happens if I run?

19:51.040 --> 19:52.040
Two projects is the same time.

19:52.040 --> 19:55.040
Each of them requiring both your stuff there are.

19:55.040 --> 19:57.040
Will they class on a board?

19:57.040 --> 19:58.040
Yes.

19:58.040 --> 19:59.040
Can I configure that?

19:59.040 --> 20:00.040
Yeah.

20:00.040 --> 20:01.040
Exactly.

20:01.040 --> 20:02.040
So, I'll give you the question.

20:02.040 --> 20:04.040
Talking about the services,

20:04.040 --> 20:06.040
the question is about the,

20:06.040 --> 20:11.040
can I want two players at the same time that they are using the same service?

20:11.040 --> 20:13.040
And if they are going to collide?

20:13.040 --> 20:14.040
Yes.

20:14.040 --> 20:17.040
For example, for the post-grads,

20:17.040 --> 20:18.040
maybe...

20:19.040 --> 20:23.040
You can try to customize it just to use the same board,

20:23.040 --> 20:26.040
but at a different database, because that's a way issue door.

20:26.040 --> 20:28.040
But clearly for NGNX,

20:28.040 --> 20:32.040
no, you'll need to have declared a different post.

20:32.040 --> 20:35.040
I have to say that I discovered that recently,

20:35.040 --> 20:39.040
but the thing provides, probably with the latest version,

20:39.040 --> 20:41.040
a different talk, local.

20:41.040 --> 20:45.040
So, that's why it's not going to be,

20:46.040 --> 20:48.040
I have to keep the repository.

20:48.040 --> 20:51.040
It's intended to have your customizations.

20:51.040 --> 20:52.040
So, over there, you provide,

20:52.040 --> 20:55.040
I want it to use this board so I can do exactly that.