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

vox-server

v0.0.3

Published

A server for the Postvox network

Downloads

8

Readme

Postvox Server

This is a basic implementation of a Postvox server. It implements (most of) the Postvox protocol. It stores its data on local disk. It doesn't do any fancy clustering.

It can be found running in the wild at http://vanilla.postvox.net.

Running in production

$ export DEBUG='vox:*'
$ export NODE_ENV='production'
$ node vox-server.js \
    --dbDir=/path/to/dir \
    --port=9001 \
    --metricsPort=9002

or

Modify pm2-process.json and:

$ pm2 start pm2-process.json
$ pm2 logs

Running in development

$ export DEBUG='vox:*'
$ export NODE_ENV='development'
$ # TODO: run fakehub
$ node vox-server.js \
    --dbDir=/path/to/dir \
    --port=9001 \
    --metricsPort=9002

Using nodemon is very convenient for development:

$ npm install -g nodemon
$ nodemon vox-server.js <flags>

Flags

Name | Example | Description :----|:--------|:----------- --dbDir | /home/user/vox-server-db | The on-disk location of the server's database. This is where message streams and metadata will be stored. --port | 9001 | The port to bind to. --metricsPort | 9002 | The port to bind the internal metrics server to. --hubUrl | http://hub.postvox.net | The URL of the Hub. The Hub is like DNS, but for users' nicknames. If you point to a different Hub, you also need to update the expected public key in vox-common/authentication.js.

TODO

  • [] Implement the rest of the protocol.
  • [] Make it easy to run fakehub in development mode.