profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/cmharlow/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Christina Harlow cmharlow Mozilla Beach Haven, NJ

cmharlow/c4lMDCpres 7

Code4Lib MDC OpenRefine Workshop 2015

cmharlow/elag16metadata 6

ELAG 2016 Metadata Migration to RDF, PCDM, Fedora 4 Workshop

cmharlow/BF2 3

BIBFRAME 2 Specs regularly pulled and captured in GitHub

cmharlow/DLF15GeoMetadata 3

DLF 15 Workshop: Enhancing Metadata with Geospatial Data portion

cmharlow/CULMetadataAssessment 2

CUL Metadata Working Group Metadata Assessment Workshop Materials

cmharlow/CULopenrefine 2

Cornell University Libraries OpenRefine Workshop Docs

cmharlow/eCommonsMetadata 2

eCommons Metadata Review

bibliotechy/notflix 1

Generates some less-popular Netflix Categories

cmharlow/dataMunging 1

Data Munging Workshop + Presentation stuff for Royal Library, Copenhagen

push eventmozilla-it/refractr

Christina Harlow

commit sha bd97e7c17af3bc14fa512f6fbdca10d94893965d

pastebin.mozilla.org pointing at updating paste.mozilla.org

view details

Christina Harlow

commit sha dd5653e0acc949e7be533b578361cd9ee9f39c24

krakenbenchmark.mozilla.com decommissioned entirely

view details

push time in a day

delete branch mozilla-it/refractr

delete branch : pastebin-recom-kraken-decom

delete time in a day

PR merged mozilla-it/refractr

Pastebin recom kraken decom

Refractr PR Checklist

JIRA ticket: Came up in context of Let's Encrypt Cert Expiration Alerts

