<commit_before># ===================================================================
# Artemis specific properties
# ===================================================================

artemis:
    course-archives-path: ./exports/courses         # a folder in which archived courses and exams are stored.
    repo-clone-path: ./repos                        # a folder in which git repos for the online code editor are stored. In a multi node setup, this folder should be in a shared file system area (e.g. based on NFS), so that user can access the same files over multiple nodes
    repo-download-clone-path: ./repos-download      # a temporary folder, in which git repos are downloaded that are immediately deleted afterwards (e.g. exports, plagiarism checks), should NOT be in a shared file system area
    encryption-password: <encrypt-password>         # arbitrary password for encrypting database values
    user-management:
        use-external: true
        external:
            url: https://jira.ase.in.tum.de
            user: <username>        # e.g. ga12abc
            password: <password>
            admin-group-name: tumuser
        ldap:                       # the whole section is optional: whether user details (such as the registration number) can be obtained from a LDAP service
            url: <url>
            user-dn: <user-dn>
            password: <PASSWORD>>
            base: <base>
            allowed-username-pattern: '^([a-z]{2}\d{2}[a-z]{3})'    # example for a TUM identifier, e.g. ab12cde
        internal-admin:
            username: artemis_admin
            password: <PASSWORD>
        registration:               # the whole section is optional: whether user can register in Artemis
            enabled: false
            allowed-email-pattern: '[a-zA-Z0-9_\-\.\+]+@(tum\.de|in\.tum\.de|mytum\.de)'
            allowed-email-pattern-readable: '@tum.de, @in.tum.de, @mytum.de'
            cleanup-time-minutes: 60 # The amount of time until non-activated accounts are deleted automatically
        accept-terms: false     # whether users have to accept terms before they can login, from a privacy point of view this is not needed during education, therefore the default value is false
        course-registration:                    # the whole section is optional: whether there is a restriction for the self-registration of students in courses
            allowed-username-pattern: '^([a-z]{2}\d{2}[a-z]{3})'    # example for a TUM identifier, e.g. ab12cde
        login:
            account-name: TUM                   # optional: customization for the welcome page "please sign in with your <account-name> account"
    version-control:
        url: https://bitbucket.ase.in.tum.de
        user: <username>                # e.g. ga12abc
        password: <password>
        # token: <token>                  # VCS API token giving Artemis full Admin access.
        ci-token: <token from the CI>   # Token generated by the CI (e.g. Jenkins) for webhooks from the VCS to the CI. Not needed for Bamboo+Bitbucket
        ssh-template-clone-url: ssh://git@bitbucket.ase.in.tum.de:7999/    # Url Stem for cloning via ssh, for gitlab use 'ssh://git@artemistest2gitlab.ase.in.tum.de:2222/'
        ssh-keys-url-path: /plugins/servlet/ssh/account/keys  # Url Path to access a users ssh keys, for gitlab this is '/profile/keys'
#        ssh-private-key-folder-path: <ssh-private-key-folder-path>       # the path to the folder in which the private ssh key file (e.g. id_rsa) is stored that can be used to clone git repos on the version control server
#        ssh-private-key-password: <ssh-private-key-password>        # the password for the private ssh key
        default-branch: master        # The branch that should be used as default branch for all newly created repositories. This does NOT have to be equal to the default branch of the VCS
    continuous-integration:
        user: <username>                # e.g. ga12abc
        password: <password>
        token: <token>                  # Enter a valid token generated in Bamboo giving Artemis full Admin access
        url: https://bamboo.ase.in.tum.de
        vcs-application-link-name: LS1 Bitbucket Server     # If the VCS and CI are directly linked (normally only for Bitbucket + Bamboo)
        empty-commit-necessary: true                        # Do we need an empty commit for new exercises/repositories in order for the CI to register the repo<commit_msg>Development: Fix an issue in the configuration of a default username regex pattern<commit_after># ===================================================================
# Artemis specific properties
# ===================================================================

