#366 Development environment to carry on redesign tests on websites
Closed: Fixed by arrfab. Opened by areguera.

Hi,

To carry on visual redesign tests related to websites, I would like to request access to dev instances equivalent to the following sites:

  • www.centos.org
  • lists.centos.org
  • blog.centos.org
  • people.centos.org (httpd autoindex tests with user-specific/customized page header)
  • mirror.centos.org (httpd autoindex tests with default page header)

The redesign tests consist on the following:

  • A single place for CSS customization taking advantage of jekyll SASS feature. This would enable files (e.g., centos-blog.bootstrap.min.css, centos-lists.bootstrap.min.css) used by other sites (e.g., blog.dev.centos.org, lists.dev.centos.org) at www.dev.centos.org/assets/css/ location. When a change is introduced to files under _sass/ directory in www.dev.centos.org, the final files under www.dev.centos.org/assets/css/ are rebuilt automatically thanks to jekyll sass feature. When that happens, other sites can reflect the changes immediately.

  • Contribute to playbooks being used to propagate changes against this dev environment. So to check playbooks do what they need to do, before applying them to prod environment.

Best regards.


Metadata Update from @arrfab:
- Issue tagged with: centos-common-infra, low-trouble, medium-gain

Already tagged but not yet prioritized , but will be done ASAP

Metadata Update from @arrfab:
- Issue assigned to arrfab

In progress and @areguera has info to connect to provisioned instances.
So far (today), the following new public vhosts are reachable:

  • https://blog.dev.centos.org (to test centos wordpress theme)
  • https://lists.dev.centos.org (to test centos mailman theme)

More to come in the next days, between other tasks

Other roles were pushed and the following vhosts are now reachable :

  • https://people.dev.centos.org
  • http://mirror.dev.centos (attention no TLS and some browsers would try https and so different vhost)
  • https://www.dev.centos.org

Worth knowing that nodes are reachable and this is just ansible role and sometimes no content (but you can locally generate some for testing). Closing this request but we'll catch up probably on irc/emails for some details

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Log in to comment on this ticket.

Metadata