canonical / webteam.canonical.com Goto Github PK

Expected Behavior

Opening the masterclasses URL should return the masterclasses page

Current Behavior

A 502 error is returned

Possible Solution

• So far the issue seems to have been narrowed down to an Out of Memory exception, which causes Gunicorn workers to be shut down and restarted whenever /masterclasses is accessed.
• Between worker restarts, the proxy returns a 502 error.
• Increasing the memory for this container might solve this issue

Steps to Reproduce

1. Open webteam.canonical.com/masterclasses
2. Open webteam.staging.canonical.com/masterclasses

Summary

• Multistage builds to decrease image size, faster image building.
• Update .dockerignore to ignore files uncessary in prod
• Update image to Ubuntu Focal

Add commit data for releases table
Refactor back-end and front-end to merge into single source of data (all prod, staging domains and repos info are in one place)
Add test for domain-info endpoint
Remove some sites that are down (no jenkins job), archived (github repo) or obsolete (don't exist anywhere).
Removed sites that will not be supported because they have been moved to ubuntu.com (e.g. partners.ubuntu.com, tutorials.ubuntu.com)

This repository is still using CircleCI. We should plan some time to migrate to GitHub Actions.

Some links from the homepage give a 504 Gateway Time-out

• Team Members
• Random Colleague
• Canonicool 500 : Internal Server Error

We are missing the Juju GUI project from the list.

All links are broken on README.

https://canonical-web-and-design.github.io/practices/ results in a 404 now

Update the headers to remove the caching on this site. Old releases are being triggered by using this site.

We're adding country inputs by default on all forms. Perhaps we should make it a component that can easily be reused on all sites and maintained from a central source.

Just a thought.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined

Update the headers to remove the caching on this site. Old releases are being triggered by using this site.

Trying to visit that page results in either 502 Bad Gateway, or a 500:

The table should default to sort by age of the last staging build with the ability to change the sorting on the other table headers.

We should display the number of commits behind staging is from production as an indication of staleness.

Make a top-level "training" section which will include suggestions for training courses that people could do. This content should be pulled from ... Discourse? And be editable by all.

• Go to https://webteam.canonical.com/
• Click "Guides" in the top nav
• You'll see an error stating that the page tried to redirect you too many times

This doesn't happen locally, instead it takes you to the SSO login page, and redirects you to /guides as expected. It's also affecting #93.

By showing how many commits (or other similar metric) production is behind the master/main branch this will allow us to know in a quick look which sites haven't been released in a while.

The practices content is now internal at https://discourse.canonical.com/c/web-and-design-team/7, but we should still expose this publicly on webteam.canonical.com when we get a chance.

Originally put forward by @nottrobin in #93 (review)

Pagination behaviour

When you go to page 2, the information about "next session" disappears. This is surprising. I personally think that pagination should never fundamentally change a page. But I understand why you hide that section - because it pushes down the actual list content below the fold, so when you arrive back at the top of page 2, you wouldn't even be able to see the results if you kept that section.

Which kind of highlights that that header section takes up a lot of space.

Is there no way to merge the "next session" information into the top line of the header, and then leave all that information in-place on pagination?

Cache session sheets loaded into the /masterclasses template. This should help speed up the load time for /masterclasses.

We should conditionally display the release button based on if there commit ids from staging and production match.

At present, the /masterclasses page simply shows as empty if the private key is missing. This is fundamentally confusing behaviour - that page is not functional without being connected to the spreadsheet, so it should clearly show an error saying so.

It would be really useful to see if any staging (or ideally also production) deployment is in progress.

A helpful addition would be at least a link to jenkins (staging and production) to see current build or history of builds.