When env variable is set, any config file will be ignored and the default settings will be used

[jim-taylor-business]

When LEMMY_INITIALIZE_WITH_DEFAULT_SETTINGS env variable is set, any config file will be ignored and the default settings will be used.

This is for a special no federation standalone mode of operation for use in CI pipelines or other testing or restricted execution environments, e.g. automated end to end testing of the Leptos Lemmy UI.

[Nutomic]

This doesnt make sense because the only mandatory config field is the domain name. And if thats missing, the default would be an empty string which would break federation.

[jim-taylor-business]

totally agree

this idea is for a special mode of operation for use in end 2 end testing of the leptos UI, so there will be no federation

there is probably a better way to trigger this standalone/testing mode rather than defaulting to it when no config file is found

this is very much a draft idea, i only made this PR to see if it would break any current tests

thanks for considering it seriously though @Nutomic 😄

[dullbananas]

The default config should be enabled using a new CLI option and require the domain name to be set in another CLI option.

[jim-taylor-business]

i don't think a command line/entry-point can be specified in a woodpecker CI service but environment variables would work

[jim-taylor-business]

for more context please see:

LemmyNet/lemmy-ui-leptos#54

[jim-taylor-business]

i have implemented a potential solution using an environment variable, the build is breaking due to network errors at the moment

[jim-taylor-business]

do you think this could go into 0.19.4 @dessalines @Nutomic ? would be awesome, but i understand if there's a feature lock now

[Nutomic]

Yes it will be in 0.19.4