JSPM

gd-backup

1.1.3
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 4
  • Score
    100M100P100Q22965F
  • License MIT

Automated Google Drive Backup

Package Exports

  • gd-backup

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (gd-backup) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

gdn23

Automated Google Drive Backup 1.1.3

GD backs up your google drive account into a zip file

How to setup the project

Tested for node 6.3.1 and npm 3.10.5

From git:

# clone project
git@github.com:mousemke/gd.git

# go into folder
cd gd

# install the npm modules
npm i

# edit config.js and add your account info.  In whatever editor you like

# run tests
npm test

# start server
npm run serve

From npm:

# clone project
npm i -D gd-backup

# go into folder
cd node_modules/gd

# install the npm modules
npm i

# edit config.js and add your account info.  In whatever editor you like

# run tests
npm test

# start server
npm run serve

Scripts

npm scripts description
npm run serve starts the dev server at http://localhost:16666
npm run lint runs eslint for code and code style issues
npm run lintFix runs eslint for code and code style issues, fixes minor issues
npm test runs only linters (for now)

Issues

Please report issues here.

(1.) add any specific information that can help to reproduce and resolve the bug.
  • What did you do, when the bug appeared.
  • Node, NPM, + version number
  • OS
(2.) Add a label to the issue, if possible.
  • critical -> needs fix right away (like broken build, blocks development)
  • bug -> needs fix
  • issue -> small bug, does not affect anything (small bug in UI, design issue)
  • feature -> feature request
  • question -> needs discussion
  • docs -> needs documentation
  • help wanted -> need help with implementation or fixing bug

Contributing

Branch structure:

master - latest stable git repo. Auto deploys to live (when applicable)

stage - stable git repo release candidate. no dist files commited. auto deploys to stage (when applicable)

dev - current development branch. This is where feature branches should branch from

feature branches - these branches come from dev, are branched for a specific geature or bug, then get merged back into dev

Check here for more detailed instructions

Thank you <3

This project adheres to the Contributor Covenant. By participating, you are expected to honor this code.

GD - Code of Conduct

Change log:

1.1.3

  • readme changes
  • dependencies cleaned

1.1.2

  • documentation and publishing info changes

1.1.0

  • initial commit