Question 1

How do I set up Satisfy with Docker?

Accepted Answer

Use the prebuilt Docker image by creating configuration files like parameters.yml and satis.json, then run docker-compose as per the README example, which maps ports and volumes for easy deployment.

Question 2

What's the difference between Satisfy and Satis?

Accepted Answer

Satis is the static Composer repository generator that requires manual JSON editing, while Satisfy adds a web-based management interface with a UI, security, and webhooks to simplify administration and automation.

Question 3

How can I automate package builds using webhooks in Satisfy?

Accepted Answer

Configure webhooks in your version control system (e.g., BitBucket) to point to Satisfy's /webhook/bitbucket endpoint; this triggers a build for the specific package on code pushes, avoiding full manual builds.

Question 4

Can Satisfy handle multiple users with different permissions?

Accepted Answer

No, Satisfy's security is basic with configurable users in parameters.yml, but it doesn't support role-based permissions; all authenticated users have full access to the management interface.

Question 5

What are the system requirements for running Satisfy?

Accepted Answer

Satisfy requires a PHP environment with Composer, a web server, and dependencies from composer.json; for Docker, it runs on containerized setups, but you need to manage configuration files and builds manually.

Question 6

Is Satisfy better than using Satis alone for private packages?

Accepted Answer

Satisfy is better if you need a graphical interface and features like webhooks or composer.lock imports, but if you prefer minimal setup and command-line control, plain Satis might suffice without the overhead.

Satisfy

What is Satisfy?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions