Installation issues #146

Closed
mfenner opened this Issue Oct 19, 2014 · 1 comment

Projects

None yet

1 participant

@mfenner
Member
mfenner commented Oct 19, 2014
  • database.yml: database: alm_<%= Rails.env %> should be database: lagotto_<%= Rails.env %>
  • node.json: "recipe[apt]"needed before "recipe[lagotto]" or the use of "apt-get install" is likely to fail because apt-get update hasn't happened recently enough.
  • node.json: new VM hostname is not actually set on the host. Possibly fixed by: "recipe[hostname]" again, before "recipe[lagotto]" and with appropriate changes to the Cheffile, though I'm not sure yet.
  • Instructions (git clone... vagrant up...) need to say that the Vagrantfile needs to be modified for use with AWS (and probably other providers). For AWS the following is what I changed to:
aws.access_key_id = ENV['AWS_KEY_ID']
aws.secret_access_key = ENV['AWS_SECRET_KEY']
aws.keypair_name = ENV['AWS_KEYPAIR_NAME']
override.ssh.private_key_path = ENV['AWS_KEY_PATH']
  • Instructions also need to indicate the need to change settings.yml, config.json, development.rb, production.rb et al to suit the need.
@mfenner mfenner added the enhancement label Oct 24, 2014
@mfenner mfenner pushed a commit that referenced this issue Oct 27, 2014
Martin Fenner use test database #146 735c0df
@mfenner mfenner pushed a commit that referenced this issue Oct 27, 2014
Martin Fenner Removed obsolete cofiguration file #146 4f3bfed
@mfenner
Member
mfenner commented Oct 27, 2014

Starting with the Lagotto 3.7 release all user-specific configuration options for Rails, as well as for the server configuration and deployment tools Vagrant, Chef and Capistrano are environment variables, and can be stored in a single .env file. An example file is provided (.env.example) and can be used without modifications for a development server. More information regarding ENV variables and .env is available here. The following configuration options need to be set:

# Example configuration settings for this application

# database settings
DB_NAME=lagotto
DB_USERNAME=vagrant
DB_PASSWORD=
DB_HOST=localhost

# internal name of server
HOSTNAME=lagotto.local

# public name of server
# can be HOSTNAME, or different if load balancer is used
SERVERNAME=lagotto.local

# all instances of server used behind load balancer
# can be HOSTNAME, or comma-delimited string of HOSTNAME
SERVERS=lagotto.local

# name used on navigation bar and in email subject line
SITENAME=ALM

# couch_db database
COUCHDB_URL=http://localhost:5984/lagotto

# email address for sending emails
ADMIN_EMAIL=admin@example.com

# number of background workers
WORKERS=3

# automatic import via CrossRef API.
# Use 'all', 'member', 'sample', 'member_sample', or leave empty
IMPORT=

# persistent identifier used
UID=doi

# keys
# run `rake secret` to generate these keys
API_KEY=8897f9349100728d66d64d56bc21254bb346a9ed21954933
SECRET_TOKEN=c436de247c988eb5d0908407e700098fc3992040629bb8f98223cd221e94ee4d15626aae5d815f153f3dbbce2724ccb8569c4e26a0f6f663375f6f2697f1f3cf

# mail settings
MAIL_ADDRESS=localhost
MAIL_PORT=25
MAIL_DOMAIN=localhost

# vagrant settings
PRIVATE_IP=10.2.2.4

AWS_KEY=
AWS_SECRET=
AWS_KEYNAME=
AWS_KEYPATH=

DO_PROVIDER_TOKEN=
DO_SIZE=1GB
SSH_PRIVATE_KEY='~/.ssh/id_rsa'

# user and group who own application repository
DEPLOY_USER=vagrant
DEPLOY_GROUP=vagrant

# mysql server root password for chef
DB_SERVER_ROOT_PASSWORD=EZ$zspyxF2
@mfenner mfenner closed this Oct 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment