-
Notifications
You must be signed in to change notification settings - Fork 0
/
app-config.production.yaml
80 lines (79 loc) · 2.75 KB
/
app-config.production.yaml
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
app:
# Should be the same as backend.baseUrl when using the `app-backend` plugin.
baseUrl: ${PROTOCOL}://${HOSTNAME}
backend:
csp:
upgrade-insecure-requests: false
img-src: ["'self'", "https://itsyndicate.org", "https://gitlab.com", "https://secure.gravatar.com"]
listen: ':7007'
# Note that the baseUrl should be the URL that the browser and other clients
# should use when communicating with the backend, i.e. it needs to be
# reachable not just from within the backend host, but from all of your
# callers. When its value is "http://localhost:7007", it's strictly private
# and can't be reached by others.
baseUrl: ${PROTOCOL}://${HOSTNAME}
# The listener can also be expressed as a single <host>:<port> string. In this case we bind to
# all interfaces, the most permissive setting. The right value depends on your specific deployment.
cors:
origin: ${PROTOCOL}://${HOSTNAME}
# config options: https://node-postgres.com/apis/client
database:
client: better-sqlite3
connection: ':memory:'
reading:
allow:
- host: ${GITLAB_HOSTNAME}
gitlab:
allowedKinds:
- Component
- Resource
auth:
environment: production
providers:
guest: {}
gitlab:
production:
clientId: ${AUTH_GITLAB_CLIENT_ID}
clientSecret: ${AUTH_GITLAB_CLIENT_SECRET}
audience: https://${GITLAB_HOSTNAME}
signIn:
resolvers:
- resolver: emailLocalPartMatchingUserEntityName
- resolver: emailMatchingUserEntityProfileEmail
scaffolder:
# see https://backstage.io/docs/features/software-templates/configuration for software template options
defaultAuthor:
name: ITSyndicate
email: itsyndicate@gmail.com
#catalog:
# Overrides the default list locations from app-config.yaml as these contain example data.
# See https://backstage.io/docs/features/software-catalog/#adding-components-to-the-catalog for more details
# on how to get entities into the catalog.
# locations: []
catalog:
rules:
- allow:
- API
- Domain
- Component
- Location
- Resource
- System
- Template
- AWSEnvironment
- AWSEnvironmentProvider
providers:
backstageOpenapi:
plugins:
- catalog
- search
gitlab:
GitLabProvider:
host: ${GITLAB_HOSTNAME} # Identifies one of the hosts set up in the integrations
orgEnabled: true
allowInherited: true
schedule: # Same options as in SchedulerServiceTaskScheduleDefinition. Optional for the Legacy Backend System.
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 5 }
# supports ISO duration, "human duration" as used in code
timeout: { minutes: 3 }