Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant EC2 provider #39

Open
6 tasks
sanguis opened this issue Mar 30, 2016 · 1 comment
Open
6 tasks

Vagrant EC2 provider #39

sanguis opened this issue Mar 30, 2016 · 1 comment
Assignees

Comments

@sanguis
Copy link

sanguis commented Mar 30, 2016

Replacing the vagrant provider with an ec2 provider:

Feature: Vagrantfile provider with an ec2 provider
Lower system resources on locals by allowing devs to use EC2 for hosted development environments on the free tier.
Will be used by application developers

  • Scenario: Provision the environment.
    Given I am in the directory for this repo
    When I run run "vagrant up"
    Then I should get
Vagrant box creation dialog including urls and IP's to connect to
  • Scenario: Connect to the Box
    Given Vagrant up was successful
    When I run Vagrant ssh
    Then I should connect to the box
  • Scenario: folders are shared.
    Given I Vagrant Up is sucessful
    When I append "$Date" to FILE
    And I go to "SERVER IP"
    Then I should be able to see "$Date"

Other requirements that I don't know how to gherkinize.

  • the AWS security role to only allow traffic from Harvard.
  • basic auth over the web.
  • Bonus item, have machine auto tear it self down if after N time.
@sanguis sanguis self-assigned this Mar 30, 2016
@sanguis sanguis added this to the Sp2016 Sprint 7 milestone Mar 30, 2016
@sanguis
Copy link
Author

sanguis commented Mar 30, 2016

@arthurian please make sure the above is good

@arthurian arthurian changed the title 3 - Vagrant EC2 provider Vagrant EC2 provider Mar 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants