Question 1

How does static-php-cli compare to Docker for deploying PHP apps?

Accepted Answer

static-php-cli creates lightweight, single-file executables that run natively without container overhead, ideal for CLI tools, while Docker offers better isolation and environment control for complex web applications.

Question 2

How to build a static PHP binary with custom extensions like GD and Redis?

Accepted Answer

Create a craft.yml file listing extensions such as 'gd,redis', then run ./spc craft. The tool automatically downloads and compiles them into a standalone binary, with logs available via --debug.

Question 3

Can I use static-php-cli for running PHP web servers in production?

Accepted Answer

Yes, it supports PHP-FPM binaries, but static compilation may introduce performance trade-offs and lack dynamic module loading, making it less suitable for high-scale web apps compared to standard setups.

Question 4

What's the performance difference between static PHP and regular PHP?

Accepted Answer

Static binaries have similar execution speed but may use more memory due to bundled extensions. The primary advantage is portability, not performance optimization.

Question 5

How do I update my static PHP binary when a new PHP version comes out?

Accepted Answer

Update the php-version in craft.yml and recompile using ./spc craft. Pre-built binaries might be available, but custom builds require manual updates, which can be slow.

Question 6

Is static-php-cli good for Windows development?

Accepted Answer

Yes, it provides pre-built spc executables for Windows, but building from source requires VS2022 and can be more complex than on Unix-like systems, as noted in the download instructions.

Static PHP CLI

What is Static PHP CLI?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions