Skip to content

Latest commit

 

History

History
96 lines (66 loc) · 2.3 KB

CONTRIBUTING.md

File metadata and controls

96 lines (66 loc) · 2.3 KB
Raw

How To Contribute

Setup

  • git clone [email protected]:cybertooth-io/ember-simple-auth-aws-amplify.git
  • cd ember-simple-auth-aws-amplify
  • yarn

Building The Add-on

  • ember b
  • ember build

Linting

  • npm run lint:hbs
  • npm run lint:js
  • npm run lint:js -- --fix

Running tests

  • ember test – Runs the test suite on the current Ember version
  • ember test --server – Runs the test suite in "watch mode"
  • ember try:each – Runs the test suite against multiple Ember versions

Running The Dummy Application

For more information on using ember-cli, visit http://ember-cli.com/.

Upgrading The Add-On

When upgrading this add-on, after successfully performing ember init use the following commands to install the following dependencies required by this add-on.

ember install ember-auto-import
ember install ember-concurrency
yarn add @aws-amplify/auth @aws-amplify/core ember-simple-auth

Linking This Add-on For Local Testing

Linking

Use yarn.

# from this add-on project
$ yarn link
# from the other project that depends on this add-on
$ yarn link ember-simple-auth-aws-amplify

Note: I've actually had to go into my other project and put this into its package.json: "ember-simple-auth-aws-amplify": "link:../ember-simple-auth-aws-amplify",

Unlinking

Again, use yarn.

# from this add-on project
$ yarn unlink
# from the other project that linked to this add-on
$ yarn unlink ember-simple-auth-aws-amplify

Deploying The Dummy Application

Make sure your ~/.aws/credentials file has a profile named cybertooth with a valid key and secret,

[cybertooth]
aws_access_key_id = <KEY>
aws_secret_access_key = <SECRET>

Deploy by invoking the following command: ember deploy production

Confirm your changes are showing up in our S3 container: http://ember-simple-auth-aws-amplify.cybertooth.io/

You may need to go into AWS CloudFront to expire the index.html file before the site changes are picked up (see issue).

Releasing & Publishing To NPM

# `yarn publish` will prompt you for the next/new version name
$ yarn publish
$ git push
$ git push --tags