Create deployment of the content repository
Closed, ResolvedPublic5 Story Points

Description

The deployment of the new content should be atomic, as it is done in the deployment playbook for the fundraising frontend.

Deploy the branches to the respective system (test to test, master to production).

Possible steps in a playbook:

  • Check out newest version in a local release subdirectory.
  • Create an archive, copy it to the server and extract it in a timestamped subdirectory in content
  • Change the content symlink in the app subdirectory to the new release subdirectory.
  • Clear Twig cache
  • Remove old releases, leaving the last 2 releases.

Create the playbook steps and an include file that can be run as part of the deployment playbook for the fundraising frontend and as a standalone playbook.

gabriel-wmde moved this task from Backlog to Sprint ready on the WMDE-Fundraising-Tech board.EditedApr 7 2017, 11:30 AM
gabriel-wmde closed this task as Declined.
Pablo-WMDE renamed this task from Create an Ansible playbook for the deployment of the content repository to Create deployment of the content repository.Apr 12 2017, 1:09 PM
Pablo-WMDE reopened this task as Open.
Pablo-WMDE updated the task description. (Show Details)
Pablo-WMDE claimed this task.
This comment was removed by Pablo-WMDE.
Pablo-WMDE added a comment.EditedTue, May 9, 3:17 PM

WIP here https://github.com/wmde/fundraising-infrastructure/pull/129

Opted against the discussed ansistrano after realizing that

  • it will check out on the remote host
  • does not upload via tar ball even if checked out locally by hand

Create a (WIP) PR to illustrate interaction of a more sophisticated project w/ all hooks of wmde.atomic-deploy https://github.com/wmde/FundraisingFrontend/pull/880

Pablo-WMDE added a comment.EditedTue, May 16, 8:21 AM

I think https://github.com/wmde/fundraising-infrastructure/pull/129 is now good to go for content. Review please.
Todos in https://github.com/wmde/FundraisingFrontend/pull/880 indicate there are some changes required to get FundraisingFrontend on board later, but that should be a dedicated story (T165458).

Waiting for feedback from the mailing list https://groups.google.com/forum/#!topic/ansible-project/GBK_uPjhvHw after review issues could not be resolved satisfyingly.

Pablo-WMDE changed the task status from Open to Stalled.Wed, May 17, 7:29 AM

Configured FundraisingFrontend so that content using atomic deploy lives in current
https://github.com/wmde/FundraisingFrontend/pull/882

Pablo-WMDE closed this task as Resolved.