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

medic-builds-repo

v0.3.0

Published

Medic's build repository ddocs

Downloads

35

Readme

medic-builds-repo

Design doc for builds repository.

DDOCS are pushed up by travis with a specific name. These are then pulled back down by api and deployed by horticulturalist.

Design Doc requirements

Naming scheme

Three valid examples: medic:medic:3.0.0-beta.1, medic:medic:3.0.0, medic:medic:my-awesome-feature-branch.

The first two chunks between : is the namespace and the application name respectively. The namespace is just that: it has no logic relevant and is just used to scope things. The application name maps to the original ddoc name. It is what will be used to determine what to call the ddoc when deploying it.

The next section is either the version or the branch. We support both "released" versions (1.2.3) or and "pre-release" versions (1.2.3-beta.4). The pre-release label can be whatever you like. We also support an arbitrary branch name.

Metadata

There needs to be a build_info property in the ddoc:

{
    "build_info": {
        "namespace": "medic",
        "application": "medic",
        "version": "3.0.0",
        "time": "2018-04-09T07:48:27.015Z",
        "author": "travis-ci"
    }
}

Usage

All usage is through the builds/releases view.

Usage is documented via the ddoc integration test, showing how to use the view using the PouchDB library. Other libraries (or straight curl) will be similar.

Quick notes:

  • use startkey and endkey to filter the view to get what you want.
  • releases and pre-releases are sorted by the major / minor / patch / pre-releasse number
  • branches are sorted newest branch first

Testing

You need grunt. To run the integration tests you need CouchDB (1.x or 2.x).

Run the unit tests with grunt unit.

To also run the integration tests call grunt test. You need to pass in the URL of the CouchDB database you want to run the tests on. The URL must contain any basic auth required. The DB doesn't have to yet exist. The tests will destroy and re-create this DB when running the tests:

TEST_URL=http://admin:pass@localhost:5984/builds-test grunt test

Deployment

The DDOC can be built with grunt build.

Automatic deployment to the build server is handled by Travis, when a branch is merged to master. See: https://github.com/medic/medic-builds-repo/blob/master/scripts/pushToServer.js