@backstage/create-app 0.0.0-nightly-20220421024404 → 0.0.0-nightly-20220422024928

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # @backstage/create-app
2
2
 
3
- ## 0.0.0-nightly-20220421024404
3
+ ## 0.0.0-nightly-20220422024928
4
4
 
5
5
  ### Patch Changes
6
6
 
@@ -8,6 +8,42 @@
8
8
 
9
9
  To apply this change to an existing app, update your `packages/backend/Dockerfile` to match the documented `Dockerfile` at https://backstage.io/docs/deployment/docker#host-build.
10
10
 
11
+ - 28bbf5aff6: Added some instruction comments to the generated config files, to clarify the
12
+ usage of `backend.baseUrl` and `backend.listen.host`. Importantly, it also per
13
+ default now listens on all IPv4 interfaces, to make it easier to take the step
14
+ over to production. If you want to do the same, update your
15
+ `app-config.production.yaml` as follows:
16
+
17
+ ```diff
18
+ backend:
19
+ listen:
20
+ port: 7007
21
+ + host: 0.0.0.0
22
+ ```
23
+
24
+ Also, updated the builtin backend Dockerfile to honor the
25
+ `app-config.production.yaml` file. If you want to do the same, change
26
+ `packages/backend/Dockerfile` as follows:
27
+
28
+ ```diff
29
+ -COPY packages/backend/dist/bundle.tar.gz app-config.yaml ./
30
+ +COPY packages/backend/dist/bundle.tar.gz app-config*.yaml ./
31
+ RUN tar xzf bundle.tar.gz && rm bundle.tar.gz
32
+
33
+ -CMD ["node", "packages/backend", "--config", "app-config.yaml"]
34
+ +CMD ["node", "packages/backend", "--config", "app-config.yaml", "--config", "app-config.production.yaml"]
35
+ ```
36
+
37
+ If you look carefully, this adds a glob match on app-config files. For those
38
+ that try out the build flows locally, you also want to make sure that the docker
39
+ daemon does NOT pick up any local/private config files that might contain
40
+ secrets. You should therefore also update your local `.dockerignore` file at the
41
+ same time:
42
+
43
+ ```diff
44
+ +*.local.yaml
45
+ ```
46
+
11
47
  - 344ea56acc: Bump `commander` to version 9.1.0
12
48
 
13
49
  ## 0.4.26
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@backstage/create-app",
3
3
  "description": "A CLI that helps you create your own Backstage app",
4
- "version": "0.0.0-nightly-20220421024404",
4
+ "version": "0.0.0-nightly-20220422024928",
5
5
  "private": false,
6
6
  "publishConfig": {
7
7
  "access": "public"
@@ -3,3 +3,4 @@ node_modules
3
3
  packages
4
4
  !packages/backend/dist
5
5
  plugins
6
+ *.local.yaml
@@ -1,8 +1,19 @@
1
1
  app:
2
- # Should be the same as backend.baseUrl when using the `app-backend` plugin
2
+ # Should be the same as backend.baseUrl when using the `app-backend` plugin.
3
3
  baseUrl: http://localhost:7007
4
4
 
5
5
  backend:
6
+ # Note that the baseUrl should be the URL that the browser and other clients
7
+ # should use when communicating with the backend, i.e. it needs to be
8
+ # reachable not just from within the backend host, but from all of your
9
+ # callers. When its value is "http://localhost:7007", it's strictly private
10
+ # and can't be reached by others.
6
11
  baseUrl: http://localhost:7007
7
12
  listen:
8
13
  port: 7007
14
+ # The following host directive binds to all IPv4 interfaces when its value
15
+ # is "0.0.0.0". This is the most permissive setting. The right value depends
16
+ # on your specific deployment. If you remove the host line entirely, the
17
+ # backend will bind on the interface that corresponds to the backend.baseUrl
18
+ # hostname.
19
+ host: 0.0.0.0
@@ -15,6 +15,9 @@ backend:
15
15
  baseUrl: http://localhost:7007
16
16
  listen:
17
17
  port: 7007
18
+ # Uncomment the following host directive to bind to all IPv4 interfaces and
19
+ # not just the baseUrl hostname.
20
+ # host: 0.0.0.0
18
21
  csp:
19
22
  connect-src: ["'self'", 'http:', 'https:']
20
23
  # Content-Security-Policy directives follow the Helmet format: https://helmetjs.github.io/#reference
@@ -28,7 +28,7 @@ RUN tar xzf skeleton.tar.gz && rm skeleton.tar.gz
28
28
  RUN yarn install --frozen-lockfile --production --network-timeout 300000 && rm -rf "$(yarn cache dir)"
29
29
 
30
30
  # Then copy the rest of the backend bundle, along with any other files we might want.
31
- COPY packages/backend/dist/bundle.tar.gz app-config.yaml ./
31
+ COPY packages/backend/dist/bundle.tar.gz app-config*.yaml ./
32
32
  RUN tar xzf bundle.tar.gz && rm bundle.tar.gz
33
33
 
34
- CMD ["node", "packages/backend", "--config", "app-config.yaml"]
34
+ CMD ["node", "packages/backend", "--config", "app-config.yaml", "--config", "app-config.production.yaml"]