name: FastAPI People

on:
  schedule:
    - cron: "0 14 1 * *"
  workflow_dispatch:
    inputs:
      debug_enabled:
        description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
        required: false
        default: 'false'

jobs:
  fastapi-people:
    if: github.repository_owner == 'tiangolo'
    runs-on: ubuntu-latest
    steps:
      - name: Dump GitHub context

Sebastián Ramírez <******@****.***> 1712013143 -0500

        All that, on top of all the incredible help provided by a bunch of community members, the [FastAPI Experts](https://fastapi.tiangolo.com/fastapi-people/#experts), that give a lot of their time to come here and help others.

edit_uri: ''
plugins:
  search: null
  macros:
    include_yaml:
    - external_links: ../en/data/external_links.yml
    - github_sponsors: ../en/data/github_sponsors.yml
    - people: ../en/data/people.yml
    - sponsors_badge: ../en/data/sponsors_badge.yml
    - sponsors: ../en/data/sponsors.yml
  redirects:
    redirect_maps:
      deployment/deta.md: deployment/cloud.md

name: "Generate FastAPI People"
description: "Generate the data for the FastAPI People page"
author: "Sebastián Ramírez <******@****.***>"
inputs:
  token:
    description: 'User token, to read the GitHub API. Can be passed in using {{ secrets.FASTAPI_PEOPLE }}'
    required: true
runs:
  using: 'docker'

    img: https://fastapi.tiangolo.com/img/sponsors/mongodb.png
silver:
  - url: https://training.talkpython.fm/fastapi-courses
    title: FastAPI video courses on demand from people you trust
    img: https://fastapi.tiangolo.com/img/sponsors/talkpython-v2.jpg
  - url: https://github.com/deepset-ai/haystack/
    title: Build powerful search from composable, open source building blocks

'environment'. ## Installing The new installer is intended to be modular and very explicit about what is installed. It has far more steps than the Istio installer - but each step is smaller and focused on a specific feature, and can be performed by different people/teams at different times. It is strongly recommended that different namespaces are used, with different service accounts. In particular access to the security-critical production components (root CA, policy, control) should be locked down and restricted....