CloudServices/Loop/Deploy: Difference between revisions

→‎Dev: add setting info
(ADDING OPS, DEV, QA DEPLOYING FLOW.)
(→‎Dev: add setting info)
 
(One intermediate revision by one other user not shown)
Line 35: Line 35:
==Dev==
==Dev==


* <b>Host:</b> https://loop-dev.stage.mozaws.net/
* <b>Host:</b> https://loop-dev.stage.mozaws.net
* <b>Maintainer:</b> DEVs
* <b>Maintainer:</b> DEVs
* <b>Tokbox mocked?</b> NO.
* <b>Tokbox mocked?</b> NO.
Line 43: Line 43:
** loop-server is updated with the master branch by devs on a regular basis - or upon request. you can get the version by displaying the root URL of the server.
** loop-server is updated with the master branch by devs on a regular basis - or upon request. you can get the version by displaying the root URL of the server.
* <b>Access:</b>  ec2-user@loop.dev.mozaws.net
* <b>Access:</b>  ec2-user@loop.dev.mozaws.net
To use this in your browser go to about:config and edit <code>loop.server</code> changing the value to <code>https://loop-dev.stage.mozaws.net</code> and then restart your browser.


'''This environment can be used to test end-to-end scenario until the service hits the Stable channel.'''
'''This environment can be used to test end-to-end scenario until the service hits the Stable channel.'''
Line 205: Line 207:
* Then, sometimes we have a real emergency in Production that requires a change (DEV or OPS). We have not always been good about the process for this case.  
* Then, sometimes we have a real emergency in Production that requires a change (DEV or OPS). We have not always been good about the process for this case.  


Examples:
<b>Examples:</b>
1. The service is broken and needs a code change
 
2. Server issues like stack size, cpu/memory/disk issues, config issues, DB issues
# The service is broken and needs a code change
# Server issues like stack size, cpu/memory/disk issues, config issues, DB issues
Confirmed users
176

edits