<commit_before># RapidSMS configuration file.

# -- RAPIDSMS
#
# The main configuration of the RapidSMS server. It contains a list of
# apps and backends to run, which can be names of app classes, or (in the
# case of multiple apps or backends of the same type) names for apps of
# the same type (see APPS and BACKENDS sections below).
#
# apps=[app1,app2,app3,...]         * comma-separated list of apps to load
# backends=[backend1,backend2,...]  * comma-separated list of backends to load

[rapidsms]
apps=echo
backends=spomc

# -- DATABASE
#
# Database configuration info.
#
# engine={sqlite3,mysql,postgresql,oracle,postgresql_psycopg2}  * defaults to sqlite3
# name=<database-name>
# user=<database-user>                                          * defaults to root
# password=<database-password>                                  * defaults to empty string
# host=<datbase-host>                                           * defaults to localhost (empty string)
# port=<database-port>                                          * not used for sqlite3

[database]
engine=sqlite3
name=/tmp/rapidsms.sqlite3
#user=
#password=
#host=
#port=

# -- LOG
#
# Configure the built-in log module of RapidSMS.
#
# level={debug,info,warning,error,critical}     * defaults to debug
# file=<full-path-to-log-file>                  * defaults to /tmp/rapidsms.log

[log]
level=debug
file=/tmp/rapidsms.log

# -- APPS
#
# In this area you can define configurations for individual applications. The app
# must be listed under the section [rapidsms] in "apps". If no configuration is
# listed for your app it will use the default parameters. However, if you wish to
# run two apps of the same type, you MUST define configure them explicitly here.

#[alpha]
#beginning=yes
#end=no

# -- BACKENDS
#
# In this area you can define configurations for individual backends. The backend
# must be listed under the section [rapidsms] in "backends". If no configuration is
# listed for your backend it will use the default parameters. However, if you wish to
# run two backends of the same type, you MUST define configure them explicitly here.

#[spomc]
#type=spomc
#port=9000
<commit_msg>The dashboard is one of the most expensive (in terms of performance) pages to generate. Enabling caching, allows us to cache the generated page and serve it again later when the page is requested so as to save on the time in takes to regenerate the page. I see this having a number of use cases eventually.<commit_after># RapidSMS configuration file.

# -- RAPIDSMS
#
# The main configuration of the RapidSMS server. It contains a list of
# apps and backends to run, which can be names of app classes, or (in the
# case of multiple apps or backends of the same type) names for apps of
# the same type (see APPS and BACKENDS sections below).
#
# apps=[app1,app2,app3,...]         * comma-separated list of apps to load
# backends=[backend1,backend2,...]  * comma-separated list of backends to load

[rapidsms]
apps=echo
backends=spomc

# -- DATABASE
#
# Database configuration info.
#
# engine={sqlite3,mysql,postgresql,oracle,postgresql_psycopg2}  * defaults to sqlite3
# name=<database-name>
# user=<database-user>                                          * defaults to root
# password=<database-password>                                  * defaults to empty string
# host=<datbase-host>                                           * defaults to localhost (empty string)
# port=<database-port>                                          * not used for sqlite3

[database]
engine=sqlite3
name=/tmp/rapidsms.sqlite3
#user=
#password=
#host=
#port=

# -- LOG
#
# Configure the built-in log module of RapidSMS.
#
# level={debug,info,warning,error,critical}     * defaults to debug
# file=<full-path-to-log-file>                  * defaults to /tmp/rapidsms.log

[log]
level=debug
file=/tmp/rapidsms.log

# -- APPS
#
# In this area you can define configurations for individual applications. The app
# must be listed under the section [rapidsms] in "apps". If no configuration is
# listed for your app it will use the default parameters. However, if you wish to
# run two apps of the same type, you MUST define configure them explicitly here.

#[alpha]
#beginning=yes
#end=no

# -- BACKENDS
#
# In this area you can define configurations for individual backends. The backend
# must be listed under the section [rapidsms] in "backends". If no configuration is
# listed for your backend it will use the default parameters. However, if you wish to
# run two backends of the same type, you MUST define configure them explicitly here.

#[spomc]
#type=spomc
#port=9000

# -- DJANGO
#
# In this area you can define configuration options for django that would usually
# go into your settings.py file. There's no need to make the variables uppercase
# also do not specify strings by surrounding them with the quotes " or '. This
# is automatically taken care of before injecting it into django's core configuration
[django]
# Specify a cache backend. Caching becomes necessary when you have views or sections
# that are expensive to generate. Please read http://docs.djangoproject.com/en/dev/topics/cache/
# for more information on how to use the caching capabilities of django.
#
# cache_backend=dummy:///
cache_backend=file:///tmp/django_cache

{'fraction_non_alphanumeric': 0.08432595953866516, 'fraction_numerical': 0.005672149744753261, 'mean_word_length': 3.162077104642014, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 15, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 14, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3654023', 'n_tokens_mistral': 1517, 'n_tokens_neox': 1462, 'n_words': 630}