To set the server date and time, we must run the following (for example, we will use the Madrid time zone): sudo ln -fs share zoneinfo etclocaltime.sudo dpkg-reconfigure –frontend noninteractive tzdata
Configuring system service for n8n
We will set up a background startup service for n8n, to automatically start n8n when the server reboots or some unexpect error occurs.
We have set the memory and spe
Limits ( LimitNOFILE , LimitNPROC and LimitCORE ) very lax (without limits), since n8n can also have very memory-intensive processes, always depending on the amount of data we query.
Since the server is dicat and this is the office 365 database only major service we will have running in the background, we can allow n8n to use as much CPU and RAM as possible.
Note: Only the core (or kernel ) of
The operating system will limit the n8n service in case of very sudden use of CPU or memory, so as not to disrupt the operation of the operating system at a basic level.
We see that the user that runs this multi-site catering: the role of digital tools to streamline service (in User=n8n ) is call n8n (we will create it later). It is very important to run n8n without being superuser (or root ), to minimize permissions and not grant too many user privileges.
Of course, user n8n does not have
Any access to superuser commands, that is, he is not part of the wheel or sudoers groups , nor will he have any special access in etcsudoers.d .
Setting environment variables
Environment variables help n8n to boot with specific specifications. To save the environment variables, we will do so in another configuration file for this service.
We will carefully read the comments regarding each of the variables, to know the context.
Remember to replace yourdomain.com with usa data the domain of your choice.
It is also very important to read the documentation on environment variables to learn more about useful variables and the details of each of them.