Skip to content
Start using Cerebral Cortex with Docker
CSS Python Jupyter Notebook JavaScript HTML Shell 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.
cassandra
cc_config_file
cc_demo
data
fluentd
influxdb
jupyterhub
md2k-spark-notebook
minio/configuration
mysql/initdb.d
nginx
.env.template
.gitignore
LICENSE
README.md
docker-compose.prod.yml
docker-compose.prod_logging.yml
docker-compose.yml

README.md

CerebralCortex-DockerCompose

Cerebral Cortex is the big data cloud companion of mCerebrum designed to support population-scale data analysis, visualization, model development, and intervention design for mobile sensor data.

Start using Cerebral Cortex with Docker

You can find more information about MD2K software on our software website or the MD2K organization on our MD2K website.

Install

Setup environment

Minimum requirements:

  • Any Debian Linux Distro (We have tested it on Centos, Linux Mint, KDE, and Ubuntu)

Clone and configure CerebralCortex-DataAnalysis

  • clone https://github.com/MD2Korg/CerebralCortex-DockerCompose.git
  • Execute following commands to run/setup environment:
    • cd CerebralCortex-DockerCompose
    • docker-compose create
    • docker-compose up -d
  • Once the system is up and running, you would need to manually run influxdb commands inside the contains.
    • docker-compose exec influxdb influx (command to connect to influxdb container)
    • Please copy and run influxdb init setup
  • Note: please modify docker-compose-yaml to change ports and other settings.

Contributing

Please read our Contributing Guidelines for details on the process for submitting pull requests to us.

We use the Python PEP 8 Style Guide.

Our Code of Conduct is the Contributor Covenant.

Bug reports can be submitted through JIRA.

Our discussion forum can be found here.

Versioning

We use Semantic Versioning for versioning the software which is based on the following guidelines.

MAJOR.MINOR.PATCH (example: 3.0.12)

  1. MAJOR version when incompatible API changes are made,
  2. MINOR version when functionality is added in a backwards-compatible manner, and
  3. PATCH version when backwards-compatible bug fixes are introduced.

For the versions available, see this repository's tags.

Contributors

Link to the list of contributors who participated in this project.

License

This project is licensed under the BSD 2-Clause - see the license file for details.

Acknowledgments

You can’t perform that action at this time.