npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

oncloud.admin

v3.4.13

Published

The adapter opens a webserver for the oncloud admin UI.

Downloads

3

Readme

Logo

oncloud.admin

NPM version Downloads

NPM

Build

node node_modules/gulp/bin/gulp default

User interface for configuration and administration.

Using common.localLink

  • %ip% - oncloud ip address (address of the admin)
  • %secure% or %protocol% - read from native.secure the value and use http or https
  • %web_protocol% - looking for the first instance of web (e.g. web.0) and get "native.secure" from "system.adapter.web.0"
  • %instance% - instance of the adapter
  • %someField% - get someField from "native" of this adapter instance
  • %web.0_bind% - get native.bind from "system.adapter.web.0"
  • %native_someField% - get someField from "native" of this adapter instance

Scheduled restart

Some adapters re not stable or connection disappear after one or two days. To fix this there is a scheduled restart setting. To activate scheduled restart just define CRON condition when to restart adapter.

It is suggested to restart in the night, when no one use the adapter, e.g. "0 3 * * *" - at 3:00 every day.

Let's Encrypt Certificates

Let’s Encrypt is a free, automated, and open certificate authority brought to you by the non-profit Internet Security Research Group (ISRG).

You can read about Let’s Encrypt here.

Some installations use Dynamic DNS and Co to get the domain name and to reach under this domain name own web sites. oncloud supports automatic request and renew of certificates from Let’s Encrypt Organisation.

There is an option to activate free certificates from Let’s Encrypt almost in every adapter, that can start some web server and supports HTTPS.

If you just enable the using of certificates and will not activate an automatic update the instance will try to use stored certificates.

If the automatic update is activated the instance will try to request certificates from Let’s Encrypt and will automatically update it.

The certificates will be first requested when the given domain address will be accessed. E.g you have "sub.domain.com" as address, when you try to access https://sub.domain.com the certificates will be first requested and it can last a little before first answer will come.

The issuing of certificates is rather complex procedure, but if you will follow the explanation you will easy get free certificates.

Description:

  1. The new account will be created with given email address (you must set it up in system settings)
  2. Some random key will be created as password for the account.
  3. After the account is created the system starts on port 80 the small web site to confirm the domain.
  4. Let's encrypt use always port 80 to check the domain.
  5. If port 80 is occupied by other service see point 4.
  6. After the small web server is up the request to get certificates for given domains (system settings) will be sent to the Let's encrypt server.
  7. Let's encrypt server sends back some challenge phrase as answer on the request and after a while tries to read this challenge phrase on "http://yourdomain:80/.well-known/acme-challenge/"
  8. If challenge phrase from our side comes back the Let's encrypt server send us the certificates. They will be stored in the given directory (system settings).

Sounds complex, but everything what you must do is to activate checkboxes and specify your email and domain in system settings.

The received certificates are valid ca. 90 days. After the certificates are received the special task will be started to automatically renew the certificates.

The topic is rather complex and 1000 things can go wrong. If you cannot get certificates please use cloud service to reach your installation from internet.

Let's encrypt works only from node.js version>=4.5

Todo

  • move html tooltips to materialize tooltips
  • tiles for hosts (additionally to table - low prior)
  • tiles for instances (additionally to table - low prior)

Used icons

This project uses some icons from Flaticon: