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

ansible-lint-rules

v1.0.1

Published

This is the rule-set I use for my ansible roles. By linting the roles and playbooks you get an standarized setup and use best practices.

Downloads

5

Readme

ansible-lint

This is the rule-set I use for my ansible roles. By linting the roles and playbooks you get an standarized setup and use best practices.

Setup

You need to have ansible-lint installed:

$ pip install ansible-lint

Check the rules out to a directory of your choice:

$ hub clone lxhunter/ansible-lint /usr/local/src/ansible-lint
# or
$ git clone https://github.com/lxhunter/ansible-lint.git /usr/local/src/ansible-lint

Pro-Tip: I use fresh for this:

$ fresh lxhunter/ansible-lint . --file=/usr/local/src/ansible-lint

Usage

Now you can lint your playbooks by doing:

# just my rules
$ ansible-lint -r /usr/local/src/ansible-lint/rules playbook.yml
# or for the standard rule and mine
$ ansible-lint -R -r /usr/local/src/ansible-lint/rules playbook.yml

Rules

| Code | Message | | --- |:---| | LX1 | Playbook | | --- | | | LX2 | Role | | --- | | | LX3 | Task | | --- | | | LX4 | General Module | | LX401 | Specific Modules should have owner, group and mode | | --- | | | LX5 | Specific Module | | LX501| Template Module - Template files should have the extension '.j2' |

Testing

Setup:

You need to have nodemon installed:

$ npm install

Usage:

I used node for testing:

nodemon LX401

Credits

Contribute

Tutorial

Author

Author:: Alexander Jäger

Copyright 2018