[DiscordArchive] does it look like .dist with only a few things changed?
[DiscordArchive] does it look like .dist with only a few things changed?
Original source
I wish the whole thing was one language throughout
rektbyfaith
01-23-2023, 09:45 PM #31Archived author: mynameismeat • Posted: 2023-01-23T21:45:04.790000+00:00
Original source
I wish the whole thing was one language throughout
Original source
but it gets the job done for probably a good number of people, and thats what matters most
rektbyfaith
01-23-2023, 09:45 PM #32Archived author: mynameismeat • Posted: 2023-01-23T21:45:20.378000+00:00
Original source
but it gets the job done for probably a good number of people, and thats what matters most
Original source
of course I say that and then do shit like this
https://github.com/michaeldelago/azeroth...unt-create
rektbyfaith
01-23-2023, 09:46 PM #33Archived author: mynameismeat • Posted: 2023-01-23T21:46:57.505000+00:00
Original source
of course I say that and then do shit like this
https://github.com/michaeldelago/azeroth...unt-create
Original source
So let's say we remove the "error" messages when a config option doesn't exist, and just rely on the core handling those "unconfigured" variables like normal.
We then have very minimal .conf files, with bare minimum requirements for the core to start, ie connection info, logger info, and a few database vars for importing.
We move the config variables to the wiki, so end users can check the wiki for available config variables to add to their minimal .conf file.
I like this approach personally, it gets rid of the .dist file in its entirety, we stick to a single config file, and we minimize it. It will have no impact on existing users, as the old conf files will just define defaults.
rektbyfaith
01-23-2023, 09:50 PM #34Archived author: Foe • Posted: 2023-01-23T21:50:10.709000+00:00
Original source
So let's say we remove the "error" messages when a config option doesn't exist, and just rely on the core handling those "unconfigured" variables like normal.
We then have very minimal .conf files, with bare minimum requirements for the core to start, ie connection info, logger info, and a few database vars for importing.
We move the config variables to the wiki, so end users can check the wiki for available config variables to add to their minimal .conf file.
I like this approach personally, it gets rid of the .dist file in its entirety, we stick to a single config file, and we minimize it. It will have no impact on existing users, as the old conf files will just define defaults.
Original source
I can definitely see it generate a lot of "Is it possible to do x?" support questions though from people not reading the documentation
rektbyfaith
01-23-2023, 09:52 PM #35Archived author: Foe • Posted: 2023-01-23T21:52:44.903000+00:00
Original source
I can definitely see it generate a lot of "Is it possible to do x?" support questions though from people not reading the documentation
Original source
one thing I'm thinking of: if there's no .conf file already, just add in the file containing all the defaults. that way, the user can get the server up and running a bit faster, and they'll still be able to go through the "whole milk" version of the config to browse all the defaults
if they already have a conf file with their non-default settings in it, nothing will happen and their setup will continue to function
rektbyfaith
01-23-2023, 09:53 PM #36Archived author: mynameismeat • Posted: 2023-01-23T21:53:52.825000+00:00
Original source
one thing I'm thinking of: if there's no .conf file already, just add in the file containing all the defaults. that way, the user can get the server up and running a bit faster, and they'll still be able to go through the "whole milk" version of the config to browse all the defaults
if they already have a conf file with their non-default settings in it, nothing will happen and their setup will continue to function
Original source
That's the way it works currently with copying everything from .dist
rektbyfaith
01-23-2023, 09:54 PM #37Archived author: Foe • Posted: 2023-01-23T21:54:27.760000+00:00
Original source
That's the way it works currently with copying everything from .dist
Original source
Could add a config option to disable config errors
rektbyfaith
01-23-2023, 09:57 PM #38Archived author: Foe • Posted: 2023-01-23T21:57:56.956000+00:00
Original source
Could add a config option to disable config errors
Original source
I was gonna say it'd make sense to hide them with a loglevel (does acore have loglevels?)
rektbyfaith
01-23-2023, 09:58 PM #39Archived author: mynameismeat • Posted: 2023-01-23T21:58:24.839000+00:00
Original source
I was gonna say it'd make sense to hide them with a loglevel (does acore have loglevels?)
Original source
yep
rektbyfaith
01-23-2023, 09:58 PM #40Archived author: Foe • Posted: 2023-01-23T21:58:31.176000+00:00
Original source
yep
1 Guest(s)
1 Guest(s)