Skip to main content

Dev Environment

Overview​

We are currently unable to use UAT for development due to the complexity around merging in and merging out of code between releases. We feel that we need a temporary solution so we are able to test our Auth0 implementation E2E without effecting other in flight work.

Proposal​

dev.rapha.cc (or any other suggested subdomain) would act as a FO hybris node for the time being. Considering that won’t require changes at DB/model level, the idea behind this approach is to save costs from an infrastructure point of view, and in terms of efficiency.

  • dev.rapha.cc consisting in:
    • A single node, FO oriented
    • No processing required (no tasks/jobs)
    • No catalog manipulation (no syncs/changes)
    • No system updates/impexes
  • Utilise the following resources from UAT
    • Database
    • SOLR
    • Media files (hybris media files, /hybris/data/media/)
  • Cloudflare firewall to filter traffic, enabling permissions for Auth0's range
    • Note: No workers required at this initial time
  • Manual or semi-manual release from gitlab branch

This approach requires maintaining the feature branch containing Auth up to date with rapha-cc/-/tree/master, this means that any changes of db.type.system.name need to be aligned with the Auth0 feature branch. To normalise that process, we should keep the Auth feature branch in sync with development in UAT, by performing a sync a day or keeping BAU changes in Hybris models visible to all squads involved.

Notes​

This proposal will not work when we move into checkout development, but would fit nicely with our Auth and Search initiatives.