When creating a PR for Refractr, confirm you've done the following steps for smooth CI and CD experiences:

  • [x] Is this the right place for your redirect (e.g. developer.mozilla.com/* redirects should be managed by MDN; other examples here as known)?
  • [x] Have you updated the relevant YAML in the PR?
  • [x] Have you checked the relevant YAML for any possible dupes regarding your domain?
  • [x] Have you checked if there are any TLS cert concerns - e.g. if the domain being redirected already exists, and it is being changed to point at Refractr, is a temporary TLS 'outage' while waiting for Lets Encrypt certification via HTTP challenge okay? If not, have you followed these steps for using DNS challenges with our cert-manager setup?
  • [x] If desired, have you generated the Nginx manually to confirm addition works as expected?
  • [x] If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

After PR merge, next steps include:

  • [ ] If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • [ ] Confirm you are ready and able to perform the requested DNS creation or change post-deploy?
+0 -6

1 comment

1 changed file

cmharlow

pr closed time in a day

pull request commentmozilla-it/refractr

Pastebin recom kraken decom

I know the pastebin.mozilla.org removal from refractr is okay (it is pointing at the updated paste.mozilla.org).

I think the krakenbenchmark.mozilla.com removal from refractr is okay, based on https://github.com/mozilla-it/websre-infra/pull/5

cmharlow

comment created time in a day

PR opened mozilla-it/refractr

Pastebin recom kraken decom

Refractr PR Checklist

JIRA ticket: Came up in context of Let's Encrypt Cert Expiration Alerts

When creating a PR for Refractr, confirm you've done the following steps for smooth CI and CD experiences:

  • [ ] Is this the right place for your redirect (e.g. developer.mozilla.com/* redirects should be managed by MDN; other examples here as known)?
  • [ ] Have you updated the relevant YAML in the PR?
  • [ ] Have you checked the relevant YAML for any possible dupes regarding your domain?
  • [ ] Have you checked if there are any TLS cert concerns - e.g. if the domain being redirected already exists, and it is being changed to point at Refractr, is a temporary TLS 'outage' while waiting for Lets Encrypt certification via HTTP challenge okay? If not, have you followed these steps for using DNS challenges with our cert-manager setup?
  • [ ] If desired, have you generated the Nginx manually to confirm addition works as expected?
  • [ ] If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

After PR merge, next steps include:

  • [ ] If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • [ ] Confirm you are ready and able to perform the requested DNS creation or change post-deploy?
+0 -6

0 comment

1 changed file

pr created time in a day

create barnchmozilla-it/refractr

branch : pastebin-recom-kraken-decom

created branch time in a day

created tagmozilla-it/refractr

tagv0.0.76

yaml -> nginx for redirects and rewrites

created time in 3 days

release mozilla-it/refractr

v0.0.76

released time in 3 days

push eventmozilla-it/refractr

Christina Harlow

commit sha 059e4b199f34155b7dc2daa1bb7370086b308008

add note for MDN-managed redirects

view details

push time in 4 days

delete branch mozilla-it/refractr

delete branch : SE-2238-repair2

delete time in 4 days

PR merged mozilla-it/refractr

add note for MDN-managed redirects

Refractr PR Checklist

JIRA ticket: SE-2238 repair 2, bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1660250

Note: PR adds note for MDN-managed redirects to PR checklist

When creating a PR for Refractr, confirm you've done the following steps for smooth CI and CD experiences:

  • [x] Have you updated the relevant YAML in the PR?
  • [x] Have you checked the relevant YAML for any possible dupes regarding your domain?
  • [x] Have you checked if there are any TLS cert concerns - e.g. if the domain being redirected already exists, and it is being changed to point at Refractr, is a temporary TLS 'outage' while waiting for Lets Encrypt certification via HTTP challenge okay? If not, have you followed these steps for using DNS challenges with our cert-manager setup?
  • [x] If desired, have you generated the Nginx manually to confirm addition works as expected?
  • [x] If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

After PR merge, next steps include:

  • [x] If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • [x] Confirm you are ready and able to perform the requested DNS creation or change post-deploy?
+1 -5

0 comment

2 changed files

cmharlow

pr closed time in 4 days

PR opened mozilla-it/refractr

add note for MDN-managed redirects

Refractr PR Checklist

JIRA ticket: SE-2238 repair 2, bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1660250

Note: PR adds note for MDN-managed redirects to PR checklist

When creating a PR for Refractr, confirm you've done the following steps for smooth CI and CD experiences:

  • [ ] Have you updated the relevant YAML in the PR?
  • [ ] Have you checked the relevant YAML for any possible dupes regarding your domain?
  • [ ] Have you checked if there are any TLS cert concerns - e.g. if the domain being redirected already exists, and it is being changed to point at Refractr, is a temporary TLS 'outage' while waiting for Lets Encrypt certification via HTTP challenge okay? If not, have you followed these steps for using DNS challenges with our cert-manager setup?
  • [ ] If desired, have you generated the Nginx manually to confirm addition works as expected?
  • [ ] If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

After PR merge, next steps include:

  • [ ] If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • [ ] Confirm you are ready and able to perform the requested DNS creation or change post-deploy?
+1 -5

0 comment

2 changed files

pr created time in 4 days

create barnchmozilla-it/refractr

branch : SE-2238-repair2

created branch time in 4 days

created tagmozilla-it/refractr

tagv0.0.75

yaml -> nginx for redirects and rewrites

created time in 4 days

release mozilla-it/refractr

v0.0.75

released time in 4 days

push eventmozilla-it/refractr

Christina Harlow

commit sha 5f2f0d47afde183d67e72ba8d743f58dc35aa172

techspeakers.mozilla.org redirected twice

view details

Christina Harlow

commit sha 3edd3b37e3d58591fa850d381fd4e767f8b4d481

add dupes check to PR checklist, since so many domains

view details

push time in 4 days

delete branch mozilla-it/refractr

delete branch : SE-2238-repair

delete time in 4 days

PR merged mozilla-it/refractr

techspeakers.mozilla.org redirected twice

Refractr PR Checklist

JIRA ticket: SE-2238, https://bugzilla.mozilla.org/show_bug.cgi?id=1660250

Note: PR repairs techspeakers.mozilla.org being redirected twice, plus missing other redirect request in bugzilla ticket (developer.mozilla.com/communities/mozilla-tech-speakers)

When creating a PR for Refractr, confirm you've done the following steps for smooth CI and CD experiences:

  • [x] Have you updated the relevant YAML in the PR?
  • [x] Have you checked if there are any TLS cert concerns - e.g. if the domain being redirected already exists, and it is being changed to point at Refractr, is a temporary TLS 'outage' while waiting for Lets Encrypt certification via HTTP challenge okay? If not, have you followed these steps for using DNS challenges with our cert-manager setup?
  • [x] If desired, have you generated the Nginx manually to confirm addition works as expected?
  • [x] If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

After PR merge, next steps include:

  • [x] If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • [x] Confirm you are ready and able to perform the requested DNS creation or change post-deploy?
+10 -6

0 comment

2 changed files

cmharlow

pr closed time in 4 days

push eventmozilla-it/refractr

Christina Harlow

commit sha d3ba8e12bd81138085ebcfc1854259459c992d1d

add dupes check to PR checklist, since so many domains

view details

push time in 4 days

push eventmozilla-it/refractr

Christina Harlow

commit sha fdb576610a7dbbc432272908b29e6558db6ca1a7

techspeakers.mozilla.org redirected twice

view details

push time in 4 days

PR opened mozilla-it/refractr

techspeakers.mozilla.org redirected twice

Refractr PR Checklist

JIRA ticket: SE-2238, https://bugzilla.mozilla.org/show_bug.cgi?id=1660250

Note: PR repairs techspeakers.mozilla.org being redirected twice, plus missing other redirect request in bugzilla ticket (developer.mozilla.com/communities/mozilla-tech-speakers)

When creating a PR for Refractr, confirm you've done the following steps for smooth CI and CD experiences:

  • [ ] Have you updated the relevant YAML in the PR?
  • [ ] Have you checked if there are any TLS cert concerns - e.g. if the domain being redirected already exists, and it is being changed to point at Refractr, is a temporary TLS 'outage' while waiting for Lets Encrypt certification via HTTP challenge okay? If not, have you followed these steps for using DNS challenges with our cert-manager setup?
  • [ ] If desired, have you generated the Nginx manually to confirm addition works as expected?
  • [ ] If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

After PR merge, next steps include:

  • [ ] If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • [ ] Confirm you are ready and able to perform the requested DNS creation or change post-deploy?
+5 -6

0 comment

1 changed file

pr created time in 4 days

create barnchmozilla-it/refractr

branch : SE-2238-repair

created branch time in 4 days

created tagmozilla-it/refractr

tagv0.0.74

yaml -> nginx for redirects and rewrites

created time in 4 days

release mozilla-it/refractr

v0.0.74

released time in 4 days

push eventmozilla-it/refractr

Brett Kochendorfer

commit sha de46e4b38a61156546115717b52509943f0ac7e1

SE-2237 Redirect for www.mozilla.ch Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1598043 I believe we can now redirect www.mozilla.ch to mozilla.org

view details

Brett Kochendorfer

commit sha 90ad0a54ef1d8e7a0bda602024ea411a6e1858d0

Add bugzilla and jira IDs

view details

push time in 4 days

delete branch mozilla-it/refractr

delete branch : SE-2237

delete time in 4 days

PR merged mozilla-it/refractr

SE-2237 Redirect for www.mozilla.ch

Description

Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1598043 I believe we can now redirect www.mozilla.ch to mozilla.org. DNS is already pointing at refractr. The www subdomain currently 404s. Certificate offered from the www subdomain is a generic k8s ingress certificate.

Refractr PR Checklist

JIRA ticket: [https://mozilla-hub.atlassian.net/browse/SE-2237]

When creating a PR for Refractr, confirm you've done the following steps for smooth CI and CD experiences:

  • [X] Have you updated the relevant YAML in the PR?

Hopefully.

DNS already pointed at refractr and the subdomain www. 404s. Any outage for certificate here should be fine as it is not working right now.

  • [X] If desired, have you generated the Nginx manually to confirm addition works as expected?

I generated the config and looked at it. It looks correct to me.

  • [X] If desired, are you able to connect to EKS (cluster itse-apps-prod-1, namespace fluxcd) to more closely monitor the deploys?

Yes, I certainly can

After PR merge, next steps include:

  • [ ] If going straight from main merge & Stage deploy to a release & production deploy, create the relevant GitHub release with an incremented version / tag applied.
  • [ ] Confirm you are ready and able to perform the requested DNS creation or change post-deploy?

DNS is already created and pointing at refractr.

+3 -0

1 comment

1 changed file

bkochendorfer

pr closed time in 4 days

pull request commentmozilla-it/refractr

SE-2237 Redirect for www.mozilla.ch

wrapping into release today.

bkochendorfer

comment created time in 4 days

push eventmozilla-it/refractr

Brett Kochendorfer

commit sha 7b352e2791b4a8799b1da643b546a11a7dee287e

Redirect techspeakers to community portal This is a request we received through [Bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=1660250). techspeakers.mozilla.org currently resolves to refractr but 404s. This will redirect the url to the community portal. ```sh server { server_name techspeakers.mozilla.org; add_header Strict-Transport-Security "max-age=60; includeSubDomains" always; location = / { return 301 https://community.mozilla.org/en/groups/tech-speakers/; } } ```

view details

Brett Kochendorfer

commit sha 1a7d8906437edecf7dcf488f491f4f2fc94ab944

Change to simple redirect

view details

push time in 4 days

delete branch mozilla-it/refractr

delete branch : SE-2238-community-speakers-url

delete time in 4 days