Skip to content

Commit

Permalink
Merge pull request #321 from engineyard/DOC-380-unix
Browse files Browse the repository at this point in the history
Doc 380 unix
  • Loading branch information
janeday committed Mar 10, 2012
2 parents b79418a + 84ef551 commit 83ff6ba
Show file tree
Hide file tree
Showing 5 changed files with 40 additions and 36 deletions.
1 change: 1 addition & 0 deletions pages/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@
* [[Maintenance pages|deployment-maintenance-pages]]
* [[Change your Git repository location|change-your-repo-location]]
* [[Convert Capistrano symlinks|convert-capistrano-symlinks-to-cloud-symlinks]]
* [[Add unix packages|deploy-unix-package]]
* [[Troubleshooting|deployment-troubleshooting]]
* [[FAQs|deployment-faqs]]
* [[Manage your Application|manage-app-intro]]
Expand Down
18 changes: 9 additions & 9 deletions pages/account-collaboration.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The collaboration feature introduces three new concepts to Engine Yard Cloud. Th

* Accounts
* Users
* Creator Users
* Owners

### Accounts

Expand All @@ -22,9 +22,9 @@ A user is a person with login credentials into Engine Yard Cloud and is currentl

Each user can be a part of multiple accounts and can invite other users to an account. Similarly, each account contains multiple users, and each user has access to all the environments in that account.

### Creator user
### Owners

The creator is the user who created the account by signing up with Engine Yard. This special user is responsible for billing for the account, has access to payment information. Also, this is the only user who can cancel the account.
The owner is the user who created the account by signing up with Engine Yard. This special user is responsible for billing for the account, has access to payment information. Also, this is the only user who can cancel the account.

## Use cases

Expand All @@ -39,7 +39,7 @@ Click on the account settings link on the top bar to see the list of accounts th

<img src="/images/collaboration/collab-nav-link.jpg" alt="Account Settings Link" width="700" />

The accounts page lists each account, the creator for that account and some other summary information. You can manage each account by clicking on the account name to get to the account management screen.
The accounts page lists each account, the owner for that account and some other summary information. You can manage each account by clicking on the account name to get to the account management screen.

<img src="/images/collaboration/collab-account-list.jpg" alt="Engine Yard Cloud List of Accounts" width="700" />

Expand Down Expand Up @@ -71,9 +71,9 @@ If a user is a part of multiple accounts, each environment from each account wil

Many Engine Yard customers develop applications for multiple consumers simultaneously. These consumers might be external customers or separate internal applications. In such situations, having common credentials that can be used across each account is useful for customers. The following is a recommended workflow for these use cases:

- Create a new account for each customer. You can do so by [[signing up|http://cloud.engineyard.com]]. This creates a new creator user, which is the administrator user for this account. **Note:** If you already have existing accounts that you would like to collaborate with, skip this step.
- Create a new account for each customer. You can do so by [[signing up|http://cloud.engineyard.com]]. This creates a new owner, which is the administrator user for this account. **Note:** If you already have existing accounts that you would like to collaborate with, skip this step.
- In the new account, go to the accounts section and add developers to the account. If the developers already have Engine Yard credentials, they can accept the invitation under whatever account they are signed in as. You can also add new users to each account. Add their email information and they receive an invitation to open a new account.
- If you want to hand off the project to your customer, give them credentials for the creator account and remove any members who no longer need access from the Accounts page.
- If you want to hand off the project to your customer, give them credentials for the owner account and remove any members who no longer need access from the Accounts page.

The email invitation sent to a user can be accepted only once. However, we do not bind the invitation link to the email address it was originally sent to. This enables users who already have accounts to accept invitations sent to other email addresses that they own. Any member of an account can also rescind an invitation by removing it on the Account Management page.

Expand All @@ -87,8 +87,8 @@ Learn more about [[managing your ssh keys|env_ssh_keys]] on our docs site.

### Can we assign specific permissions to individual users in each account?

Currently there are no per-user permissions in Engine Yard Cloud. Each user for an account has access to all environments on that account. The only special permissions are the ability to change payment information and cancel the account, which is granted to the creator user.
Currently there are no per-user permissions in Engine Yard Cloud. Each user for an account has access to all environments on that account. The only special permissions are the ability to change payment information and cancel the account, which is granted to the owner.

### Can we change the creator user for an account?
### Can we change the owner for an account?

At this point, we do not support reassigning the creator user for an account.
To change the owner of the account, submit a ticket with [[Engine Yard Support|http://support.cloud.engineyard.com]].
27 changes: 0 additions & 27 deletions pages/application_home.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,33 +101,6 @@ The gem appears on the "Selected Gems" list below. Boot your instance and the ge
Click the x Remove link and the gem is removed. This will remove the gem from the UI but will not remove the gem from any currently running instances.


## Add Unix packages to your application

You can add additional software packages to your application within Engine Yard Cloud. Packages are added at the account-level. After a package is applied to specific environment, it cannot be removed from that environment. (Although, after a package is dissociated from an application, new environments for that application do not have the package.)

###To configure additional software packages for your application within Engine Yard Cloud.

1. In the Dashboard, click the name of the application you want to modify.
2. Click the Unix Packages icon.
3. Search for your package.
For example `rabbitmq` for RabbitMQ.
Results are returned under the heading "Available Unix Packages".
4. Click Add ->.
The package is added to the Selected list.
5. To install the package on an existing environment:
a. Click Go to dashboard.
b. Click the environment name.
c. Click Apply.
6. To install the package on new environment:
a. Click Go to dashboard.
b. Create and boot a new environment for the application.

### To remove a software package

1. In the Dashboard, click the name of the application to remove the software package from.
2. Click the Unix Packages icon.
3. Click x Remove for the package.
This removes the package from the UI but does not remove the package from any currently running environments.


<h2 id="topic5"> More information</h2>
Expand Down
27 changes: 27 additions & 0 deletions pages/deploy-unix-package.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Add unix packages to your application

You can add additional software packages to your application within Engine Yard Cloud. Packages are added at the account-level. After a package is applied to specific environment, it cannot be removed from that environment. (Although, after a package is dissociated from an application, new environments for that application do not have the package.)

##To configure additional software packages for your application within Engine Yard Cloud.

1. In the Dashboard, click the name of the application you want to modify.
2. Click the Unix Packages icon.
3. Search for your package.
For example `rabbitmq` for RabbitMQ.
Results are returned under the heading "Available Unix Packages".
4. Click Add ->.
The package is added to the Selected list.
5. To install the package on an existing environment:
a. Click Go to dashboard.
b. Click the environment name.
c. Click Apply.
6. To install the package on new environment:
a. Click Go to dashboard.
b. Create and boot a new environment for the application.

## To remove a software package

1. In the Dashboard, click the name of the application to remove the software package from.
2. Click the Unix Packages icon.
3. Click x Remove for the package.
This removes the package from the UI but does not remove the package from any currently running environments.
3 changes: 3 additions & 0 deletions pages/deployment-intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,9 @@ deploying your applications to the cloud with our platform.

11. ### [[Convert Capistrano symlinks to Engine Yard Cloud symlinks|convert-capistrano-symlinks-to-cloud-symlinks]]
Learn how to convert Capistrano symlinks to Engine Yard Cloud symlinks for deployment.

12. ### [[Add unix packages to your application|deploy-unix-package]]
Learn how to add a unix package to an environment.

12. ### [[Troubleshooting|deployment-troubleshooting]]
Check here for tips and ideas to help troubleshoot your deployment.
Expand Down

0 comments on commit 83ff6ba

Please sign in to comment.