artemis:
    course-archives-path: ./exports/courses         # a folder in which archived courses and exams are stored.
    repo-clone-path: ./repos                        # a folder in which git repos for the online code editor are stored. In a multi node setup, this folder should be in a shared file system area (e.g. based on NFS), so that user can access the same files over multiple nodes
    repo-download-clone-path: ./repos-download      # a temporary folder, in which git repos are downloaded that are immediately deleted afterwards (e.g. exports, plagiarism checks), should NOT be in a shared file system area
    encryption-password: <encrypt-password>         # arbitrary password for encrypting database values
    user-management:
        use-external: true
        external:
            url: https://jira.ase.in.tum.de
            user: <username>        # e.g. ga12abc
            password: <password>
            admin-group-name: tumuser
        ldap:                       # the whole section is optional: whether user details (such as the registration number) can be obtained from a LDAP service
            url: <url>
            user-dn: <user-dn>
            password: <password>
            base: <base>
            allowed-username-pattern: '^([a-z]{2}\d{2}[a-z]{3})$'    # example for a TUM identifier, e.g. ab12cde
        internal-admin:
            username: artemis_admin
            password: <PASSWORD>
        registration:               # the whole section is optional: whether user can register in Artemis
            enabled: false
            allowed-email-pattern: '[a-zA-Z0-9_\-\.\+]+@(tum\.de|in\.tum\.de|mytum\.de)'
            allowed-email-pattern-readable: '@tum.de, @in.tum.de, @mytum.de'
            cleanup-time-minutes: 60 # The amount of time until non-activated accounts are deleted automatically
        accept-terms: false     # whether users have to accept terms before they can login, from a privacy point of view this is not needed during education, therefore the default value is false
        course-registration:                    # the whole section is optional: whether there is a restriction for the self-registration of students in courses
            allowed-username-pattern: '^([a-z]{2}\d{2}[a-z]{3})$'    # example for a TUM identifier, e.g. ab12cde
        login:
            account-name: TUM                   # optional: customization for the welcome page "please sign in with your <account-name> account"
    version-control:
        url: https://bitbucket.ase.in.tum.de
        user: <username>                # e.g. ga12abc
        password: <password>
        # token: <token>                # VCS API token giving Artemis full Admin access.
        ci-token: <token from the CI>   # Token generated by the CI (e.g. Jenkins) for webhooks from the VCS to the CI. Not needed for Bamboo+Bitbucket
        ssh-template-clone-url: ssh://git@bitbucket.ase.in.tum.de:7999/    # Url Stem for cloning via ssh, for gitlab use 'ssh://git@artemistest2gitlab.ase.in.tum.de:2222/'
        ssh-keys-url-path: /plugins/servlet/ssh/account/keys  # Url Path to access a users ssh keys, for gitlab this is '/profile/keys'
#        ssh-private-key-folder-path: <ssh-private-key-folder-path>       # the path to the folder in which the private ssh key file (e.g. id_rsa) is stored that can be used to clone git repos on the version control server
#        ssh-private-key-password: <ssh-private-key-password>        # the password for the private ssh key
        default-branch: master          # The branch that should be used as default branch for all newly created repositories. This does NOT have to be equal to the default branch of the VCS
    continuous-integration:
        user: <username>                # e.g. ga12abc
        password: <password>
        token: <token>                  # Enter a valid token generated in Bamboo giving Artemis full Admin access
        url: https://bamboo.ase.in.tum.de
        vcs-application-link-name: LS1 Bitbucket Server     # If the VCS and CI are directly linked (normally only for Bitbucket + Bamboo)
        empty-commit-necessary: true                        # Do we need an empty commit for new exercises/repositories in order for the CI to register the repo
{'fraction_non_alphanumeric': 0.11241946234170185, 'fraction_numerical': 0.0066651855143301485, 'mean_word_length': 2.378236397748593, 'pattern_counts': {'":': 0, '<': 39, '<?xml version=': 0, '>': 40, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 4, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 7, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5101270', 'n_tokens_mistral': 2478, 'n_tokens_neox': 2290, 'n_words': 933}