Weird application.yaml causes stupid problems

[lavalink-devs]

Weird application.yaml causes stupid problems

[melmsie]

Here's what my application.yaml looks like, I'm actually not seeing what's wrong with it?

  port: 2333
  address: 0.0.0.0
spring:
  main:
    banner-mode: log
lavalink:
  server:
    password: "password"
    sources:
      youtube: true
      bandcamp: true
      soundcloud: true
      twitch: true
      vimeo: true
      mixer: true
      http: true
      local: false
    bufferDurationMs: 400
    youtubePlaylistLoadLimit: 10
    gc-warnings: true

metrics:
  prometheus:
    enabled: false
    endpoint: /metrics

sentry:
  dsn: "url"
#  tags:
#    some_key: some_value
#    another_key: another_value

logging:
  file:
    max-history: 30
    max-size: 1GB\

  path: ./logs/

  level:
    root: INFO
    lavalink: INFO

[freyacodes]

The first line was missing, making this YAML invalid. The logging is handled by Spring Boot, but Spring Boot can't start if the configuration is malformed, thus no logging directory was set.

The error should have been apparent if you had read the output of stdin.

Edit: Did not see the screenshot. Did not know Spring Boot was capable of doing that.

[melmsie]

Alright, thanks.