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

apiwee

v0.1.11

Published

basic api key managament

Downloads

29

Readme

A fast and lightweight solution for quickly adding api keys to an Express application

Installation

$ npm install apiwee

the code to put it in

var express = require('express');
var app = express();
var apiweeConfig = {
    username: 'username', // required
    password: 'password', // required
    publicPaths: ['GET:/', 'GET:/health'], // optional
    file: __dirname + '/../myNewFileLocation' // optional, otherwise stored in node_modules/apiwee
}
var apiwee = require('apiwee')(express, app,apiweeConfig);

app.use(apiwee);

app.listen(3000);

how it works

Apiwee is added to the Express middleware functionality, where it validates from a local file (slower than memory but can be updated dynamically).

then navigate to {yourDomain}:{yourPort}/apiwee/admin and login with the credentials provided in the instantiation this will take you to the configurations page where you can define the keys and the routes. You can delete keys, add new ones, edit the key field, drag routes to the api key, and disable keys.

once your api keys are defined use them by using the header field x-api-key

username and password are shown hard-coded in the config but use your best judgement on how to pass them into the instantiation.

handling multiple instances

aws asg group

ensure that each aws instance has permissions for running the aws cli command describe-instances it also requires you to use the tags Environment and Name for the groups

below are the required fields for setting up the api keys on all instances in your aws asg group

var apiweeConfig = {
    username: 'username',
    password: 'password',
    awsRegion: 'us-east-1',
    awsEnvironment: 'development',
    awsInstanceName: 'myApp',
    protocol: 'http/https',
    port: 3000
}
var apiwee = require('apiwee')(express,app,apiweeConfig);

hard-coded ips

below is the required config for scaling your api keys across instances using their addresses Include all ips, including the address it is running on

var apiweeConfig = {
    username: 'username',
    password: 'password',
    ips: ['1.1.1.1', '1.1.1.2', '1.1.1.3'],
    protocol: 'http/https',
    port: 3000
}
var apiwee = require('apiwee')(express,app,apiweeConfig);

screenshots

login configure