* feature(techdocs): JIT generation of techdocs
* Fix linting issues
* Add Techdocs tab to entity page
* Added missing dep
* Added missing dep
* Removed duplicate dep
* Better tab navigation
* Update label on entity page to say docs
* Fix lint issue
* Move building of docs from entity to a function
* feature(techdocs): JIT generation of techdocs
* Fix linting issues
* Add Techdocs tab to entity page
* Added missing dep
* Added missing dep
* Removed duplicate dep
* Better tab navigation
* Update label on entity page to say docs
* Fix lint issue
* Move building of docs from entity to a function
* attempt to add back react as a dep
* Fixed failing test
* fix(techdocs): Hopefully fixed tests
* Fixed another failing test
* Initial apiRef for techdocs storage
* Cleaned up some code in reader
* test(headertabs): add tests to HeaderTabs component
* fix(headertabs): change tab mock id
* fix(techdocs-generator): fix problem with macOS symlink to tmp folder
* fix(lint): remove unused configApiRef
* wip
* Ongoing cleanups
* Cleanups and fix tests
* WIP cleanups
* Clean up some things
* Clean up some things
* Added missing notice header
* ts issue fixed
* Add show contition to api tab
Co-authored-by: Fredrik Adelöw <freben@gmail.com>
Co-authored-by: Emma Indal <emmai@spotify.com>
We're using cloud build in gcp to build/package our backstage deployment
and when you upload your artifacts it will remove all of the .git folder
to mimimize the upload causing the techdocs-cli to fail as it relies on
using `git rev-parse` to discover the full path. I changed this to be
statically linked so the reliance on git is no longer there and so that
as long as the structure of your repo doesn't change it should build no
matter where the root folder is placed.
This PR https://github.com/mbrn/material-table/pull/2311 broke material-table builds that use webpack. We don't see the problem locally since we have the unaffected version in our lockfiles. However when running the e2e (app generation) flows, there is no lockfile so it resolves to the affected broken versions, breaking master builds at the moment.
Pinning to the unaffected version for now.
* The backend listens to all interfaces by default
Previously, if you did not specify a host, it would only
listen to localhost, so it would not accept connections from the network.
If you use the default generated app, it is configured to listen to 0.0.0.0
which only listens to IPv4 interfaces.
This changes the default behavior, just listen to all interfaces.
* Add some comment
Many cloud providers have an environment variable PORT.
an application is supposed to listen in that port.
Currently, the yaml for listen address looks like this:
```yaml
backend:
listen: 0.0.0.0:7000
```
the problem is that I can't use the port environment variable there.
This PR changes it to this:
```yaml
backend:
listen:
host: 0.0.0.0
port: 7000
```
if I want to use the PORT environment variable, now I can do it like this:
```yaml
backend:
listen:
host: 0.0.0.0
port:
$secret:
env: PORT
```
Raghunandan