<commit_before># Default configuration
# This holds the base configuration and loads by default.
# When setting a spring profile on the commandline you can override parts of this config.
# Please note that the default config links development as it's default active profile (so this also loads when not setting a param).
spring:
  application:
    name: <%= baseName %>
  profiles:
    active: development

---

# Development config
# This configuration is set as the active profile in the default config.
# Additional profiles can be chained by using a comma in the commandline parameter.
# For example: -spring.profiles.active: developement,peer1 or -spring.profiles.active: developement,peer2
spring:
  profiles: development
  cloud:
    config:
      uri: http://192.168.252.141:8003
      username: mxt-config-server
      password: <PASSWORD>
      failFast: <%= configFail %>

---

# Production config
# This configuration can be activated by using the commandline parameter.
# For example: -spring-profiles.active: production.
# Additional profiles can be chained by using a comma in the commandline parameter.
# For example: -spring.profiles.active: production,peer1 or -spring.profiles.active: production,peer2
spring:
  profiles: production
  cloud:
    config:
      uri: http://mxt-nwsconfig01.newyse.maxxton:8003
      username: xxx
      password: <PASSWORD><commit_msg>Added acceptance profile in bootstrap.yml<commit_after># Default configuration
# This holds the base configuration and loads by default.
# When setting a spring profile on the commandline you can override parts of this config.
# Please note that the default config links development as it's default active profile (so this also loads when not setting a param).
spring:
  application:
    name: <%= baseName %>
  profiles:
    active: development

---

# Development config
# This configuration is set as the active profile in the default config.
# Additional profiles can be chained by using a comma in the commandline parameter.
# For example: -spring.profiles.active: developement,peer1 or -spring.profiles.active: developement,peer2
spring:
  profiles: development
  cloud:
    config:
      uri: http://192.168.252.141:8003
      username: mxt-config-server
      password: <PASSWORD>
      failFast: <%= configFail %>

---

# Acceptance config
# This configuration is set as the active profile in the default config.
# Additional profiles can be chained by using a comma in the commandline parameter.
# For example: -spring.profiles.active: acceptance,peer1 or -spring.profiles.active: acceptance,peer2
spring:
  profiles: acceptance
  cloud:
    config:
      uri: http://test-services02.newyse.maxxton:8003
      username: xxx
      password: <PASSWORD>
      failFast: <%= configFail %>
      
---

# Production config
# This configuration can be activated by using the commandline parameter.
# For example: -spring-profiles.active: production.
# Additional profiles can be chained by using a comma in the commandline parameter.
# For example: -spring.profiles.active: production,peer1 or -spring.profiles.active: production,peer2
spring:
  profiles: production
  cloud:
    config:
      uri: http://mxt-nwsconfig01.newyse.maxxton:8003
      username: xxx
      password: <PASSWORD>
{'fraction_non_alphanumeric': 0.08028083028083029, 'fraction_numerical': 0.018315018315018316, 'mean_word_length': 3.8191176470588237, 'pattern_counts': {'":': 0, '<': 13, '<?xml version=': 0, '>': 13, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6482090', 'n_tokens_mistral': 920, 'n_tokens_neox': 867, 'n_words': 350}