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

@nsfilho/redis-connection

v0.1.14

Published

A very simple and small services to simplify process to connect a redis host or cluster and provide some sugars and environments flavors.

Downloads

101

Readme

Redis Connection Library

A very simple and small services to simplify process to connect a redis host or cluster and provide some sugars and environments flavors.

  • Project licensed under: GPLv3
  • Site Documentation: Homepage
  • Repository: GitHub

Environment Variables

This services use some environment variables to pre-adjust some things, like:

Environment Variables

This services use some environment variables to pre-adjust some things, like:

  • REDIS_${INSTANCENAME}_CLUSTER: a redis cluster or host, example and default: [{ port: 6379, host: '127.0.0.1' }];
  • REDIS_${INSTANCENAME}_PASSWORD: a password for access redis, example and default: password;
  • REDIS_CONNECTION_POOLING: timing between multiples connections to check for instance;
  1. If you do not specify instance name in getConnection or disconnect it will use as default main.
  2. The environment variables replaces the hard-coded values for nodes and password.

For debug purposes, we are using debug library. You can use:

  • DEBUG: with a value like redis-connection:* to see all logs.

Running

For use this library you will need to run a RabbitMQ. A sample docker-compose:

version: '2.0'

services:
    redis:
        image: redis:6
        environment:
            ALLOW_EMPTY_PASSWORD: 'no'
            REDIS_EXTRA_FLAGS: '--maxmemory 250mb'
        command: >
            --requirepass password
        ports:
            - 6379:6379

If you would like to use a docker swarm (stack) version, you can see in your sample folder.

Example

You will found other samples in: Samples Folder.

/* eslint-disable no-console */
import { getConnection, disconnect } from '@nsfilho/redis-connection';

const createSampleKey = async () => {
    const redis = await getConnection();
    redis.set(
        'mysample',
        JSON.stringify({
            when: new Date().toISOString(),
            status: true,
        }),
    );
};

const readSampleKey = async () => {
    const redis = await getConnection();
    const valueStr = await redis.get('mysample');
    if (valueStr) {
        const valueObj = JSON.parse(valueStr);
        console.log('Recovered values:', valueObj);
    }
};

const execute = async () => {
    await createSampleKey();
    await readSampleKey();
    await disconnect();
};

execute();