Additional environment variables or mount config.yaml in docker-compose about flathunter HOT 4 CLOSED

Hey, thanks for your effort!

I just added FLATHUNTER_IS24_COOKIE as an environment variable and tested whether it works using the urls from the config.yaml, thus a combination of both config.yaml and environment variables. Everything now works as expected.

I close the issue now.

from flathunter.

From a quick glance, having the IS24-cookie or other crawler-specific settings read from an ENV variable is currently not possible without some code overhaul or refactoring.

Your configuration seems fine. Can you try changing the message format in the config.yaml to check whether the file gets read?

from flathunter.

Hey @pomeloy, I did some trial & error and the solution seems to be the following: Once you define the urls inside the config.yaml instead of the docker-compose.yaml, the script seems to look for the information in the config.yaml, and then also used the cookie from there.

As the issue technically still persists, I would leave it open for now. However, with my fix, it is solvable.

from flathunter.

I've added the option to override the IS24 cookie with an environment variable in #587 - you can now set FLATHUNTER_IS24_COOKIE. In general it should be fine to combine the config file with the environment variables. If the environment variables are present, they will override the settings in the file. And if no config file is present, everything should be read from the environment.

I've added some tests for this. If you find that the functionality isn't working as expected with the latest code on main, please let me know. If not, please close the ticket as resolved.

Thanks for the report!

from flathunter.