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

Prettier fix for line length

Browse Source
This commit is contained in:
Harvey
2020-10-26 09:49:54 -04:00
parent 5010bf5fe0
commit 2e04225056
4 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started/deployment-helm.md
+2 -2
View File
@@ -10,8 +10,8 @@ sidebar_label: Kubernetes and Helm
An example Backstage app can be deployed in Kubernetes using the
[Backstage Helm charts](https://github.com/spotify/backstage/tree/master/contrib/chart/backstage).
First, choose a DNS name where Backstage will be hosted, and create a YAML file for
your custom configuration.
First, choose a DNS name where Backstage will be hosted, and create a YAML file
for your custom configuration.
```yaml
appConfig:
docs/overview/architecture-overview.md
+8 -8
View File
@@ -158,19 +158,19 @@ https://circleci.com.
## Databases
As we have seen, both the `lighthouse-audit-service` and `catalog-backend` require a
database to work with.
As we have seen, both the `lighthouse-audit-service` and `catalog-backend`
require a database to work with.
At the time of writing, the `lighthouse-audit-service` requires PostgreSQL to work
with. The service catalog backend uses an in-memory Sqlite3 instance. This is a
development-oriented setup and there are plans to support other databases in the
future.
At the time of writing, the `lighthouse-audit-service` requires PostgreSQL to
work with. The service catalog backend uses an in-memory Sqlite3 instance. This
is a development-oriented setup and there are plans to support other databases
in the future.
To learn more about the future of databases and Backstage, see the following
GitHub issues.
* [Knex + Plugins (Multiple vs Single Database) · Issue #1598 · spotify/backstage](https://github.com/spotify/backstage/issues/1598)
* [Update migrations to support postgres by dariddler · Pull Request #1527 · spotify/backstage](https://github.com/spotify/backstage/pull/1527#discussion_r450374145)
- [Knex + Plugins (Multiple vs Single Database) · Issue #1598 · spotify/backstage](https://github.com/spotify/backstage/issues/1598)
- [Update migrations to support postgres by dariddler · Pull Request #1527 · spotify/backstage](https://github.com/spotify/backstage/pull/1527#discussion_r450374145)
## Containerization
docs/plugins/testing.md
+1 -1
View File
@@ -285,7 +285,7 @@ jest.mock('./MyApi'); // Instruct Jest to swap all future imports of './MyApi.js
import MyApi from './MyApi'; // Will actually return the contents of the file in the __mocks__ folder now
it ('loads data', (done) => {
it('loads data', done => {
MyApi.fetchSomethingFromServer().then(result => {
expect(result).toBe('some result object simulating server data here');
done();
docs/tutorials/journey.md
+6 -6
View File
@@ -239,12 +239,12 @@ hits merge.
# 8. Attack of the Clones
Sam just released v1.8.4 of the plugin, and at this point it's so popular that a
couple of other plugins have started depending on the `sam.wise/spotify-track-id`
annotation. One such plugin being the `spotify-album-art` plugin that can
display the album art of the theme tune as the background of the entity header.
Sam thinks it's all pretty cool, but doesn't like that the annotation that was
once an internal concern of the plugin is now becoming a standard in the
community.
couple of other plugins have started depending on the
`sam.wise/spotify-track-id` annotation. One such plugin being the
`spotify-album-art` plugin that can display the album art of the theme tune as
the background of the entity header. Sam thinks it's all pretty cool, but
doesn't like that the annotation that was once an internal concern of the plugin
is now becoming a standard in the community.
In order to standardize the annotation in Backstage, Sam submits a Pull Request
to the Backstage Core repo. The request suggests a new well-known metadata