New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details
Socket
Book a DemoSign in
Socket

@aikosia/automaton-daemon

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@aikosia/automaton-daemon

a daemon which manage browser automaton in server

latest
Source
npmnpm
Version
1.0.1
Version published
Maintainers
1
Created
Source

AUTOMATON DAEMON
A Daemon which Manage Browser For Automaton

npm-publish Branches Functions Lines Statements Jest coverage

INTRODUCTION

PLEASE FOLLOW BELOW TUTORIAL ONE TIME setup daemon module.

For this to work, you need to create a .env file at your root project with following variables:

AUTOMATON_DAEMON_HOST=
AUTOMATON_DAEMON_PORT=

AUTOMATON_DEV_PROTOCOL_RANGE=

AUTOMATON_SUPABASE_URL=
AUTOMATON_SUPABASE_KEY=

LINUX SERVER

SETUP DAEMON

  • Fetch source code project automaton into your server
git clone [url_project]
  • Run following command on root directory:
npm install --verbose
  • Link to npm global packages directories
npm install . -g

SETUP PM2 - KEEP ALIVE WHEN REBOOT

  • please install pm2 on your server using:
npm install -g pm2
  • To generate the startup script, simply run the following command:
pm2 startup

follow the guide based on the output, until you copy and run the script as describe by the output.

To confirm that the PM2 startup service is up and running under systemd, run the following command (replace the pm2-[user].service with the actual name of your service, check the output of the previous command):

systemctl status pm2-root.service
  • Next, you want to start your Node.js applications using PM2 as follows. If you already have them up and running, started via PM2, you can skip this step:
pm2 start npm --name "automaton-daemon" -- run "start"
  • Next, you need to register/save the current list of processes you want to manage using PM2 so that they will re-spawn at system boot (every time it is expected or an unexpected server restart), by running the following command:
pm2 save

additional, pm2 cleardump for unsaved

  • Finally, you need to test if the setup is working fine. Restart your system, and check if all your Node.js processes are running under PM2.
pm2 ls
or
pm2 status

Keywords

aikosia

FAQs

Package last updated on 12 May 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts