paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 48 Packages Projects Releases Wiki Activity

docs: correct "Github" to "GitHub" in multiple documentation files

Browse Source 
Signed-off-by: ryoku4 <122875619+ryoku4@users.noreply.github.com>
This commit is contained in:
ryoku4
2026-05-23 00:23:27 +09:00
parent 80d86dbbd2
commit 247ec64ba5
7 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/golden-path/deployment/__meta__.md
+2 -2
View File
@@ -21,7 +21,7 @@ Users are expected to already have created a Backstage application, but we have
## Prerequisites
The user should already have created a Backstage application (`create-app`) and pushed their code to an origin in a source control management system (Github, Gitlab, etc). They should have a handle on how their company builds and deploys code.
The user should already have created a Backstage application (`create-app`) and pushed their code to an origin in a source control management system (GitHub, Gitlab, etc). They should have a handle on how their company builds and deploys code.
## Deploying Backstage
@@ -47,7 +47,7 @@ Use this section to walk through database options, talk through why Postgres is
### Authentication
By default, Backstage lets users login through a guest user. While that's a good fit for a solid developer experience locally, it can open up security holes when it's deployed to production. For that reason, you should configure a different authentication provider. See the docs at `auth/*`. A solid choice is Github authentication - your target audience with a developer portal should already have access to Github.
By default, Backstage lets users login through a guest user. While that's a good fit for a solid developer experience locally, it can open up security holes when it's deployed to production. For that reason, you should configure a different authentication provider. See the docs at `auth/*`. A solid choice is GitHub authentication - your target audience with a developer portal should already have access to GitHub.
## Deployment Guides