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

@iztiar/iztiar-core

v0.9.0

Published

The core of the Iztiar software family

Downloads

9

Readme

Iztiar

Liminaries

Iztiar aims to form a big family of packages (and, of course, nothing less) to drive a set of sensors, actioners, scenarios, and the glue around all of these. Put in together, we so are building a home automation application, the dream of an automated home, a building supervision software, etc.

Thanks to the designed unique architecture, we do not at the moment identify any limit to the possible usages.

As of 0.x versions, we are still in the long process of drawing the future plans and evaluating implementation patterns.

In other words, though all is public and published in gthub and npmjs, nothing is really finalized, and the application still does nothing :(

At least, it is almost bug-free!

So, please be patient...

iztiar-core

iztiar-core (this package) is the very core of the whole software family. Through its command-line interface, it is expected to provide the core services required by Iztiar:

  • the coreBroker messaging bus
  • the coreController service
  • the REST API server
  • the certificate-based security framework.

Command-line interface

iztiar {start|stop|test} [--storage-dir <storage_dir>] [--loglevel <loglevel>]

It is a design decision that the command-line accept as few options as possible. The rationale is that we want the configuration be written.

The <storage_dir> option addresses the iztiar configuration file, which itself is expected to fully describe all services to be started (respectively stopped, tested).

See also:

  • the Technologies document which describes the used technologies
  • the Architecture description
  • the Taxonomy document which defines and explain the notions used here
  • , and, last, the Installation to know how to install this piece of gold :)

Some notes about the iztiar word

According to Wikipedia, Itziar may be understood as both a spain city and a female given name.

According to Etre parents, Itziar would originate from basque language, and would be appliable to both male and female persons. It would mean « champ d’étoiles » in french, or « field of stars » in english.

Other considered names were:

  • adomojs: Authomatized Domus Javascript
  • adomong: Authomatized Dom New Generation
  • or see also how NodeJS finds three new words each time we reload the page..;)

A copyright notice

First, and though lot of the code has been redesigned or rewritten, the very first code set has been shamelessly forked from Homebridge.

Second, many ideas have been taken from Jeedom.

Third, many ideas have also been pulled from other automation softwares, either current or stopped as the day...