Skip to content

Commit fcba54b

Browse files
committed
Merge branch 'master' into feat/calculate-run-dynamic-memory
2 parents 4cab2e6 + ef27d2e commit fcba54b

File tree

13 files changed

+868
-1580
lines changed

13 files changed

+868
-1580
lines changed

.bun-version

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
1.3.3
1+
1.3.4

.github/workflows/check.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,7 @@ jobs:
354354
run: yarn insert-cli-metadata && yarn build-bundles
355355

356356
- name: Upload Bundles
357-
uses: actions/upload-artifact@v5
357+
uses: actions/upload-artifact@v6
358358
with:
359359
name: apify-cli-bundles-${{ matrix.label }}
360360
path: bundles/**

.github/workflows/pre_release.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ jobs:
179179
run: yarn insert-cli-metadata && yarn build-bundles
180180

181181
- name: Upload bundles
182-
uses: actions/upload-artifact@v5
182+
uses: actions/upload-artifact@v6
183183
with:
184184
name: apify-cli-bundles-${{ matrix.label }}
185185
path: bundles/**
@@ -195,7 +195,7 @@ jobs:
195195
steps:
196196
# This step also deals with unzipping the archive from GitHub, so we get a big folder with all the bundles!
197197
- name: Download bundles
198-
uses: actions/download-artifact@v6
198+
uses: actions/download-artifact@v7
199199
with:
200200
pattern: apify-cli-bundles-*
201201
merge-multiple: true

.github/workflows/release.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ jobs:
206206
run: yarn insert-cli-metadata && yarn build-bundles
207207

208208
- name: Upload bundles
209-
uses: actions/upload-artifact@v5
209+
uses: actions/upload-artifact@v6
210210
with:
211211
name: apify-cli-bundles-${{ matrix.label }}
212212
path: bundles/**
@@ -222,7 +222,7 @@ jobs:
222222
steps:
223223
# This step also deals with unzipping the archive from GitHub, so we get a big folder with all the bundles!
224224
- name: Download bundles
225-
uses: actions/download-artifact@v6
225+
uses: actions/download-artifact@v7
226226
with:
227227
pattern: apify-cli-bundles-*
228228
merge-multiple: true

.nvmrc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
24.11.1
1+
24.12.0

package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@
101101
"js-levenshtein": "^1.1.6",
102102
"lodash.clonedeep": "^4.5.0",
103103
"mime": "~4.1.0",
104-
"open": "~10.2.0",
104+
"open": "~11.0.0",
105105
"rimraf": "~6.1.0",
106106
"semver": "~7.7.0",
107107
"string-width": "^8.0.0",
@@ -148,7 +148,7 @@
148148
"vitest": "^4.0.0"
149149
},
150150
"volta": {
151-
"node": "24.11.1",
151+
"node": "24.12.0",
152152
"yarn": "4.12.0"
153153
},
154154
"packageManager": "[email protected]",

renovate.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,16 @@
2525
{
2626
"groupName": "eslint/prettier/biome",
2727
"automerge": true,
28+
"automergeType": "branch",
2829
"groupSlug": "formatting-linting-dependencies",
2930
"matchPackageNames": ["/eslint/", "/prettier/", "/biome/"]
31+
},
32+
{
33+
"groupName": "inquirer",
34+
"automerge": true,
35+
"automergeType": "branch",
36+
"groupSlug": "all-inquirer",
37+
"matchPackageNames": ["@inquirer/**"]
3038
}
3139
],
3240
"schedule": ["every weekday"]

website/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@
4141
"unist-util-visit": "^5.0.0"
4242
},
4343
"volta": {
44-
"node": "24.11.1",
44+
"node": "24.12.0",
4545
"yarn": "4.12.0"
4646
},
4747
"packageManager": "[email protected]"
Lines changed: 32 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,35 @@
11
---
2-
title: Apify CLI
2+
title: Apify CLI overview
3+
description: An introduction to Apify CLI, a command-line interface for creating, developing, building, and running Apify Actors and managing the Apify cloud platform.
4+
sidebar_label: Overview
35
---
46

5-
Apify command-line interface (Apify CLI) helps you create, develop, build and run
6-
[Apify Actors](https://apify.com/actors),
7-
and manage the Apify cloud platform from any computer.
8-
9-
Apify Actors are cloud programs that can perform arbitrary web scraping, automation or data processing job.
10-
They accept input, perform their job and generate output.
11-
While you can develop Actors in an online IDE directly in the [Apify web application](https://console.apify.com/),
12-
for complex projects it is more convenient to develop Actors locally on your computer
13-
using <a href="https://github.com/apify/apify-sdk-js">Apify SDK</a>
14-
and only push the Actors to the Apify cloud during deployment.
15-
This is where the Apify CLI comes in.
16-
17-
Note that Actors running on the Apify platform are executed in Docker containers, so with an appropriate `Dockerfile`
18-
you can build your Actors in any programming language.
19-
However, we recommend using JavaScript / Node.js, for which we provide most libraries and support.
7+
Apify command-line interface (Apify CLI) helps you create, develop, build and run [Apify Actors](https://apify.com/actors), and manage the Apify platform from any computer.
8+
9+
## What are Apify Actors?
10+
11+
Actors are cloud programs that can perform arbitrary web scraping, automation or data processing job. They accept input, perform their job and generate output.
12+
13+
## Why use Apify CLI?
14+
15+
The Apify CLI enables you to develop Actors locally on your computer using your preferred tools:
16+
17+
- Your favorite code editor
18+
- Version control system
19+
- Development tools and workflows
20+
21+
This gives you full control over your development environment and makes it easier to work on complex projects. You can leverage the [Apify SDK](https://github.com/apify/apify-sdk-js) with all its powerful features, then push your Actor to the Apify platform for deployment when ready.
22+
23+
:::note Actor development environment
24+
25+
Actors run in Docker containers on the Apify platform. With an appropriate `Dockerfile`, you can build Actors in any programming language. We recommend JavaScript/Node.js and Python, for which we have the most comprehensive libraries and support.
26+
27+
:::
28+
29+
## Learn more
30+
31+
Learn everything you need to use the Apify CLI effectively:
32+
33+
- Learn how to [install](./installation.md) the CLI on your system
34+
- See the complete [reference of all CLI commands](./reference.md) and options
35+
- Find [solutions to common issues](./troubleshooting.md)
Lines changed: 32 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,35 @@
11
---
2-
title: Apify CLI
2+
title: Apify CLI overview
3+
description: An introduction to Apify CLI, a command-line interface for creating, developing, building, and running Apify Actors and managing the Apify cloud platform.
4+
sidebar_label: Overview
35
---
46

5-
Apify command-line interface (Apify CLI) helps you create, develop, build and run
6-
[Apify Actors](https://apify.com/actors),
7-
and manage the Apify cloud platform from any computer.
8-
9-
Apify Actors are cloud programs that can perform arbitrary web scraping, automation or data processing job.
10-
They accept input, perform their job and generate output.
11-
While you can develop Actors in an online IDE directly in the [Apify web application](https://console.apify.com/),
12-
for complex projects it is more convenient to develop Actors locally on your computer
13-
using <a href="https://github.com/apify/apify-sdk-js">Apify SDK</a>
14-
and only push the Actors to the Apify cloud during deployment.
15-
This is where the Apify CLI comes in.
16-
17-
Note that Actors running on the Apify platform are executed in Docker containers, so with an appropriate `Dockerfile`
18-
you can build your Actors in any programming language.
19-
However, we recommend using JavaScript / Node.js, for which we provide most libraries and support.
7+
Apify command-line interface (Apify CLI) helps you create, develop, build and run [Apify Actors](https://apify.com/actors), and manage the Apify platform from any computer.
8+
9+
## What are Apify Actors?
10+
11+
Actors are cloud programs that can perform arbitrary web scraping, automation or data processing job. They accept input, perform their job and generate output.
12+
13+
## Why use Apify CLI?
14+
15+
The Apify CLI enables you to develop Actors locally on your computer using your preferred tools:
16+
17+
- Your favorite code editor
18+
- Version control system
19+
- Development tools and workflows
20+
21+
This gives you full control over your development environment and makes it easier to work on complex projects. You can leverage the [Apify SDK](https://github.com/apify/apify-sdk-js) with all its powerful features, then push your Actor to the Apify platform for deployment when ready.
22+
23+
:::note Actor development environment
24+
25+
Actors run in Docker containers on the Apify platform. With an appropriate `Dockerfile`, you can build Actors in any programming language. We recommend JavaScript/Node.js and Python, for which we have the most comprehensive libraries and support.
26+
27+
:::
28+
29+
## Learn more
30+
31+
Learn everything you need to use the Apify CLI effectively:
32+
33+
- Learn how to [install](./installation.md) the CLI on your system
34+
- See the complete [reference of all CLI commands](./reference.md) and options
35+
- Find [solutions to common issues](./troubleshooting.md)

0 commit comments

Comments
 (0)