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

@torus-tools/config

v0.0.123

Published

Automatic project configuration module for torus tools

Downloads

4

Readme

Torus Config

In order to provide a seamless experience and eliminate any barriers to entry, the torus CLI was designed to be self-configurating. To maintain and reuse a similar configuration in our other projects we made this configuration SDK.

Features

  • Helps automate global as well as project configuration for all of the torus tools.
  • Lets you control your configuration settings, as well as your API keys, at a global and also a per-project basis.
  • Guides you through the necessary steps to generate the API keys for all of the different supported providers.

How it works

The global configuration file sotred in ~/.aws/config holds the standard environment variables that the user intends to use on most of their projects. the global config file uses a simple toml format and it includes both the API keys/env variables for each cloud/domain provider as well as the providers configuration that sets which provider should be used for which resource. The codeblock bellow shows a sample gloabl config file for a user that usually deploys sites with a Godaddy domain, AWS Bucket, AWS route53 DNS, AWS Cloudfront CDN, and AWS ACM Certificate. Notice that for the aws provider we dont have to provide API keys as we can reference the AWS config in ~/.aws/credentials. If you dont have a global AWS config you can also provide the API keys directly as access_key_id and secret_access_key.

[aws]
region=us-east-1
profile=default

[godaddy]
api_key=fe98wkf287e927198dnj87589hjspi
secret_key=iufyewuiyf8746r98370

[providers]
domain=godaddy
bucket=aws
cdn=aws
dns=aws
https=aws

The diagram bellow represents the flow of configuration variables.

Flow of configuration variables in torus

Torus_config JSON file

every project will have a torus config file that will contain the default providers for that project. You may modify this config file manually at any time or on a per-instance basis by providing CLI flags

const config = {
  index:"index.html",
  error:"error.html",
  last_deployment:"",
  providers: {
    domain: 'godaddy',
    bucket: 'aws',
    cdn: 'aws',
    dns: 'aws',
    https: 'aws'
  }
}