Merged
Conversation
Apify Actor that brings Wick's browser-grade content extraction to Apify's 22K+ marketplace. Two modes: bundled Wick engine (runs on Apify infra with Chrome TLS fingerprint) or tunnel to local Wick Pro instance (residential IP + full anti-detection). Supports fetch, crawl, and map operations with clean JSON output via Wick's HTTP API server running as a sidecar process. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying wickproject with
|
| Latest commit: |
a8add93
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://da9a4cba.wickproject.pages.dev |
| Branch Preview URL: | https://apify-actor.wickproject.pages.dev |
There was a problem hiding this comment.
Pull request overview
Adds an Apify marketplace Actor wrapper around Wick, packaging a container that can either run a bundled wick serve --api sidecar locally in Apify infrastructure or proxy requests to a user-provided Wick tunnel endpoint.
Changes:
- Implemented the Actor runtime logic (fetch/crawl/map) and dataset output in
apify/src/main.js. - Added a Dockerfile that downloads and installs the Wick Linux binary + dependencies and runs the Actor.
- Added Apify marketplace metadata: Actor definition, README listing, and input/dataset schemas.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| apify/src/main.js | Actor entrypoint: starts Wick locally (or uses tunnel), calls Wick HTTP API, writes results to Apify dataset |
| apify/package.json | Minimal Node package definition for the Actor (Apify SDK dependency, ESM mode) |
| apify/Dockerfile | Container build steps: install Wick from GitHub release, install npm deps, run Actor |
| apify/.actor/input_schema.json | Actor input schema for URLs, mode, output format, crawl limits, and tunnel/API key options |
| apify/.actor/dataset_schema.json | Dataset schema describing output records for fetch/crawl/map results |
| apify/.actor/ACTOR.md | Marketplace listing / documentation for the Actor and its modes |
| apify/.actor/actor.json | Apify Actor metadata wiring Dockerfile, README, input schema, and dataset schema |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Position Wick as complementary to the Apify ecosystem rather than competitive. Removed the comparison table vs Website Content Crawler, added honest limitations section, and framed the Actor as a lightweight option that pairs well with browser-based Actors. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Null-safe Actor.getInput() with validation for urls array - Error/exit handlers on spawned wick process - Drain stdout/stderr pipes to prevent buffer blocking - Dockerfile uses curl + sha256 checksum instead of ADD - Map limit is now configurable via mapLimit input (default 100, max 5000) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Architecture
The Actor starts
wick serve --apiinside the container and calls it over localhost. If a tunnel URL is provided, it calls the remote Wick instance instead. Same code path either way.Files
apify/.actor/— Apify metadata, input schema, dataset schema, marketplace READMEapify/src/main.js— Actor logic (~120 lines)apify/Dockerfile— Downloads Linux binary from GitHub releaseapify/package.json— Just theapifySDK dependencyTest plan
docker buildthe Dockerfile locally to verify Wick binary works in the containerwick serve --apiinstanceapify pushto deploy to Apify platform🤖 Generated with Claude Code