BTFS Web UI

Check on your node stats, explore the IPLD powered merkle forest, see peers around the world and manage your files, without needing to touch the CLI.

Test the WebUI

After making changes to the WebUI repository, the updated changes can be viewed in the browser using the following steps:

Download the repo

git clone https://github.com/TRON-US/btfs-webui

CD into the btfs-webui repo. Then with node >= 8.12 and npm >= 6.4.1 installed, run

cd btfs-webui
npm install

Open a separate terminal and start the BTFS daemon. This will allow you to see the updated WebUI in your localhost:

btfs daemon

In your previous terminal, run the dev server:

npm start

The final output should be as such:

Compiled successfully!

You can now view btfs-webui in the browser.

  Local:            http://localhost:3000/
  On Your Network:  http://10.10.0.77:3000/

Note that the development build is not optimized.
To create a production build, use npm run build.

Paste the local host URL into your web browser to view the updated WebUI.

When working on the code, run a btfs daemon, the local dev server, the unit tests, and the storybook component viewer and see the results of your changes as you save files. For debugging follow this post

In separate shells run the following:

# Run BTFS
> btfs daemon

# Run the dev server @ http://localhost:3000
> npm start

# Run the unit tests
> npm test

# Run the UI component viewer @ http://localhost:9009
> npm run storybook

Configure BTFS API CORS headers

You must configure your BTFS API at http://0.0.0.0:5001 to allow cross-origin (CORS) requests from your dev server at http://localhost:3000

Easy mode

Run the cors-config.sh script with:

> ./cors-config.sh

The manual way

> btfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["http://localhost:3000"]'
> btfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '["PUT", "GET", "POST"]'

Reverting

To reset your config back to the default configuration, run the following command.

> btfs config --json API.HTTPHeaders {}

You might also like to copy the ~/.btfs/config file somewhere with a useful name so you can use btfs config replace <file> to switch your node between default and dev mode easily.

Build

To create an optimized static build of the app, output to the build directory:

# Build out the html, css & jss to ./build
> npm run build

Test

The following command will run the app tests, watch source files and re-run the tests when changes are made:

> npm test

The WebUI uses Jest to run the isolated unit tests. Unit test files are located next to the component they test and have the same file name, but with the extension .test.js

End-to-end tests

The end-to-end tests (e2e) test the full app in a headless Chromium browser. They require an http server to be running to serve the app.

In dev, run npm start in another shell before starting the tests

# Run the end-to-end tests
> npm run test:e2e

By default the test run headless, so you won't see the the browser. To debug test errors, it can be helpful to see the robot clicking around the site. To disable headless mode and see the browser, set the environment variable DEBUG=true

# See the end-to-end tests in a browser
> DEBUG=true npm run test:e2e

Coverage

To do a single run of the tests and generate a coverage report, run the following:

> npm run test:coverage

Lint

Perform standard linting on the code:

> npm run lint

Analyze

To inspect the built bundle for bundled modules and their size, first build the app then:

# Run bundle
> npm run analyze

Translations

The translations are stored on ./public/locales and the English version is the source of truth. We use Transifex to help us translate WebUI to another languages.

Release WebUI

After all changes have been made and tested, follow the steps below to release a new version of the BTFS WebUI:

1. In the terminal, navigate to the btfs-webui directory. Then run npm run build. This builds the the WebUI files and places them in a newly created build folder.
2. SSH into the first bootstrap node(/ip4/18.237.54.123/tcp/4001/p2p/QmWJWGxKKaqZUW4xga2BCzT5FBtYDL8Cc5Q5jywd6xPt1g). Then upload the build folder by running btfs add build/, and republish the new hash value to /btns/QmWJWGxKKaqZUW4xga2BCzT5FBtYDL8Cc5Q5jywd6xPt1g by running btfs name publish /btfs/$new_hash.
3. SSH into all bootstrap nodes and run btfs name resolve /btns/QmWJWGxKKaqZUW4xga2BCzT5FBtYDL8Cc5Q5jywd6xPt1g.

License

MIT © TRON Foundation