Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Auto create default configuration. #168

Open
nathan130200 opened this issue Feb 3, 2019 · 2 comments · Fixed by #781
Open

Feature request: Auto create default configuration. #168

nathan130200 opened this issue Feb 3, 2019 · 2 comments · Fixed by #781

Comments

@nathan130200
Copy link

nathan130200 commented Feb 3, 2019

Auto create default configuration file if does not exists in lavalink directory, instead of download manually configuration and put into directory.

@topi314 topi314 linked a pull request Nov 22, 2022 that will close this issue
@topi314 topi314 added this to the v3.7.0 milestone Nov 28, 2022
@topi314
Copy link
Member

topi314 commented Jan 14, 2023

implemented in https://github.com/freyacodes/Lavalink/releases/tag/3.7.0

@topi314 topi314 closed this as completed Jan 14, 2023
@topi314
Copy link
Member

topi314 commented Jan 17, 2023

This has been reverted in https://github.com/freyacodes/Lavalink/releases/tag/3.7.1, due to issues with differently named configs.
Spring allows for the config values to be read from an application.properties, application.yaml and some more which we did not account for here.
We will revisit this later

@topi314 topi314 reopened this Jan 17, 2023
@topi314 topi314 removed this from the v3.7.0 milestone Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants