-
Type: Story
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.2 Larks
-
Fix Version/s: 1.2 Larks
-
Labels:None
-
Sprint:Larks 1.2, 1.3 Larks
As a QA I'd like to have a PRE-PROD environment with the same database as production so that I can test features on data loads close to real
As a Developer I'd like to have a PRE-PROD environment with the same database as production so that I can be sure my database migrations will pass on PROD
Acceptance Criteria:
- Our database backup happens once a day, every time this backup is created, it automatically renews the PREPROD database. Contact Maksim Reshetov or Stanislav Bashkyrtsev for details on where to get db dump.
- The password of the user 'admin' has to be changed in PREPROD database because it's used to communicate between Poulpe and JCommune in production. This might not be necessary if HTTPS communication will be implemented by the start of this task. Communicate Evgeny Surovtsev or Evgeny Kapinos for details.
- Forum URL hast to be changed in COMPONENTS table to http://preprod.jtalks.org so that PREPROD Poulpe will communicate with PREPROD JCommune instead of PROD one.
- Forum should be deployed onto: http://preprod.jtalks.org/jcommune and Poulpe should be deployed onto http://preprod.jtalks.org/poulpe. Contact Guram Savinov to get details on how and where to deploy a new instance.
- A new CI build should be created to deploy JCommune and Poulpe to PREPROD. This build should be a part of Deployment Pipeline. Contact Stanislav Bashkyrtsev when you need permissions and/or details.
- Java Mail Server has to be started and used to send mails. It should intercept all the mails and not let them out to real users. Contact Guram Savinov or Vitaliy Kravchenko for details.
When someone starts to work on this story, he/she should create a subtask for a particular item from acceptance criteria in order to track the progress.
There are no Sub-Tasks for this issue.