4237dda205
* feat: synchronize ui folder with ui repository * docs: updated README in /ui to reflect new UI asset build process * chore: update CHANGELOG * chore: re-worded CHANGELOG message and added trailing newline to fetch_ui_assets.sh script * fix: leveraged queryBuilder test code from ui repo to fix flaky queryBuilder test on chrome * docs: added comments to fetch_ui_assets script explaining where the assets come from * chore: empty commit to trigger CI |
||
---|---|---|
.. | ||
__mocks__/@influxdata | ||
assets | ||
cypress | ||
mocks | ||
scripts | ||
src | ||
.browserslistrc | ||
.dockerignore | ||
.eslintignore | ||
.eslintrc.js | ||
.npmrc | ||
.prettierrc.json | ||
Makefile | ||
README.md | ||
cypress.json | ||
fetch_ui_assets.sh | ||
global.d.ts | ||
index.d.ts | ||
jest.config.js | ||
jestSetup.ts | ||
package.json | ||
testSetup.ts | ||
tsconfig.json | ||
tsconfig.test.json | ||
webpack.common.ts | ||
webpack.dev.ts | ||
webpack.prod.ts | ||
webpack.tsconfig.json | ||
webpack.vendor.ts | ||
yarn.lock |
README.md
InfluxDB UI
UI assets for InfluxDB are automatically downloaded and embedded in the influxd
binary
when using the top-level Makefile
. The UI assets are built and made available from
the influxdata/ui
repository. Currently, this ui
folder and its contents are being kept to preserve the ability to run end-to-end tests via Cypress in this repository against the built UI when changes are made to influxdb
.
Starting a Local Development Environment
It is possible to run a frontend development server with hot reloading using the UI from
influxdata/ui
in front of the InfluxDB backend:
Start influxd
listening on the default port (8086
):
$ ./bin/darwin/influxd
Clone (if needed) & start the UI development server from the ui
repository:
$ git clone https://github.com/influxdata/ui.git
$ cd ui
$ yarn start
The UI development server runs at http://localhost:8080
Running InfluxDB with Local UI Assets
To run InfluxDB with local UI assets, first build the assets:
$ git clone https://github.com/influxdata/ui.git
$ cd ui
$ yarn build
Start influxd
using the local UI assets via the --assets-path
flag. For example,
if the ui
folder containing built assets is at the same level as the influxdb
folder
and the influxd
binary is at influxdb/bin/darwin/influxd
:
$ ./bin/darwin/influxd --assets-path=../ui/build
Cypress Testing
For the end to end tests to run properly, the server needs to be running in the e2e testing mode with the in-memory data store. From the influxdb
directory:
$ ./bin/darwin/influxd --e2e-testing --store=memory
From the ui directory, install the packages necessary for testing:
$ yarn install
To run Cypress locally:
$ yarn cy