Skip to main content
use-apify.com

Linux: guides & tutorials

Linux for scraping ops: systemd/cron, SSH basics, headless Chrome flags. Run Apify CLI and crawlers on servers for steadier performance and simpler ops.

2 articles

View all tags

Linux is where most scrapers run in production, from systemd and cron scheduling to SSH basics and headless Chrome flags. These guides cover operating crawlers and the Apify CLI on Linux servers.

Comfort with the shell, services, and process management makes scraping ops far smoother and steadier. Below you will find practical Linux guidance for running scrapers and automation.

Related topics

DevOps7 min read

VPS Security Hardening Checklist: Protect Your Server in 30 Minutes (2026)

· 7 min read
Yassine El Haddad
Yassine El Haddad
Software Developer & Automation Specialist

Default VPS configurations are insecure. Bots scan the internet for open ports and weak SSH configs within minutes of provisioning — brute-force attempts and exploit probes start almost immediately. A Liquid Web VPS gives you a solid foundation, but you still need to harden the OS. This guide walks through six essential steps to protect your server in about 30 minutes, whether you run self-hosted scrapers, APIs, or web apps.

Frequently asked questions

Frequently Asked Questions

Most production scrapers run on Linux servers—Docker containers use Ubuntu or Alpine base images, VPS hosts default to Debian or CentOS. Linux provides the process management, cron scheduling, networking tools, and shell scripting that scraping pipelines rely on. Apify actors run in Linux containers, so Linux knowledge is foundational.

curl and wget for HTTP debugging, jq for JSON processing in shell scripts, cron for scheduling, tmux for persistent sessions, netstat/ss for network diagnostics, and Docker for containerization. htop shows resource usage per process, useful for diagnosing concurrency issues. nmap and tcpdump help debug proxy connectivity problems.

Cron handles simple schedules with crontab entries; systemd timers provide better logging and dependency management for production. For more complex orchestration with retry and monitoring, use Airflow or Prefect. Apify Cloud manages scheduling without needing Linux server administration skills.

Disable root SSH login, use key-based authentication, install fail2ban for brute-force protection, apply automatic security updates, use a non-root user for all scraper processes, and firewall inbound ports to only necessary services. Rotate credentials stored on the server on a schedule and use a secrets manager for API keys.