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

aws-mongodump

v0.0.3

Published

mongodumps directly to s3, does not pass go, does not create dump locally and then upload. streams and pipes all the way.

Downloads

10

Readme

aws-mongodump

A node.js package to dump mongodb (mongodump) directly into s3 without filling up your local disk in the process.

NOTE: This is still a work in progress. Please don't rely on it as your only backup option, especially without some decent testing.

NOTE 2: You may need to upgrade your version of mongodump (by upgrading mongo) due to this issue: https://jira.mongodb.org/browse/SERVER-5233

Install

npm install aws-mongodump

Use

var dump = require('aws-mongodump').dump;

var now = +new Date(); // gives the current time as a number

dump("MY_MONGO_URI", "mongobackup-" + now, function (err, res) {
  if (err) { throw err; }
  console.log('results: ', res);
});

By default, dumpstr will check for a file in your working directory called "conf.js", which should look something like this.

// This file is called conf.js
module.exports = {
  aws: {
    key: "MY_KEY_IS_HERE"
  , secret: "THIS_IS_SECRET_HERE"
  , bucket: "I_HAS_A_BUCKET"
  }
}

You can also update that path using setConfig.

var md = require('dumpstr')
, dump = md.dump;

md.setConfig("my_config_path/is_better.js");

Or you can supply a json config object directly using setConfigJson.

var md = require('dumpstr')
, dump = md.dump;

md.setConfigJson(json);

If you want to keep your configs in environment variables instead (Who could blame you?), go ahead and set these instead. That way you can leave out the config file entirely.

AWS_KEY
AWS_SECRET
AWS_BUCKET

Thanks

@timisbusy for the providing pretty much all of this code base, added convict (json) config options and updated logger.