bsodium / slashboard-pulsar

A simple dashboard to keep track of all your active devices/servers

Hey there 👋

📖 I'm a Software developer and former computer science student at ENSEEIHT, interested in 3D rendering, computer graphics and physics simulations. Feel free to explore my projects, contributions are welcome !

🚀 Currently working on the Cron project, drop a star if you want to keep track of it / contribute with some ideas.

slashboard-pulsar's Issues

Uninstall

How do you uninstall this and all its packages?

Ran the auto installer and getting error

Error

The authenticity of host 'github.com (140.82.114.3)' can't be established.ted to /pulsar/Slashboard-pulsar/node_modules/.staging/type-is-546f807e (97ms)

Improve security

Improvement of the security would be great, I'm up to helping it along or even do it myself, I'm opening this issue so we can discuss it.

NPM error

[ ......] | extract:mongoose: sill extract [email protected] extracted to /var/www/Slashboard-pulsar/node_modules/.staging/mongoose-0eab8500 (2235ms)
npm WARN [email protected] No repository field.

npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/izigibran/omit-deep.git
npm ERR!
npm ERR! Host key verification failed.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-09-21T15_45_47_154Z-debug.log

Reinforce the need for TLS when exposing the server to the internet

Contact Details

[email protected]

Describe your idea

Reinforce the need for TLS when exposing the server to the internet, the server is now more secure with the ephemeral tokens but the read-me still doesn't warn about the need to use a reverse proxy with TLS when exposing the server to the internet as it is still very much insecure to exchange the credentials over plain HTTP. I can help with this if you need.

Code of Conduct

• I agree to follow Pulsar's Code of Conduct

[Bug]: Can't run Pulser

Contact Details

[email protected]

What happened ?

pm2 shows an error and cannot be executed.
I was able to run it in the previous version.

How can we reproduce it ?

run "pm2 start ecosystem.config.js --env production"

Relevant log output

0|Pulsar  | WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
0|Pulsar  | WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
0|Pulsar  | WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
0|Pulsar  | WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
0|Pulsar  | { Error: Cannot find module 'node:crypto'
0|Pulsar  |     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
0|Pulsar  |     at Module.Hook._require.Module.require (/usr/local/lib/node_modules/pm2/node_modules/require-in-the-middle/index.js:61:29)

Code of Conduct

• I agree to follow Pulsar's Code of Conduct