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

pico-server

v0.4.0

Published

A lean and mean realtime api server

Downloads

57

Readme

NPM version pico-server

A lean and mean realtime api server

Features

  • mean in functionality for api server and api server only, create an api server by a config file and app sepcific api and model scripts
  • lean in process, request parsing, action routing, session handling, data loss management, logging and response rendering all in one file
  • app level database transaction
  • action and model separation to promote code reuse
  • data cache to prevent data lost
  • unique protocol design for data channel and handle large json data without unnessary parsing and stringify
  • efficent user session handling, session only persistence when pull channel dc
  • supported chained requests
  • two channel design, push and pull channel to achieve fast and realtime http server (WIP)

Installation

  1. mkdir [PROJ_DIR]
  2. cd [PROJ_DIR]
  3. sudo npm install pico-server -g
  4. npm link pico-server
  5. mkdir app # all your server code should goes here

Create a Hello World Server

  1. mkdir -p app/config app/actions # create minimal project folders
  2. touch app/config/master.json app/config/worker.json
  3. paste this to your master.json
{
    "app":{
        "name": "YOUR_PROJECT_NAME",
        "env": "dev",
        "elements": []
    },
    "worker":{
        "config": "config/worker",
        "count":1
    },
    "lib":{
    }
}
  1. paste this to your worker.json
{
    "app":{
        "name": "YOUR_PROJECT_NAME",
        "env": "dev",
        "elements": ["actions"]
    },
    "lib":{
        "webServer":{
            "mod":"web",
            "port":5678,
            "updateRate":60000
        }
    }
}
  1. vi app/index.js # create server entry point
var pico = require('pico-server');
// pico.createApp('/var/nodes/YOUR_PROJ_DIR/app', 'config/master');
pico.createApp('PATH/TO/APP/', 'CONFIG/PATH');
  1. vi app/actions/index.js
module.exports = [
    require('./foobar'),
];
  1. vi app/actions/foobar.js
function hello(session, order, cb){
	var model = session.getModel('foobar');
	model['me'] = 'world';
	session.addJob(
		G_PICO_WEB.RENDER_FULL,
		[[session.createModelInfo('foobar', 'me')]]
	);
	cb();
}
exports.setup = function(context, next){
	var web = context.webServer;
	web.route('Hello', [hello]);
    next();
};
  1. run the server in YOUR_PROJ_DIR
node app
  1. run following curl command on your local machine
curl -X POST -H "Content-Type: application/json" -d '[{"api":"Hello","reqId":1,"data":""}]' http://YOUR_SERVER_IP:5678/pull

Configuration

pico server has two types of configuration files, master process configuration and worker process configuration. every pico server must has one master process and zero to unlimited numbers of worker processes. ##Web Server Config

"webServer":{
    "mod":"web",
    "port":56789,
    "pfx":"config/dev_ssl.pfx",
    "allowOrigin":"25.107.56.189:6666",
    "secretKey":"hashash",
    "cullAge":120000,
    "delimiter":["crlf"],
    "uploadWL":["proj/mod/act1","proj/mod/act2"]
},
  • webServer: module instance name, compulsary but name can be any
  • mod: module name, compulsary, must use "web" for web server
  • pfx: ssl cert path relative to app folder, if available, https protocol will be used
  • allowOrigin: cross origin policy, if not not available, allowOrigin is set to *
  • secretKey: request hash key, optional, if not available, request hash will not be checked
  • cullAge: request time check, optional, if not available, +- 1 hour allowanceis given
  • delimiter: for client without ajax, delimiter can be added to separate response, optional
  • uploadWL: upload white list, api not in this list will be culled