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

Dockerfile and script for running crawl jobs in Google Cloud Run with captcha support #208

Merged
merged 6 commits into from
Aug 30, 2022

Conversation

codders
Copy link

@codders codders commented Aug 28, 2022

This PR adds support for Google-Cloud-Run, and adds a docker image that can be launched to trigger a one-time crawl (which can then be setup to run on a schedule).
I have refactored the config handling so that it's possible to pass the relevant config by environment variables.
This needs a bunch of documentation still - opening the PR for discussion

@codders codders requested a review from alexanderroidl August 29, 2022 08:54
@codders codders changed the title [WIP] Dockerfile and script for running crawl jobs in Google Cloud Run with captcha support Dockerfile and script for running crawl jobs in Google Cloud Run with captcha support Aug 29, 2022
Add additional python script for gcloud run
Updated dependencies
@codders codders force-pushed the feat/google-cloud-run branch from 93f0907 to 966ce83 Compare August 29, 2022 11:35
@@ -161,15 +161,35 @@ First build the image inside the project's root directory:
$ docker build -t flathunter .
```

**When running a container using the image, a config file needs to be mounted on the container at ```/config.yaml```.** The example below provides the file ```config.yaml``` off the current working directory:
**When running a container using the image, a config file needs to be mounted on the container at ```/config.yaml``` or configuration has to be supplied using environment variables.** The example below provides the file ```config.yaml``` off the current working directory:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should think about separating the README into separate .md-files and only use the main file as index, because it is so large already

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. That would make sense. If you have a proposal for how you would like to see that split, I would welcome that. At least the basic getting-started instructions should maybe be at the top of the main README, and people who want to know more can dig a little.

alexanderroidl
alexanderroidl previously approved these changes Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants