[BUG] More than one space in the configuration prevents normal operation

[svmrw]

What happened?

I commented on this here, but I'll repeat it.

In options where multiple values can be used, if you accidentally or intentionally put more than one space as a separator, the configuration is not applied or is applied incorrectly.

Because of this I thought that > in yaml doesn't work.

How to reproduce?

All these configurations will not work properly.

There is a space after example.org

bw-scheduler:
  environment:
    SERVER_NAME: >
      bunkerweb.io
      www.bunkerweb.io
      example.org 
      www.example.org

There are two spaces between example.org and www.example.org

bw-scheduler:
  environment:
    SERVER_NAME:  "bunkerweb.io www.bunkerweb.io example.org  www.example.org"

Implementations ideas

Implement replacing more than two spaces with one. Example: /\s+/ /g

BunkerWeb version

1.6.3

What integration are you using?

Docker

Linux distribution (if applicable)

No response

Removed private data

• [x] I have removed all private data from the configuration file and the logs

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[TheophileDiot]

Hi @svmrw, I edited the SERVER_NAME setting's regex and added the requested feature (in dev for now but will be available in the next feature)

[svmrw]

@TheophileDiot, Maybe this should be done for all environment options?

[TheophileDiot]

If you look at the code, it is the case