sourcegraph/cmd/frontend
Stefan Hengl d3528061cd
chore(worker): move llm token counter to worker (#64008)
This moves the LLM token counter from `frontend` to the `worker`.

Test plan:
new unit test
2024-07-24 10:03:33 +02:00
..
auth [logging] Only record events if a new user was created (#64004) 2024-07-23 13:48:11 +02:00
backend feat(code insights): language stats speed improvements by using archive loading (#62946) 2024-07-18 08:40:48 +02:00
dotcomproductsubscriptiontest feat/enterprise-portal: ConnectRPC layer for {Get/List}CodyGatewayAccess (#62771) 2024-05-27 13:39:57 -07:00
enterprise chore: centralize logic for disabling Batch Changes on dotcom (#63370) 2024-06-24 08:37:45 -07:00
envvar Move dotcom check out of cmd/frontend (#60810) 2024-03-04 16:05:16 +00:00
external fix/telemetry(auth): return authenticated context from session.SetActorFromUser (#62701) 2024-05-15 16:48:42 -07:00
globals chore: Simplify Branding (#61905) 2024-04-16 09:33:03 +02:00
graphqlbackend Implement server-side single-repo context fetching for RFC 969 (#63980) 2024-07-23 13:36:00 +02:00
hubspot chore: remove obsolete tracking code for Cody App downloads (#63364) 2024-06-23 21:48:31 -07:00
internal chore(worker): move llm token counter to worker (#64008) 2024-07-24 10:03:33 +02:00
oneclickexport dotcom: Remove on-demand cloning of repositories (#63321) 2024-06-26 14:53:14 -07:00
registry Move dotcom check out of cmd/frontend (#60810) 2024-03-04 16:05:16 +00:00
shared Prompt Library (#63872) 2024-07-18 16:04:55 -07:00
webhooks webhooks: Add support for secrets for Bitbucket Cloud (#63198) 2024-06-18 11:54:01 +02:00
BUILD.bazel omit go:embed of big assets from sg start single-program-experimental-blame-sqs (#63477) 2024-06-25 23:08:53 +00:00
image_test.yaml Switch to OCI/Wolfi based image (#52693) 2023-06-02 12:12:52 +02:00
main.go omit go:embed of big assets from sg start single-program-experimental-blame-sqs (#63477) 2024-06-25 23:08:53 +00:00
README.md

frontend

The frontend serves our web application and hosts our GraphQL API.

Typically there are multiple replicas running in production to scale with load.

Application data is stored in our PostgreSQL database.

Session data is stored in the Redis store, and non-persistent data is stored in the Redis cache.