PRODUCTION SERVER

Source Code

• Git Repo: IDoneThis repository, and the repo name is idt-two which is currently working from the main branch.

• EC2 Application: Host name can be found from the EC2 console and the Key file to access these servers is attached along with this email. The developers can use the user name ubuntu and with this Key file, they can access the server.

  idt-2018-05-12 (6).pem

• Application hosted: /home/ubuntu/idt-two/

• 2 Servers: There are two servers, one for Web application (01-IDT-ProdNew-Ubuntu18 i-044433c13fa9a818d) and other is primarily to run Sidekiq and rake tasks (02-IDT-RakeNew-Ubuntu18 i-0f6e21720d9a291e1). Both servers can be accessed using the same key file and user name.

• Application's Production environment file: /home/idt-two/.env and it also has production database access credentials which are defined in the DATABASE_URL environment variable.

• Applications are setup to run with Puma server through Proxy with Nginx and the configuration of Nginx is in /etc/nginx/sites-enabled/ folder.

EC2

• 02-IDT-RakeNew-Ubuntu18 i-0f6e21720d9a291e1
• 01-IDT-ProdNew-Ubuntu18 i-044433c13fa9a818d

RDS

• idt-prod-new - https://us-east-1.console.aws.amazon.com/rds/home?region=us-east-1#database:id=idt-prod-new;is-cluster=false
  • endpoint: idt-new-resto.cqnigslwject.us-east-1.rds.amazonaws.com
  • port: 5432
  • username: 4395ec9942ac509
  • password: peGO7GJpskFpzoMPeuymT52Y0OMTR1a9
• idt-new-resto (I dont think we use this one) - https://us-east-1.console.aws.amazon.com/rds/home?region=us-east-1#database:id=idt-new-resto;is-cluster=false
  • endpoint: idt-new-resto.cqnigslwject.us-east-1.rds.amazonaws.com
  • port: 5432
  • username:
  • password:

Elasticache

• idt-staging-redis - (I’m not sure if we are using it because it’s staging) - https://us-east-1.console.aws.amazon.com/elasticache/home?region=us-east-1#/redis/idt-staging-redis
  • Cluster name: idt-staging-redis
  • Endpoint: idt-staging-redis.cqogab.ng.0001.use1.cache.amazonaws.com:6379