-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathrackspace.yaml
72 lines (58 loc) · 2.97 KB
/
rackspace.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
schema-version: 1.0.0
application-family: Application Frameworks
application-name: Rails
flavor: Single Linux server - RCv3
flavor-weight: 2
rackconnect: true
reach-info:
icon-20x20: https://0b5294b243620310a700-e388a7f3aba385a925111b1fc6f680d4.ssl.cf2.rackcdn.com/rails-icon-20x20.png
tattoo: https://0b5294b243620310a700-e388a7f3aba385a925111b1fc6f680d4.ssl.cf2.rackcdn.com/rails-tattoo.png
hidden_outputs:
- private_key
abstract: |
Rails is a popular open-source web development framework for Ruby developers.
instructions: |
#### Getting started
Your application should be available on port 80 of the deployed server.
#### Where the application is deployed
Your application is deployed [Capistrano](http://capistranorb.com/)-style
into the home directory of the rails user in a directory based on the name
of the git repo. As an example, when deploying from the repo
`http://github.com/MyUser/myrepo.git` the deployment for the user id
`rails` is placed in the following directory path:
`/home/rails/myrepo/`
Within this directory are two other directories, `shared` and `releases`,
along with a symbolic link, `current`, to the deployed revision--
`current` is the directory from which the application runs. The deployed
revision will be cloned into `releases` in a directory named for
the commit hash of the reference supplied. The `shared` directory contains
files which may be common across releases, such as Gems and static assets
produced by `rake assets:precompile`.
#### Gems
Gem dependencies are installed by running `bundle install --deployment`
in the `current` directory. This requires a `Gemfile.lock` file in the root
of the application repo.
#### `rake` tasks
Two rake tasks are run at deployment time: `rake db:migrate` followed by
`rake assets:precompile`. Additional rake tasks will be run if provided in
the `rails_rake_tasks` parameter.
#### Unicorn
If you are using unicorn it must be declared in the application's Gemfile.
A unicorn.rb file is generated and placed in the application's
config directory (which is linked into the current release deployment
directory) along with a `database.yml` file configured to reference
the deployment's database server.
#### Logging in via SSH
The private key provided in the passwords section can be used to login as
root via SSH. We have an article on how to use these keys with [Mac OS X and
Linux](http://www.rackspace.com/knowledge_center/article/logging-in-with-a-ssh-private-key-on-linuxmac)
as well as [Windows using
PuTTY](http://www.rackspace.com/knowledge_center/article/logging-in-with-a-ssh-private-key-on-windows).
user-input-required: true
description: |
#### Single Linux server - RCv3
Single Linux server running [Rails](http://rubyonrails.org/) and
[MySQL 5.5](http://www.mysql.com/) or
[Postgres 9.1](http://www.postgresql.org/).
This deployment is intended for development and testing scenarios.
This template will only function with RackConnect v3.