-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy path.env.example
More file actions
122 lines (98 loc) · 5.16 KB
/
Copy path.env.example
File metadata and controls
122 lines (98 loc) · 5.16 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
# shellcheck disable=SC2148
# shellcheck disable=SC2034
# This file contains defaults that are useful for development.
# It's not recommended to use this configuration for a production deployment.
# === Runtime Server Configuration ===
# Run the server with the `--help` flag to learn more about the individual settings.
# This default is designed to filter out a lot of noise, if you're
# debugging anything you'd usually want to change these settings
RUST_LOG=debug,sqlx::query=warn,hyper_util::client=info,sea_orm_migration=warn,sea_orm=info,h2=info,rustls=info,gitlab=warn
# Socket to listen on
BUILDBTW_LISTEN=0.0.0.0:8080
# TLS certificate and key for the server
# When both are set, the server will use TLS.
# Local builds do not work with self-signed certificates, so this is commented
# out by default.
# Local dev certificates in cert/ are generated by `just gen-dev-cert`.
# In production, TLS is typically handled by a reverse proxy, so these should be left unset.
# BUILDBTW_TLS_CERT=cert/buildbtw.cert
# BUILDBTW_TLS_KEY=cert/buildbtw.key
# URL the backend server is reachable at
# For development, we use the `.localhost` TLD as it should redirect to loopback:
# https://datatracker.ietf.org/doc/html/rfc6761#section-6.3
BUILDBTW_SERVER_URL=https://buildbtw.localhost:8080
# Path to the SQLite database file
BUILDBTW_DATABASE_FILE="buildbtw_backend.sqlite"
# A location for storing data such as cloned package source repositories, staging repos,
# or built packages. At the time of writing, cloning all package source repositories
# (which is the default for normal operation) will require about 5GB, and
# depending on your number of builds, this can grow a lot larger.
# For development, the recommended default is to store this outside of the code repository.
# When omitted, uses the project XDG_DATA_HOME directory by default.
BUILDBTW_DATA_DIR="../buildbtw-data"
# Collect tokio console telemetry
# When enabling this, make sure to also enable the `tokio_unstable` cfg below
BUILDBTW_TOKIO_CONSOLE_TELEMETRY=false
# Do not use this value for production.
BUILDBTW_COOKIE_ENCRYPTION_KEY=PhoaTaiZie7zug5oojai3BaesieTahloghienavaitee4eeJuas9xohwei3Zai0k
# If true, run a podman container with authelia as an OIDC provider
# alongside the buildbtw server for local development.
# This container assumes a `BASE_URL` of "http://buildbtw.localhost:8080". If you change the
# base URL, you'll need to change the authelia config at `authelia/configuration.yml` as well.
BUILDBTW_RUN_AUTHELIA_CONTAINER=true
# This value is used below in `BUILDBTW_OIDC_ISSUER_URL` as well
BUILDBTW_AUTHELIA_CONTAINER_PORT=9091
# Configuration for logging in using an OIDC provider
# For local development, it's recommended to uses `BUILDBTW_RUN_AUTHELIA_CONTAINER=true` for a local OIDC provider.
# Credentials
BUILDBTW_OIDC_CLIENT_ID=buildbtw-test
# Takes precedence over `BUILDBTW_OIDC_CLIENT_SECRET_PATH`.
BUILDBTW_OIDC_CLIENT_SECRET=insecure_secret
# Path to a file containing the OIDC client secret.
# Default: $XDG_CONFIG_HOME/buildbtw/BUILDBTW_OIDC_CLIENT_SECRET
# BUILDBTW_OIDC_CLIENT_SECRET_PATH=
# URL we can reach the provider at
BUILDBTW_OIDC_ISSUER_URL=https://authelia.buildbtw.localhost:9091
# User-visible descriptor of the OIDC provider
BUILDBTW_OIDC_ISSUER_NAME=Authelia
BUILDBTW_OIDC_ADMIN_GROUPS="Admin Group"
BUILDBTW_OIDC_PACKAGE_MAINTAINER_GROUPS="Package Maintainer Group"
# Used for:
# - Downloading the GraphQL API schema
# - Querying for changes to package source repos
# - Fetching package source repos
#
# This needs the `read_api` scope.
# Optional: for dispatching builds to gitlab, this needs the `api` scope.
# Takes precedence over `BUILDBTW_GITLAB_TOKEN_PATH`.
BUILDBTW_GITLAB_TOKEN=
# Path to a file containing the gitlab token.
# Default: $XDG_CONFIG_HOME/buildbtw/BUILDBTW_GITLAB_TOKEN
# BUILDBTW_GITLAB_TOKEN_PATH=
# This needs to be a valid URL, including the protocol.
BUILDBTW_GITLAB_DOMAIN=https://gitlab.archlinux.org
# Clone package source repositories from this group.
# When changing this, make sure to update remote URLs of already cloned
# repositories as the repo updater does not do this for you.
BUILDBTW_GITLAB_PACKAGES_GROUP=packaging-buildbtw-dev/packages
# Update package source repositories in the background.
BUILDBTW_UPDATE_SOURCE_REPOS=true
# Automatically create new iterations for buildspaces when new commits cause their build graph to change.
BUILDBTW_AUTO_CREATE_ITERATIONS=true
# Token for uploading build artifacts to the server.
# If left out, builds will not be uploaded.
# Takes precedence over `BUILDBTW_EXECUTOR_TOKEN`.
# BUILDBTW_EXECUTOR_TOKEN=
# Path to a file containing the gitlab token.
# Default: $XDG_CONFIG_HOME/buildbtw/BUILDBTW_EXECUTOR_TOKEN
# BUILDBTW_EXECUTOR_TOKEN_PATH=
# Where to dispatch builds. `local-vmexec` or `gitlab-pipelines`.
# If left out, builds are not dispatched.
# For `local-vmexec`, you need to disable TLS if using self-signed certificates
# since we don't inject the self-signing CA into the VM.
BUILDBTW_DISPATCH_BUILDS_TO=local-vmexec
# === Compile-time Server Configuration ===
# For tokio-console
# TODO does this result in a lot of recompilation of dependencies?
# probably because rust-analyzer doesn't have this set?
# RUSTFLAGS="--cfg tokio_unstable"