Skip to content
A simple API to dispense Divi for the testnet.
TypeScript CSS HTML Dockerfile
Branch: master
Clone or download
Latest commit 70178a0 Dec 4, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
api Initial version of faucet Dec 5, 2019
public Initial version of faucet Dec 5, 2019
src Docker container Dec 5, 2019
.gitignore Initial version of faucet Dec 5, 2019
.gitkeep Base scaffolding Dec 2, 2019
Dockerfile Docker container Dec 5, 2019
README.md Initial version of faucet Dec 5, 2019
package.json Initial version of faucet Dec 5, 2019
tsconfig.json Base scaffolding Dec 2, 2019
yarn.lock Initial version of faucet Dec 5, 2019

README.md

Testnet Faucet

A simple web application that is used to distribute Divi to testnet wallets on the network.

Running in Dev mode

  1. run yarn server.

  2. In a separate tab run yarn start.

Please make sure environment variables are properly configured for the API.

Running the REST Server

yarn server

Runs the REST API server on process.env.port or http://localhost:3001.

yarn server-test

Runs the REST API unit tests.

yarn build-server

Builds the dist for the REST API.

Running the Web App

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

yarn eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

You can’t perform that action at this time.