Catalog npm
PACKAGE EXPLORERView in registry

@0x4447/hotpepper

npm

🌶 A SystemD config generators for NodeJS projects

0x4447cliservicesystemd
Versions collected14
Direct dependencies2From release 2.0.0
Last observed20 Oct, 22:37 UTC

README

Current package documentation

🌶 Hot Pepper

We created Hot Pepper to quickly add a NodeJS server to SystemD by setting up a custom configuration file based on the content of the package.json file and the location in which the CLI was executed.

We prefer to use SystemD, because it's built into Debian, takes care of the lifetime of the process, and uses fewer resources than other solutions on today's market. Thus, you get more CPU and RAM for your app. Not to mention that the entire server will be set to Auto Start. This way, all the servers added to SystemD are always ready when you start your server/computer.

In addition, you'll save time because you won't be hand-creating a .service for the dozens of micro services within a given project.

How to install

] sudo npm install -g @0x4447/hotpepper

How to use

] sudo hotpepper -s .

Where to get help

] hotpepper -h

What to Expect

Run the command in the directory that contains your project. If all necessary data is present in the package.json file, the tool...

  • Generates a .service file saved in the correct SystemD directory
  • The app forces SystemD to reload the service files
  • The app starts your server
  • The app tells SystemD to start your server every time the system boots

Sample of a .service file:

[Unit]
Description=example.com
Documentation=https://github.com/user/example.com
After=network.target

[Service]
EnvironmentFile=/home/admin/example.com/.env
Type=simple
User=admin
Group=admin
WorkingDirectory=/home/admin/example.com
ExecStart=/usr/bin/node bin/server
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=example.com
Restart=on-failure
RestartSec=3
KillMode=process
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target

Once complete, the app lets you know whether the process was successful.

Where are the logs?

Run this command to view the server logs: sudo tail -f /var/log/syslog. Each log entry has the name of the project attached.

The End

If you enjoyed this project, please consider giving it a 🌟. And check out our 0x4447 GitHub account, which contains additional resources you might find useful or interesting.

Sponsor 🎊

This project is brought to you by 0x4447 LLC, a software company specializing in building custom solutions on top of AWS. Follow this link to learn more: https://0x4447.com. Alternatively, send an email to hello@0x4447.email.

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 14

Collected releases
VersionPublishedDirect dependenciesOpen version
2.0.0Registry latest8 Feb 20192
1.4.171 Jul 20182
1.4.1624 Jun 20182
1.4.1523 Jun 20182
1.4.1321 Jun 20181
1.4.1221 Jun 20181
1.4.1121 Jun 20181
1.4.1021 Jun 20181
1.4.918 Jun 20181
1.4.85 Feb 20181
1.4.729 Jan 20181
1.4.629 Jan 20181
1.4.513 Jan 20181
1.4.412 Jan 20180

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
0x4447/0x4447-node-cli-hot-pepper

Shared repository data · GitHub

License detected in repository
Not collected

Repository

NOT_FOUND
0x4447/0x4447-cli-node-hotpepper

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 22:35 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:6eb110b6fa6d0f4dc7f07968b6777f0660662c2aa60fa61be7be5d5e39fe1906