-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
46 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,42 @@ | ||
#app: | ||
# title: ${ORG_NAME} | ||
# Should be the same as backend.baseUrl when using the `app-backend` plugin. | ||
# baseUrl: ${BASE_URL} | ||
|
||
#backend: | ||
# 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: ${BASE_URL} | ||
# 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. | ||
# listen: ':7007' | ||
|
||
# config options: https://node-postgres.com/api/client | ||
# database: | ||
# client: pg | ||
# connection: | ||
# host: ${POSTGRES_HOST} | ||
# port: ${POSTGRES_PORT} | ||
# user: ${POSTGRES_USER} | ||
# password: ${POSTGRES_PASSWORD} | ||
# https://node-postgres.com/features/ssl | ||
# you can set the sslmode configuration option via the `PGSSLMODE` environment variable | ||
# see https://www.postgresql.org/docs/current/libpq-ssl.html Table 33.1. SSL Mode Descriptions (e.g. require) | ||
# ssl: | ||
# ca: # if you have a CA file and want to verify it you can uncomment this section | ||
# $file: <file-path>/ca/server.crt | ||
app: | ||
title: ${ORG_NAME} | ||
baseUrl: ${BASE_URL} | ||
|
||
organization: | ||
name: ${ORG_NAME} | ||
backend: | ||
baseUrl: ${BASE_URL} | ||
#integrations: | ||
# github: | ||
# - host: github.com | ||
# # This is a Personal Access Token or PAT from GitHub. You can find out how to generate this token, and more information | ||
# # about setting up the GitHub integration here: https://backstage.io/docs/getting-started/configuration#setting-up-a-github-integration | ||
# apps: | ||
# - appId: ${APP_ID} | ||
# clientId: ${CLIENT_ID} | ||
# clientSecret: ${CLIENT_SECRET} | ||
# webhookSecret: ${WEBHOOK_SECRET} | ||
# privateKey: ${PRIVATE_KEY} | ||
#auth: | ||
# # see https://backstage.io/docs/auth/ to learn about auth providers | ||
# environment: production | ||
# providers: | ||
# github: | ||
# production: | ||
# clientId: ${CLIENT_ID} | ||
# clientSecret: ${CLIENT_SECRET} | ||
#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: [] | ||
# import: | ||
# entityFilename: catalog-info.yaml | ||
# pullRequestBranchName: backstage-integration | ||
# rules: | ||
# - allow: [Component, System, API, Resource, Location] | ||
# providers: | ||
# github: | ||
# default: | ||
# organization: ${GITHUB_ORG} # string | ||
# schedule: # optional; same options as in TaskScheduleDefinition | ||
# # supports cron, ISO duration, "human duration" as used in code | ||
# frequency: { minutes: 30 } | ||
# # supports ISO duration, "human duration" as used in code | ||
# timeout: { minutes: 3 } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters