Integration | Staging | Production | |
---|---|---|---|
website | https://exhibits-int.library.cornell.edu | https://exhibits- |
stg.library.cornell.edu/ | https://exhibits.library.cornell.edu |
server | AWS Elastic Beanstalk elasticbeanstalk-environment-name: exhibits-int- |
---|
ruby3 | AWS Elastic Beanstalk elasticbeanstalk-environment-name: exhibits- |
stg-ruby3 | AWS Elastic Beanstalk elasticbeanstalk-environment-name: exhibits-prod- |
ruby3 | |||
solr | http://aws-108-172.internal.library.cornell.edu:8983/solr/#/ Core: exhibits-int | http://aws-108-172.internal.library.cornell.edu:8983/solr/#/ Core: exhibits-staging | http://aws-108-078.internal.library.cornell.edu:8983/solr/#/ Core: exhibits |
---|---|---|---|
mysql | Hostname and credentials in LastPass ("Exhibits int RDS admin") | Hostname and credentials in LastPass ("Exhibits int RDS admin") | Hostname and credentials in LastPass ("Exhibits prod RDS admin") |
Server
CUL-IT Library Systems docs about AWS Elastic Beanstalk: Elastic Beanstalk (USDA-ESMIS, exhibits, studentworkers, ld4l-qa)
...
- Log in to AWS
- Go to Elastic Beanstalk console > Application name = exhibits
- Choose relevant "Environment name", e.g. exhibits-integrationint-ruby3, exhibits-stg-stagingruby3, exhibits-prod-1ruby3
- Select "Logs" in menu on left
...
- Get the private IP address of the relevant elastic beanstalk instance. EB instances can be replaced, so the IP address needed for ssh access is not constant.
- Option 1: Grab from EC2 console
- Log in to AWS
- Go to the EC2 console > Instances
- Choose or search for relevant "Name", e.g. exhibits-integrationint-ruby3, exhibits-stg-stagingruby3, exhibits-prod-1ruby3
- Copy private IP address, e.g. "10.92.111.183"
- Option 2: Query the AWS CLI:
aws ec2 describe-instances --filters "Name=tag:elasticbeanstalk:environment-name,Values=exhibits-integrationint-ruby3" --query 'Reservations[*].Instances[].PrivateIpAddress'
- Option 1: Grab from EC2 console
- Connect via ssh:
ssh -i cul-admin.pem ec2-user@10.92.111.183
- Replace IP with address from step 1
...
You can review the managed-schema and solrconfig in the Solr Admin UI and use these to set up your own local Solr instance. solrconfig.xml, managed-schema
...