Skip to content
No description, website, or topics provided.
JavaScript CSS HTML Dockerfile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
public Create MLsploit frontend Mar 25, 2019
src
.env
.env.development Create MLsploit frontend Mar 25, 2019
.gitignore Create MLsploit frontend Mar 25, 2019
Dockerfile Create MLsploit frontend Mar 25, 2019
LICENSE Create MLsploit frontend Mar 25, 2019
README.md Create MLsploit frontend Mar 25, 2019
docker-compose.yml Create MLsploit frontend Mar 25, 2019
package-lock.json Improve pipeline history UI Mar 25, 2019
package.json Improve pipeline history UI Mar 25, 2019

README.md

MLsploit Web Client

The web client (frontend) of the MLsploit platform. This is designed to be used with docker and docker-compose along with the rest of the MLsploit project. The documentation below is only for development and manual deployment.

Manual Deployment (without Docker)

Requires node.js and npm installed.

In this directory (which contains package.json), run npm run build and you will see the build directory containing the compiled frontend.

Development

This is a React and Redux application, using ducks pattern and redux-promise. Knowledge of these are required to understand the data flow.

All dev and build workflows follow Create React App.

The app uses blueprint.js v3 as a base UI toolkit, but also contains custom components. All custom CSS sits in index.css and follows the BEM naming convention.

Since there are rarely any components that need to be reused, nearly all components are container components (as opposed to presentational components). They all sit in the components directory.

For redux store initialization and localStorage management, see index.js.

Build-time Environment Variables

This is only relevant if you want to host the frontend and backend on different hostnames (for testing or custom build). You can set build-time env vars in .env and .env.development. See configs.js and this page for details.

You can’t perform that action at this time.