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

envify-example

v1.1.1

Published

Generate .env.example file from .env

Downloads

496

Readme

envify-example CLI

A command-line interface tool for generating conentional github commit messages using OpenAI and managing environment variables, converting .env files, and interacting with Consul.

generate-commit-message

Installation

npm install -g envify-example

Usage

envify-example [command] [options]

Commands

Generate Pytest

envify-example generate-pytest

Generate a commit message

envify-example generate-commit-message

convert

Convert a .env file to .env.example or .env.json.

envify-example convert [options]

Options:

  • -p, --path <path>: Path to the .env file (default: current directory's .env)
  • -t, --type <type>: Output type: "example" or "json" (default: "example")

Examples:

envify-example convert
envify-example convert -p /path/to/.env -t json

configure-consul

Configure Consul settings.

envify-example configure-consul [options]

Options:

  • -c, --configure: Configure Consul settings
  • -s, --save-config: Save Consul configuration for future use

Example:

envify-example configure-consul -c -s

download

Download .env file from Consul.

envify-example download [options]

Options:

  • -p, --path <path>: Path to save the downloaded .env file (default: current directory's .env)

Example:

envify-example download
envify-example download -p /path/to/save/.env

upload

Upload .env file to Consul.

envify-example upload [options]

Options:

  • -p, --path <path>: Path to the .env file to upload (default: current directory's .env)

Example:

envify-example upload
envify-example upload -p /path/to/.env

Global Options

  • -V, --version: Output the version number
  • -h, --help: Display help for command

Examples

  1. Convert a .env file to .env.example:

    envify-example convert
  2. Convert a .env file to .env.json:

    envify-example convert -t json
  3. Configure Consul settings and save for future use:

    envify-example configure-consul -c -s
  4. Upload a .env file to Consul:

    envify-example upload
  5. Download a .env.json file from Consul:

    envify-example download

Notes

  • Make sure to configure Consul settings using the configure-consul command before attempting to upload or download files.
  • The tool assumes that your .env file is in the current working directory unless specified otherwise using the -p or --path option.

Troubleshooting

If you encounter any issues, please check the following:

  1. Ensure that you have the necessary permissions to read/write files in the specified directories.
  2. Verify that your Consul configuration is correct and that you have network access to the Consul server.
  3. Make sure that the .env file exists in the specified location when using the upload command.

For any further assistance, please open an issue on the project's GitHub repository.