# meteor-deploy-config

> Trix for managing Meteor deployment configurations

Latest version **0.0.4** (published 2012-08-08) · 0 weekly downloads

## Install

```sh
npm install meteor-deploy-config
pnpm add meteor-deploy-config
yarn add meteor-deploy-config
bun add meteor-deploy-config
```

Provides the command `mcfg`.

## Health

**Score 0/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; low quality score; pre 1.0.

Negative: insecure dependencies; abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.4 |
| Published | 2012-08-08 |
| First published | 2012-07-23 |
| Weekly downloads | 0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 3 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 6 |
| Author | Mike Bannister |
| Maintainers | possibilities |

## Links

- npm: https://www.npmjs.com/package/meteor-deploy-config
- Repository: https://github.com/possibilities/meteor-deploy-config
- Homepage: http://possibilities.github.com/meteor-deploy-config
- npm.io page: https://npm.io/package/meteor-deploy-config

## Dependencies (3)

- [commander](https://npm.io/package/commander.md) >=1.0.0
- [ddpclient](https://npm.io/package/ddpclient.md) git://github.com/possibilities/node-js_ddp-client.git#handle-connection-errors
- [underscore](https://npm.io/package/underscore.md) >=1.3.3

## Recent versions

- 0.0.4 (latest) — 2012-08-08
- 0.0.3 — 2012-07-27
- 0.0.2 — 2012-07-25
- 0.0.1 — 2012-07-23

## README

# Deploy Config

*Trix for managing Meteor deployment configurations*

## What's it for?

Sometimes a new instance of an app needs to be configured before it's useful. This library takes a simple approach to solving that problem. There are two components:

  1) A smart package that provides a `DeployConfig` key/value store that's backed by Mongo.
  
  2) A command line app that prompts for each unsatisfied value and communicates them back to the deployed app (yes, over DDP!).

## Installation

  1) Until there's a better way to install smart packages use [meteorite](http://possibilities.github.com/meteorite/)

  2) Install `mcfg` using npm

      npm install -g meteor-deploy-config

## How do I use it?

Start by fetching values from the `DeployConfig` key/value store. If the value is already in `DeployConfig` the callback gets called right away:

    DeployConfig.get('googleSecret', function(secret) {
      Meteor.accounts.google.setSecret(secret);
    });

After you deploy your app run the command line utility and you'll be prompted for any values that your app needs to get from `DeployConfig`. These values will be sent to the server, saved in `DeployConfig` and their callbacks will be invoked:

    mcfg --hostname cool-domain.com --port 3333

## Security recommendations

This package has no *real* security features of it's own. When you deploy an app that contains calls to `DeployConfig.get()` any `ddp` client can connect to it and set any unsatisfied values but after they are set they cannot be set again. Potentially I'll add authentication but I think for now this security-by-first-come-first-served is good enough for most environments. I recommend:

  * Do everything over SSL! When you specify port 443 `mcfg` will use the wss:// protocol.

  * If you need better security than this please help me add it!

  * For most environments running `mcfg` immediately after you deploy will be Secure Enough™

        meteor deploy cool-app && mcfg -h cool-app.meteor.com -p 443

---
_Source: https://npm.io/package/meteor-deploy-config · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._