Skip to content

Deploying New Prime Pages

BrysonXiao edited this page Dec 3, 2022 · 3 revisions

Deploying New Prime Pages

This wiki page aims to provide information on how to deploy new prime pages and document previous error encounters.

Process

Overview

gdrive is where writers fill out aml files for articles
One important aml file is the prime.map.articles.to.issues.
aml files uploaded onto Kerchhoff via Gdrive, Kerchoff is an internal tool to get aml files to prod.
Prime has source code in PRILUSBY and Prime gets its page data from Kerckhoff.
After aml is updated, rebuild prime.dailybruin.com and dump its build folder into the AWS s3 bucket.

Specifics

index.html and page-data.json files

index.html and page-data.json files need to be uploaded to s3 bucket for:

  • all/
  • pastissues/
  • current issue e.g. 'fall22/'
  • each article that is in the current issue
  • index.html in the root folder
  • page-data/index/page-data.json

Troubleshooting

Previous Issues

Issue shows 404 in development (Fall 2022)

Screen Shot 2022-11-28 at 5 40 56 PM

Believed Cause: The map.aml file needs to be updated by prime writers and reuploaded to kerckhoff Screen Shot 2022-11-28 at 5 42 27 PM

Kerchoff got stuck fetching large files from gdrive and lacked functionality to cancel the fetching when stuck (Fall 2022)

Handled by internal tools team.

Prod being different from dev (Fall 2022)

An article is missing a section in prod but the whole article shows up find in dev. Prod being different from dev should be a rare occurrence in PRILUSBY, but may have to do with build scripts?
Believed Cause: Combination of aml issues and incomplete deploy. All index file uploads need to be accompanied with runtime webpack/styling files, and vice versa.

'issu' (embedded magazine on the site) isn't working

Currently under investigation.