Frequently Asked Questions
Yes, the Cloud is publicly available and there are currently no authentication mechanisms in place. However, you are required to let the Cloud resolve within a certain «client context». Depending on the client, the composer.json has to require certain packages, otherwise we deny the job. That way it's impossible to use the service for free unless you do so in a certain context. In other words, somebody has to pay for the resources, there's no such thing as free lunch. There is a «public» client context for testing purposes though.
You would think it cannot because how is the Cloud supposed to access your local computer, right? But it actually can if you pass on the information of those packages. Checkout the «localPackages» key when creating a new job.
No, Composer plugins can contain arbitrary code which is why they are disabled by default. Supporting them would mean possible security vulnerabilities as a plugin could e.g. read environment variables, send e-mails etc.
Cool, let's see if we find ways to get you going! The project has been running in production since May 2018 but there is no pricing concept or anything similar yet. However, it's multi-client capable so let's talk :-)
You can use the «public» client key which is open for everyone, free and ready to use. The queue is limited to one job which makes it unusable for production but it should be just enough for you to test.
Unfortunately not yet, no. We do imagine a plugin that provides a «composer cloud-update» command once installed. However, this would require that you have enough RAM on the initial «composer update» to even get this plugin installed. So probably a separate bundled «composer.phar» makes more sense? Whatever it is going to be, you are very welcome to help us out :-)