diff --git a/docs/actor/images/github-integration.png b/docs/actor/images/github-integration.png new file mode 100755 index 0000000000..6c95b0d3d7 Binary files /dev/null and b/docs/actor/images/github-integration.png differ diff --git a/docs/actor/images/run-console.png b/docs/actor/images/run-console.png new file mode 100755 index 0000000000..5e5127e6c7 Binary files /dev/null and b/docs/actor/images/run-console.png differ diff --git a/docs/actor/images/run-log-2.png b/docs/actor/images/run-log-2.png new file mode 100755 index 0000000000..1a6db0ae86 Binary files /dev/null and b/docs/actor/images/run-log-2.png differ diff --git a/docs/actor/images/run-log.png b/docs/actor/images/run-log.png new file mode 100755 index 0000000000..690391e13f Binary files /dev/null and b/docs/actor/images/run-log.png differ diff --git a/docs/actor/images/source-env-vars.png b/docs/actor/images/source-env-vars.png new file mode 100755 index 0000000000..77887c914b Binary files /dev/null and b/docs/actor/images/source-env-vars.png differ diff --git a/docs/actor/quick_start.md b/docs/actor/quick_start.md index a08cb966a3..d0e4b2c272 100644 --- a/docs/actor/quick_start.md +++ b/docs/actor/quick_start.md @@ -15,7 +15,7 @@ Go to the [Actor](https://my.apify.com/actors) section in the app, create a new Click **Quick run** to build and run your actor. After the run is finished you should see something like: -![Apify actor run log](/img/docs/actor/run-log.png) +![Apify actor run log]({{@asset actor/images/run-log.png}}) Congratulations, you have successfully created and run your first actor! @@ -40,7 +40,7 @@ Save your actor by clicking **Save** and then rebuild it by clicking **Build**. Then set **Content type** to `application/json; charset=utf-8` and click **Run**. You will see something like: -![Apify actor run log](/img/docs/actor/run-log-2.png) +![Apify actor run log]({{@asset actor/images/run-log-2.png}}) Excellent, you have just created your first actor to accept input and store output! Now you can start adding some magic. diff --git a/docs/actor/run.md b/docs/actor/run.md index d4cce94cc7..71ca81d694 100644 --- a/docs/actor/run.md +++ b/docs/actor/run.md @@ -6,7 +6,7 @@ title: Run The actor can be invoked in a number of ways. One option is to start the actor manually in **Console** in the app: -![Apify actor run console](/img/docs/actor/run-console.png) +![Apify actor run console]({{@asset actor/images/run-console.png}}) The following table describes the run settings: diff --git a/docs/actor/source_code.md b/docs/actor/source_code.md index c202a61235..1377718cf6 100644 --- a/docs/actor/source_code.md +++ b/docs/actor/source_code.md @@ -115,7 +115,7 @@ For example, for repositories on GitHub it can be done using the following steps Then go to your GitHub repository, click **Settings**, select **Webhooks** tab and click **Add webhook**. Paste the API URL to the **Payload URL** as follows: -![GitHub integration](/img/docs/actor/github-integration.png) +![GitHub integration]({{@asset actor/images/github-integration.png}}) And that's it! Now your actor should automatically rebuild on every push to the GitHub repository. @@ -123,7 +123,7 @@ And that's it! Now your actor should automatically rebuild on every push to the The actor owner can specify custom environment variables that are set to the actor's process during the run. Sensitive environment variables such as passwords or API tokens can be protected by setting the **Secret** option. With this option enabled, the value of the environment variable is encrypted and it will not be visible in the app or APIs, and the value is redacted from actor logs to avoid the accidental leakage of sensitive data. -![Custom environment variables](/img/docs/actor/source-env-vars.png) +![Custom environment variables]({{@asset actor/images/source-env-vars.png}}) Note that the custom environment variables are fixed during the build of the actor and cannot be changed later. See the [Build]({{@link actor/build.md#build}}) section for details. diff --git a/docs/proxy/images/proxy-status.png b/docs/proxy/images/proxy-status.png new file mode 100644 index 0000000000..aa089c0d01 Binary files /dev/null and b/docs/proxy/images/proxy-status.png differ diff --git a/docs/proxy/troubleshooting.md b/docs/proxy/troubleshooting.md index 33cbf011dc..7e8d119c1b 100644 --- a/docs/proxy/troubleshooting.md +++ b/docs/proxy/troubleshooting.md @@ -10,7 +10,7 @@ To view the status of the connection to Apify Proxy, open the following URL in t If the proxy connection works well, the web page should look something like this: -![Apify proxy status page](/img/docs/proxy/proxy-status.png) +![Apify proxy status page]({{@asset proxy/images/proxy-status.png}}) To test that your requests are proxied and rotate the IP addresses correctly, you can open the following API endpoint via the proxy. It shows information about the client IP address: diff --git a/docs/scraping/cheerio_scraper.md b/docs/scraping/cheerio_scraper.md index 3f088de31e..c17d092685 100644 --- a/docs/scraping/cheerio_scraper.md +++ b/docs/scraping/cheerio_scraper.md @@ -29,13 +29,13 @@ Before we start, let's do a quick recap of the data we chose to scrape: 5. **Last run date**- When the actor was last run. 6. **Number of runs** - How many times the actor was run. -![data to scrape](../img/scraping-practice.jpg "Overview of data to be scraped.") +![data to scrape]({{@asset scraping/images/scraping-practice.jpg}} "Overview of data to be scraped.") We've already scraped number 1 and 2 in the [Getting started with Apify scrapers](https://apify.com/docs/scraping/tutorial/introduction) tutorial, so let's get to the next one on the list: Title ### [](#title)Title -![actor title](../img/title.jpg "Finding actor title in DevTools.") +![actor title]({{@asset scraping/images/title.jpg}} "Finding actor title in DevTools.") By using the element selector tool, we find out that the title is there under an `

` tag, as titles should be. Maybe surprisingly, we find that there are actually two `

` tags on the detail page. This should get us thinking. Is there any parent element that includes our `

` tag, but not the other ones? Yes, there is! There is a `
` element that we can use to select only the heading we're interested in. @@ -52,7 +52,7 @@ To get the title we just need to find it using a `header h1` selector, which sel Getting the actor's description is a little more involved, but still pretty straightforward. We can't just simply search for a `

` tag, because there's a lot of them in the page. We need to narrow our search down a little. Using the DevTools we find that the actor description is nested within the `

` element too, same as the title. Sadly, we're still left with two `

` tags. To finally select only the description, we choose the `

` tag that has a `class` that starts with `Text__Paragraph`. -![actor description selector](../img/description.jpg "Finding actor description in DevTools.") +![actor description selector]({{@asset scraping/images/description.jpg}} "Finding actor description in DevTools.") return { title: $('header h1').text(), @@ -63,7 +63,7 @@ Getting the actor's description is a little more involved, but still pretty stra The DevTools tell us that the `lastRunDate` can be found in the second of the two `