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

tarsjs-template

v1.0.11

Published

tarsjs template for new projects

Downloads

19

Readme

TARSjs

TarsJS is a full stack framework to start working with MongoDB, Node.js, Sails and AngularJS easily. It is based on Docker containers and offers a quick way to start a project and organize your application. In TarsJS, each component is stored in a seperate docker container.

Prerequisite Tools

Docker (1.11.1 or higher)

https://docs.docker.com/linux/

Docker-compose version : 1.7.1 (version 2 yml files are used)

https://docs.docker.com/compose/install/

Installation

It's pretty easy : Git clone or fork this repo and open a terminal.

Run : docker-compose up

Go to : http://172.16.0.10/ It works !

How does it work ?

Database

The database is built from the mongodb docker image. It uses a docker volume stored in db/data. This folder is ignored by git so these data aren't messing up the repo.

default ip address : 172.16.0.12

Api

The api is built from the node docker image. It exposes a sails server. This server is not directly accessed by clients. It is only aimed to be requested by the angular application to manipulate database data.

default ip address : 172.16.0.11

Front

The front api is running an Nginx server exposing the AngularJS application and serving static files. It is also the only entry point for the clients. It redirects automaticly all /api/ requests to the Api server. This behavior has been made in order to create a cache strategy over the api nodejs server.

default ip address : 172.16.0.10

How do I get to code in it ?

Basically, there's two folders and seperate applications :

Sails Application

The Sails Application is hosted in /api/src

You can edit everything you need in here.

Angular Application

The Angular Application is hosted in /front/src/app. You can edit everything you need in here as well.

Grunt is configured to publish the application in the /front/src/dist folder. All the grunt tasks are defined in the file /front/src/Grunfile.js.

The application uses Bower to manage dependencies. Bower components are stored in /front/src/bower_components and are automatically copied to /front/src/dist/libs.

The Nginx root folder is configured to be the /front/src/dist folder.

Project Roadmap

What's next ?

  • A better sample application showing the full stack chain with a mongo collection and a sails api consumed by the angular app.
  • Environment parameters to make it easier to go in production and manage environment variables
  • Unit tests integration with Mocha
  • Logging strategy to be defined

Any feedback ?

Please let me know :) Honesty level 90%.