From 97c156be88b5988c2ac7d580ef88ad7c4a6a2a71 Mon Sep 17 00:00:00 2001 From: William Carroll Date: Wed, 27 Mar 2019 18:28:59 +0000 Subject: [PATCH] Support SpeWall in bash variables NOTE: consider migrating from GH private repo to Google's Git on Borg. This is preferable since GH gets hacked and private repos can be exposed. While a path to a Google 3 repo like SpeWall may not pose a large security risk, it certainly isn't optimal. Imagine a path to a repository whose name leaked a secret project. Two options: 1. embrace encryption options like Mozilla's `sops` and remain on GH private 2. switch wholesale from private GH to GoB 3. classify "sensitve" parts of dotfiles as such and move those to GoB and keep everything else on private GH One added perk of switching to GoB is saving the $7 monthly fee to support private GH repos. --- configs/shared/zsh/variables.zsh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/configs/shared/zsh/variables.zsh b/configs/shared/zsh/variables.zsh index 129b62631..f107d2092 100644 --- a/configs/shared/zsh/variables.zsh +++ b/configs/shared/zsh/variables.zsh @@ -21,6 +21,11 @@ hash -d escalations=./corp/gtech/pto/tda/beacons_extension hash -d ultra=./ads/doubleclick/systems/crm hash -d incentives_fe=./experimental/adservices/jarvis/jarvis_extension/jarvis_staging/js hash -d incentives_be=./experimental/adservices/tesseract/handlers/incentives +hash -d spewall_fe=./alkali/apps/speakeasydashboard +hash -d spewall_be=./alkali/apps/speakeasydashboard +hash -d spewall_be=./java/com/google/alkali/applications/speakeasydashboard +hash -d spewall_protos=./google/internal/alkali/applications/speakeasydashboard +hash -d spewall_tests=./javatests/com/google/alkali/applications/speakeasydashboard # 8-bit colors black='\u001b[30m'