Repository for H0ck Framework Frontend, a interface that uses H0ck Core API to create, manage and show the result of Jobs.
In the project directory, you can run:
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.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
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.
Build the app for production environment to a folder called 'infrastructure' outside the root path. This is intended for building the project before deploying to AWS S3.
This command also takes in consideration the environment variables. This is used in the deployment to populate the H0ck Core API in the infrastructure.json file.
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.
The frontend currently has 2 implemented views. All the views uses the header component where the menu of the frontend is showed.
This view uses the component Jobs.jsx. In this component, there is a state where the job data is stored on every change. When the sumbit button is clicked, all the data of the state is sent with a POST request to the H0ck Core API.
This view uses the component Dashboard.jsx. In this component, the state stores all the current jobs that the H0ck Core API has. For each of the Jobs, an instance of the JobDisplay.jsx component is created. This is the component that shows the data, the params and each one of the resultProcessors for every job.