BetterAltay.GitHub ↗
THE ENGINE UNDERNEATH

The right PHP. Ready to run.

Use the project-linked binary distribution instead of a generic PHP installation.

PREBUILT RUNTIME PACKAGES

PHP binaries

Select an asset that matches your operating system, CPU architecture and BetterAltay release. Package availability is determined by upstream.

Windows

Prebuilt Windows runtime package.

Download Windows · bin.zip ↓

Windows release details ↗

Linux / macOS

Prebuilt Linux / macOS runtime package. Extract the archive into your server folder, preserving its directories.

Download Linux / macOS · bin.zip ↓

Linux / macOS release details ↗

Check the runtime requirements of your BetterAltay release before using these packages. The release metadata does not specify their CPU architecture or PHP version.

Browse all binary releases ↗

Check the runtime you installed.

Linux and macOS: extract the matching archive into your server folder, preserving its directories. Use the actual executable path from your package; the path below is an example.

./bin/php7/bin/php -v
./bin/php7/bin/php -m

Launch on Linux or macOS

Place start.sh alongside BetterAltay.phar, then run these commands from the server folder. Use the executable in the package that matches your operating system and CPU architecture. On macOS, check whether the runtime targets Apple Silicon (ARM64) or Intel (x86-64).

chmod +x start.sh
./start.sh

If the runtime itself reports permission denied, check its executable permission. Follow the publisher’s instructions for any missing libraries. On macOS, review the publisher and package before approving a blocked executable through System Settings.

Windows

On Windows, use the bundled executable:

.\bin\php\php.exe -v
.\bin\php\php.exe -m

Missing pthreads?

Check the requirements for your server release and use its compatible threaded runtime. Installing a random extension into a different PHP version is not a reliable fix.

Wrong architecture?

“Exec format error” usually means the executable cannot run on your operating system or CPU. Recheck the archive you selected.

Still not launching?

Compare the launcher’s expected path with the extracted package. Keep the full error message when requesting support.

Troubleshooting →