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

vdun

v1.0.4

Published

Vagrant Docker Ubuntu Nvm

Downloads

8

Readme

VDUN

Vagrant Docker Ubuntu Nvm

Usage

Be sure you have Vagrant & Docker (Optional *See Notes) installed. Then, start everything with:

vagrant up

After the install you can check that your server is running with:

curl http://127.0.0.1:8080

Explanation

Wouldn't it be nice if you could test your nodejs projects in any node version while still using the same setup to deploy your work to both development and production environments? So when you talk virtualization so many flags are thrown in terms of options and deploy-ability. This setup streamlines that process. You don't have to worry about the ram, cpu, disk, host OS ect. This will install and run on Linux, OSX, & Windows. This enables you to utilize almost any hardware as a host machine. Vagrant is used to spin up a host container which detects if docker exists on the host machine and if not installs it. This para-container can be installed on any provider or machine that supports Vagrant or Docker.

Introducing VDUN [~Vee-Done]

The Vagrant. Docker. Ubuntu. NVM development suite.

Installing

You need to install both Vagrant & Docker on the host machine to get the best of both worlds. However, you may utilize a Docker only provider by running Docker instead of Vagrant. Proper startup occurs when running either Vagrant or Docker. Utilizing Vagrant adds overhead but enables install on systems that don't fully support docker for Linux containers (Such as Windows systems without full virtualization).

Using Node

npm install vdun

Using Git

git clone https://github.com/talkquazi/vdun

*Notice: There is currently no module entry point method to spin-up vdun using a nodejs module. npm install is not needed either. The above install methods are simply to clone the source code.

Configuring

This project comes preconfigured using node version 0.12.7. You can modify the .nvmrc file to change the version of NodeJS that gets installed. Modify Dockerfile to include your own script files. You will also need to edit process.json to configure it your project.

Advanced Usage

Build the para-container with:

vagrant up

The above command will run and install everything you need for Ubuntu 14.4 to run docker and the example server. Below is an optional method to use Docker only as a containerized provider bypassing Vagrant.

Build the docker (Optional entry point) with:

docker build .

Server/app.js

This is the super simple Node.js server. You would replace this with your own code. This test server code responds to everything with 'Hello World'. Defaults to '0.0.0.0' port 8080.

Notes

This setup is designed to run using either vagrant or docker. As such it can deploy on hosting solutions that support either vagrant or docker.

Installing both docker and vagrant on the host machine will speed up the initial vagrant bootup as the system will not have to run a virtual instance and install docker for you then. This is the ideal method to have both vagrant and docker installed on a host machine if you are distributing on a cloud.

Modifying onProvisioned.sh is the easiest way to configure your own on provision completion detection with this setup.

You can change which version of node to use by editing the .nvmrc file within the projects main folder.

A beta version of pm2 version 2.0 is being used for the command pm2-docker this command is still in beta.

Notice

This setup runs your nodejs script as root. This is not ideal in a production setup.