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

generator-apib

v1.1.5

Published

Generate API Workflow

Downloads

5

Readme

APIB Workflow Generator

This generator will create a vagrant box configuration, clone in a base box config, and a base api blueprint. This is a development workflow for a Service Oriented Architecture

First you should cache the box on your local machine by running:

vagrant box add camdesigns/basebox

To install generator-apib from npm, run:

npm install -g generator-apib

This may not be recommended, but I did it:

This will allow the generator to modify your hosts file for you. Otherwise, edit your /etc/hosts file as recommended by the generator each time, this will allow all of the virtual hosts to render properly via nginx.

sudo chown <username> /etc/hosts

Initiate the generator:

yo apib

The VM should be running or you can run vagrant up from the base-box dir

  • you can now ssh is and work with your project
  • base.dev api.base.dev .. etc. are now all available URLs

Requirements

  • vagrant 1.6.3+
  • virtualbox 4.3.14+

The Conventions established will create a directory structure similar to this:

base-box
│   README.md
│   Homestead.yaml (symlinked to base-box-config/Homestead.yaml)
│
└─── base-box-config (implementation of the box)
|        |    Homestead.yaml
|        |    readme.md
|        └─── nginx (server configuration)
|           |    base.conf
|           |    base.api.conf
|
└─── base-api-blueprint (the API Blueprint)
|       |     README.md
|       |     template.txt (used for scripting that will come later)
|       └───  resources
|             |     users.md
|
└─── base-api (your api implementation)
└─── base-ui (you ui implementation)
└─── tools (server tooling / monitoring and ui)
        └─── beanstalkd
        └─── genghis
        └─── opcache
        └─── test

Box definition ( Ubuntu 14.04 )

Troubleshooting

  • Ports 3306 and 27017 will be forwarded on the VM to the host machine to allow for Mongo and MySQL connections
  • ensure you have a ~/.ssh/id_rsa key or remap the key in the Homestead.yaml file
  • screens will be running in sudo so to see what servers / processes are running try sudo screen -ls (get familiar with screens if you are not already)

Workflow

  • In the base-box-config directory you can script your box to do all the things you need (add / configure packages, add scripts for seeding, migration, etc. so your ENV si fully reproducible everytime)
  • In the base-api-blueprint Define your API following the standards in http://apiblueprint.org/
  • In the subsequent base-? directories implement your APIs and SPAs as needed.
  • https://www.npmjs.org/package/api-mock will be running the initial mock server at mock.base.dev
  • https://www.npmjs.org/package/aglio will be running the initial docs server at docs.base.dev
  • npm install dredd is availbe for api testing
  • go HAM