Use ey_cli to create the new EY environment

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
mysql, postgresql, ruby
Domain
backend, cli, cloud

Research direction

Start with the ey_cli entry point and review the AppScrolls transformations referenced in the issue. The work is done when it detects the database, app stack, job system, and Ruby runtime, then creates the appropriate eycloud environment.

Written by the indexing model from the issue text.

Description

Detect

  • mysql vs postgresql
  • which app stack
  • delayed_job or resque
  • ruby 1.9 or 1.8 or jruby

and create the appropriate eycloud environment

This is the basics of AppScrolls transformations.

Dominant language
Ruby
Stars
26
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from engineyard/engineyard-migrate

All issues in engineyard/engineyard-migrate

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.