<commit_before>Graphite
========

Graphite is a popular open source graphing library for numeric time series.
Most people use it for server monitoring. This is based off [smartprocedure]'s
fix for [evarga]'s graphite Docker image.

Features of this image:

* Better support for external volumes for persitence

  [evarga]: https://registry.hub.docker.com/u/evarga/graphite/
  [smartprocedure]: https://registry.hub.docker.com/u/smartprocure/graphite


Auth
----

Default login info is root/root and can be changed in the Django admin.


Example Graphite Lifecycle
--------------------------

Based on the names and examples establied in the makefile:

* The name of the container is `graphite`
* External volumes are stored in in `$HOME/volumes/graphite`

### Get the default configuration and database

You'll need the `conf` and `storage` directory from the image. You can edit
these configuration files and reuse them between containers.

```bash<commit_msg>document how graphite is not suitable for production<commit_after>Graphite
========

Graphite is a popular open source graphing library for numeric time series.
Most people use it for server monitoring. This is based off [smartprocedure]'s
fix for [evarga]'s graphite Docker image.

Differences [smartprocedure]'s Docker image:

* Better support for external volumes for persistence
* More logs are exposed as volumes

  [evarga]: https://registry.hub.docker.com/u/evarga/graphite/
  [smartprocedure]: https://registry.hub.docker.com/u/smartprocure/graphite

This image is only for local development only. Although you can provide a lot
of your own configuration, many other configuration options, notably the Django
SECRET_KEY, are unchanged.

Auth
----

Default login info is root/root and can be changed in the Django admin.


Example Graphite Lifecycle
--------------------------

Based on the names and examples establied in the makefile:

* The name of the container is `graphite`
* External volumes are stored in in `$HOME/volumes/graphite`

### Get the default configuration and database

You'll need the `conf` and `storage` directory from the image. You can edit
these configuration files and reuse them between containers.

```bash
{'fraction_non_alphanumeric': 0.09668633681343622, 'fraction_numerical': 0.0, 'mean_word_length': 4.066666666666666, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4395609', 'n_tokens_mistral': 605, 'n_tokens_neox': 561, 'n_words': 270}