Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

hapiest-deploy

Package Overview
Dependencies
Maintainers
2
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

hapiest-deploy

A deployment tool. Initially for AWS ElasticBeanstalk but it may expand in scope over time.

  • 0.1.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
8
decreased by-57.89%
Maintainers
2
Weekly downloads
 
Created
Source

Overview

hapiest-deploy is designed to make it really simple to deploy an application running multiple Docker images/services within the same repository to AWS ElasticBeanstalk. It may or may not expand scope over time.

If that sounds like what you need, go ahead and install the module:

npm install --save-dev hapiest-deploy

Getting starting

Setting up tests

Tests are split up into two types: unit, which run exclusively locally, and integration, which need to connect to AWS services such as S3 and ElasticBeanstalk to succeed. Unit tests should pass out of the box but you'll need to do two things to get integration tests running:

  1. Create three configuration files:

    A. test/helper/integration-config/deployConfig.json

    {
      "region": "us-east-1",
      "s3Bucket":"elasticbeanstalk-us-east-1-076414961204",
      "ebApplications" : [{
          "name": "web",
          "ebApplicationName": "visualai-web",
          "ebEnvironments": [{
              "name": "staging",
              "ebEnvironmentName": "visualai-staging-env",
              "ebEnvironmentId": "e-igxa3sgfmm",
              "gitBranch": "master"
          }]
      }]
    }
    

    Note, you should replace the above config with values that represent an ElasticBeanstalk app/env you have running in an AWS account accessible from credentials provided in (b)

    B. test/helper/integration-config/deployCredentials.json

    {
      "awsCredentials": {
        "accessKeyId": "myAcccessKeyId",
        "secretAccessKey": "mySecretAccessKey"
      }
    }
    

    C. test/helper/integration-apps/web/Dockerrun.aws.json

    {
      "AWSEBDockerrunVersion": "1",
      "Authentication": {
        "Bucket": "vizualai",
        "Key": "config/dockerhub/dockerhub-vizualai-auth.json"
      },
      "Image": {
        "Name": "vizualai/web",
        "Update": "true"
      },
      "Ports": [
        {
          "HostPort": "80",
          "ContainerPort": "3000"
        }
      ]
    }
    

    You will need to adjust the folder underneath integration-apps based on values you provide in (A). The foldername should correspond to one of application names you have in the config file (name not ebApplicationName).

Keywords

FAQs

Package last updated on 04 Apr 2017

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc