https://guide.rladies.org/organizers/tech/index.html Hugo en https://guide.rladies.org/organizers/tech/accounts/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/accounts/index.html Slack Once you initiate the process of becoming an organizer by sending an email to chapter [at] rladies [dot] org, you will be sent and invite to the R-Ladies Organizers’ Slack. Please add your city or chapter to your Slack profile. The Organizers’ Slack has a lot of channels that cover different topics. Explore them and join the ones that you find useful. You can create a channel on the global Slack for communication within the organizing team of your chapter, e.g., #rladies-san-francisco. There is also a global “all the R-Ladies” Slack. Etiquette for Slack Prefer asking in official channels rather to DM people or sending an email. This allows us to create collective knowledge, i.e., learning from other experiences. It will also ensure you a faster response, as more people will see your question. https://guide.rladies.org/organizers/tech/email/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/email/index.html General info about emails for R-Ladies chapters. Since November 2022 R-Ladies migrated to Google Work Space, and e-mail accounts are now handled using gmail infrastructure. All R-Ladies chapters use the @rladies.org domain. If you need help to manage your email account there are official google instructions on how to use a Gmail account A new account After we have created your chapter email account you will receive an email like this: https://guide.rladies.org/organizers/tech/security/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/security/index.html As organizers you will be responsible for accounts such as email and social media accounts. Here are some steps that will help reduce the risk of someone’s hacking into your account. We also recommend reading “Ten quick tips for staying safe online” by Danielle Smalls and Greg Wilson. Use a personal password manager! For your personal use (for R-Ladies things and in general!), we strongly recommend using a personal password manager, be it a free one like KeePass (with a back-up you’d set up on Dropbox or Google Drive) or Bitwarden, or a paid service like 1Password. https://guide.rladies.org/organizers/tech/brand/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/brand/index.html Info Branding information has moved to the dedicated Branding section. See: Brand overview for the full colour palette, typography, and logo guidelines Chapter branding for guidance on adopting the new RLadies+ identity Social media templates for event graphics and social media posts https://guide.rladies.org/organizers/tech/github-pat/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/github-pat/index.html Several R-Ladies workflows need to reach across repositories — triggering a website preview build from the directory repo, posting a comment back on a PR in a different repo, or checking whether someone belongs to an org team. The standard GITHUB_TOKEN can’t do any of this. That’s what GLOBAL_GHA_PAT is for. Which repositories use it Repository Workflow What the PAT does directory airtable-update.yml Triggers a website preview build on rladies.github.io directory retrigger-website.yml Re-triggers a website preview build on rladies.github.io awesome-rladies-blogs trigger-website.yaml Triggers a website preview build on rladies.github.io rladies.github.io hello.yaml Checks whether a PR/issue author belongs to the rladies/global team rladies.github.io build-preview.yaml Posts build status comments to the originating repo and downloads artifacts from directory global-team offboarding-finalise.yml Removes departing members from organization teams Creating a new PAT Who should create it Use a GitHub account belonging to someone on the leadership team who is unlikely to leave soon. If that person leaves, the PAT must be rotated — see Rotating the token below. https://guide.rladies.org/organizers/tech/github-admin-token/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/github-admin-token/index.html Three R-Ladies repos rely on a secret called ADMIN_TOKEN — a GitHub PAT with elevated permissions that lets workflows push to protected branches, invite new org members, and manage teams. If it expires or the person who created it leaves, several automated processes stop working silently. What it does The ADMIN_TOKEN handles operations that the standard GITHUB_TOKEN cannot — things that require org-level access or the ability to bypass branch protection. https://guide.rladies.org/organizers/tech/airtable/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/airtable/index.html R-Ladies uses Airtable as the backend for directory submissions and Global Team membership data. Two repos connect to Airtable through a shared API key stored as AIRTABLE_API_KEY. Airtable bases We maintain separate Airtable bases for different purposes: Base ID Purpose Key tables Used by appzYxePUruG9Nwyg Directory submissions Submissions, Languages, Countries directory appZjaV7eM0Y9FsHZ Global Team Members, Teams, Alumni rladies.github.io The directory repo pulls new member submissions every Friday via airtable-update.yml and deletes processed records after PRs merge via airtable-delete.yml. https://guide.rladies.org/organizers/tech/ssh-deploy-keys/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/ssh-deploy-keys/index.html The website build process needs to clone two private repos — directory and awesome-rladies-blogs — and push directly to a protected branch. Regular GITHUB_TOKEN permissions don’t stretch that far, so we use SSH deploy keys. Current keys Three deploy keys are stored as secrets in rladies.github.io: Secret name Deploy key on repo Purpose Write access? ssh_directoryy_repo rladies/directory Clone directory data during website builds No (read-only) RLADIES_BLOGS_KEY rladies/awesome-rladies-blogs Clone blog feed data during website builds No (read-only) push-to-protected rladies/rladies.github.io Push Airtable team data updates to the protected main branch Yes (write) Yes, ssh_directoryy_repo has a typo — two ys. Renaming it would require updating the workflow files that reference it, so we’ve left it as-is. https://guide.rladies.org/organizers/tech/meetup-api/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/meetup-api/index.html The meetup_archive repo connects to the Meetup.com API every 12 hours to archive chapter and event data. It uses JWT-based authentication, which requires three secrets. Secrets Secret What it is JWT_TOKEN A JWT signing key (RSA private key) registered with the Meetup API JWT_ISSUER The Meetup user ID associated with the API application CLIENT_KEY The OAuth client key from the Meetup API application These are stored as repo-level secrets on rladies/meetup_archive. https://guide.rladies.org/organizers/tech/build-architecture/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://guide.rladies.org/organizers/tech/build-architecture/index.html The R-Ladies website build is the most interconnected piece of our infrastructure. Three repos feed into it, multiple secrets connect them, and a failure in one place can silently break the chain. This page maps out how everything fits together. The build pipeline When someone submits a new directory entry or blog post, the path to the live website looks like this: Airtable receives a new submission (directory entry) or a contributor opens a PR (blog) Source repos (directory or awesome-rladies-blogs) process the data and create or update a PR The source repo triggers a preview build on rladies.github.io via workflow_dispatch rladies.github.io clones the source repos via SSH, builds the Hugo site, and deploys a preview to Netlify The preview build posts a comment back to the originating PR with the preview link Once the PR merges, the next scheduled production build (every 12 hours) picks up the changes What connects to what directory rladies.github.io airtable-update.yml ──dispatch──▶ build-preview.yaml retrigger-website.yml ──dispatch──▶ build-preview.yaml │ awesome-rladies-blogs ├── clones directory (SSH) trigger-website.yaml ──dispatch──▶ ├── clones blogs (SSH) ├── deploys to Netlify └── comments on source PR Secrets involved Each connection in the diagram above requires a specific secret: