You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 26, 2019. It is now read-only.
If you're here, you would like to contribute to this repository and you're really welcome!
4
+
5
+
6
+
## Bug reports
7
+
8
+
If you find a bug or a documentation issue, please report it or even better: fix it :). If you report it,
9
+
please be as precise as possible. Here is a little list of required information:
10
+
11
+
- Precise description of the bug
12
+
- Details of your environment (for example: OS, PHP version, installed extensions)
13
+
- Backtrace which might help identifing the bug
14
+
15
+
16
+
## Feature requests
17
+
18
+
If you think a feature is missing, please report it or even better: implement it :). If you report it, describe the more
19
+
precisely what you would like to see implemented and we will discuss what is the best approach for it. If you can do
20
+
some research before submitting it and link the resources to your description, you're awesome! It will allow us to more
21
+
easily understood/implement it.
22
+
23
+
24
+
## Sending a Pull Request
25
+
26
+
If you're here, you are going to fix a bug or implement a feature and you're the best! To do it, first fork the repository, clone it and create a new branch with the following commands:
Then install the dependencies through [Composer](https://getcomposer.org/):
34
+
35
+
```bash
36
+
$ composer install
37
+
```
38
+
39
+
Write code and tests. When you are ready, run the tests. (This is usually [PHPUnit](http://phpunit.de/) or [PHPSpec](http://phpspec.net/))
40
+
41
+
```bash
42
+
$ composer test
43
+
```
44
+
45
+
When you are ready with the code, tested it and documented it, you can commit and push it with the following commands:
46
+
47
+
```bash
48
+
$ git commit -m "Feature or bug fix description"
49
+
$ git push origin feature-or-bug-fix-description
50
+
```
51
+
52
+
**Note:** Please write your commit messages in the imperative and follow the [guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) for clear and concise messages.
53
+
54
+
Then [create a pull request](https://help.github.com/articles/creating-a-pull-request/) on GitHub.
55
+
56
+
Please make sure that each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting with the following commands (here, we assume you would like to squash 3 commits in a single one):
57
+
58
+
```bash
59
+
$ git rebase -i HEAD~3
60
+
```
61
+
62
+
If your branch conflicts with the master branch, you will need to rebase and repush it with the following commands:
This repository follows the [PSR-2 standard](http://www.php-fig.org/psr/psr-2/) and so, if you want to contribute,
74
+
you must follow these rules.
75
+
76
+
77
+
## Semver
78
+
79
+
We are trying to follow [semver](http://semver.org/). When you are making BC breaking changes, please let us know why you think it is important. In this case, your patch can only be included in the next major version.
**Docker PHP** (for lack of a better name) is a [Docker](http://docker.com/) client written in PHP. This library is still a work in progress. Not much is supported yet, but the goal is to reach 100% API support.
4
+
**Docker PHP** (for lack of a better name) is a [Docker](http://docker.com/) client written in PHP.
5
+
This library aim to reach 100% API support of the Docker Engine.
5
6
6
-
The test suite currently passes against the [Docker Remote API v1.20](http://docs.docker.com/reference/api/docker_remote_api_v1.20/).
7
+
The test suite currently passes against the [Docker Remote API v1.21](http://docs.docker.com/reference/api/docker_remote_api_v1.21/).
There is no *stable* version yet and the API is rapidly evolving, but we still try to semantically version the library according to [semver](http://semver.org/), but shifted a little bit:
14
-
15
-
***MAJOR** version number stays to 0 until API freeze
16
-
***MINOR** version number is incremented when a backward incompatible change is made
17
-
***PATCH** version number is incremented when a new feature is added
18
17
19
-
So basically, if you want the `0.5` version set, use a version constraint of `~0.5.0` and you should be fine.
20
-
21
-
We are **NOT** documenting upgrade procedures until we reach a stable API, please read the code and PRs to keep up with what's going on. You can also ask us for help, we're nice people!
22
18
23
19
Installation
24
20
------------
25
21
26
22
The recommended way to install Docker PHP is of course to use [Composer](http://getcomposer.org/):
27
23
28
-
```json
29
-
{
30
-
"require": {
31
-
"stage1/docker-php": "@dev"
32
-
}
33
-
}
24
+
```bash
25
+
composer require stage1/docker-php
34
26
```
35
27
36
-
**Note**: there is no stable version of Docker PHP yet.
37
-
38
28
Usage
39
29
-----
40
30
41
31
See [the documentation](http://docker-php.readthedocs.org/en/latest/).
42
32
43
-
Using Vagrant
44
-
-------------
45
-
46
-
The provisioning included does not run the `composer install` bit, so you'll have to do it yourself:
47
-
48
-
```
49
-
$ vagrant up --provider=virtualbox
50
-
$ vagrant ssh
51
-
$ cd /vagrant; composer install --dev
52
-
```
53
-
54
33
Unit Tests
55
34
----------
56
35
@@ -63,60 +42,23 @@ $ composer install --dev
63
42
Run it using [PHPUnit](http://phpunit.de/):
64
43
65
44
```
66
-
$ bin/phpunit
45
+
$ composer test
67
46
```
68
47
48
+
69
49
Contributing
70
50
------------
71
51
72
-
Here are a few rules to follow in order to ease code reviews, and discussions before maintainers accept and merge your work.
52
+
Please see [CONTRIBUTING](CONTRIBUTING.md) for details.
73
53
74
-
* You **MUST** follow the [PSR-1](http://www.php-fig.org/psr/1/) and [PSR-2](http://www.php-fig.org/psr/2/).
75
-
* You **MUST** run the test suite.
76
-
* You **MUST** write (or update) unit tests.
77
-
* You **SHOULD** write documentation.
78
-
79
-
Please, write [commit messages that make sense](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), and [rebase your branch](http://git-scm.com/book/en/Git-Branching-Rebasing) before submitting your Pull Request.
80
-
81
-
One may ask you to [squash your commits](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) too. This is used to "clean" your Pull Request before merging it (we don't want commits such as `fix tests`, `fix 2`, `fix 3`, etc.).
82
-
83
-
Also, when creating your Pull Request on GitHub, you **MUST** write a description which gives the context and/or explains why you are creating it.
84
-
85
-
Thank you!
86
54
87
55
Credits
88
56
-------
89
57
90
58
This README heavily inspired by [willdurand/Negotiation](https://github.com/willdurand/Negotiation) by @willdurand. This guy is pretty awesome.
91
59
92
-
Projects
93
-
--------
94
-
95
-
Projects known to be using docker-php:
96
-
97
-
*[JoliCi](https://github.com/jolicode/JoliCi), Run your tests on different and isolated stacks
0 commit comments