Old piximi monorepo -> see piximi/piximi
A web-based deep learning tool for classification of human cells, created with Tensorflow.js and React. https://www.piximi.app
Please make sure to clean your browser cache, since we are continuously developing new features:)
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
- Install npm and Node.js: https://www.npmjs.com/get-npm
- Verify the installation by:
node --version
andnpm -v
- Install the node dependencies with
npm install
- Clone the project:
git clone https://github.com/piximi/application.git
and move into the repo withcd application
- Run
npm start
from within the root directory of the repo, which should pop up a new tab your browser pointing at http://localhost:3000
- Clone the project:
git clone https://github.com/piximi/application.git
and move into the repo withcd application
- Make sure you have docker-compose installed:
docker-compose version
- From within the root directory, run
docker-compose up
. (Note you might want to rundocker-compose up --build
whenever you make changes to theDockerfile.dev
.) - You should be able to see the application page at http://localhost:3000. You won't need to restart the server as long as the docker-compose is running, the app will be dynamically relaoded.
There is no master branch in this repo, and develop
is the default branch that you should branch off when you want to make changes. Although in some rare cases the maintainers of the repo could merge hot-fix PRs directly to production
branch,
in general developers follow the process:
- Branch off the latest remote
develop
branch either in a forked repo or the same repo (requries write access to the repo). - Make changes, commit the changes and create a PR against the
develop
branch. - Make sure all of the tests pass.
- Ask the maintainers of the repo to merge the PR for you, usually they will be the reviewers of your PR.
- PRs merged to
develop
will trigger a deployment to the dev server.
Maintainers can merge the develop
to production
to trigger a deployment/promotion to the prod server. External contributors will need to follow the CONTRIBUTING guide.
You can deploy by running: npm deploy
You can define where to deploy in the package.json file under: ** homepage **
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
We use SemVer for versioning.
This project is licensed under the BSD 3-Clause License - see the LICENSE.md file for details
- Hat tip to anyone whose code was used
- Inspiration
- etc