<commit_before>###########################################################################
#                          WEBADMIN PLUGIN                                #
###########################################################################

This plugin is optional. It is used to update the ENSEMBL_WEBSITE database,
which contains help, news and other non-genomic content. We recommend that
you run this plugin on a development server then copy the database to your
production server, rather than running it on your live site! 

In order to use this plugin, you need the following options set up:

1) You must be using the user login system - it protects your database from 
unauthorised access, and the database interface logs user IDs in order to
track updates.

2) You need to set up a user group for staff who will be permitted to
access the interface. You can call this group anything you like, but it
should be kept separate from other groups.

3) Once your group is set up, look up its group id in the
ensembl_web_user_db database

4) Configure the group ID as the value of ENSEMBL_WEBADMIN_ID in
SiteDefs.pm, in whichever plugin contains all your server settings

The plugin also includes an interface for the ENSEMBL_HEALTHCHECK database
used by our genebuilders. This is an optional part of the plugin and 
can be ignored if you are not running our healthchecks. Simply comment
out the ENSEMBL_HEALTHCHECK database settings in DEFAULTS.ini
<commit_msg>db name changed<commit_after>###########################################################################
#                          WEBADMIN PLUGIN                                #
###########################################################################

This plugin is optional. It is used to update the ENSEMBL_WEBSITE database,
which contains help, news and other non-genomic content. We recommend that
you run this plugin on a development server then copy the database to your
production server, rather than running it on your live site! 

In order to use this plugin, you need the following options set up:

1) You must be using the user login system - it protects your database from 
unauthorised access, and the database interface logs user IDs in order to
track updates.

2) You need to set up a user group for staff who will be permitted to
access the interface. You can call this group anything you like, but it
should be kept separate from other groups.

3) Once your group is set up, look up its group id in the
ensembl_accounts database

4) Configure the group ID as the value of ENSEMBL_WEBADMIN_ID in
SiteDefs.pm, in whichever plugin contains all your server settings

The plugin also includes an interface for the ENSEMBL_HEALTHCHECK database
used by our genebuilders. This is an optional part of the plugin and 
can be ignored if you are not running our healthchecks. Simply comment
out the ENSEMBL_HEALTHCHECK database settings in DEFAULTS.ini

{'fraction_non_alphanumeric': 0.12282497441146366, 'fraction_numerical': 0.002729443875810304, 'mean_word_length': 4.099130434782609, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, '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': '6152149', 'n_tokens_mistral': 704, 'n_tokens_neox': 669, 'n_words': 412}