I remember my times using Lumen. I did not know composer scripts back then so I had to type <code>vendor/bin/phpunit</code> painstakingly when running my tests.
I used bash aliases to shorten commands. I have the alias created on my <code>Dockerfile</code> on build-time. Like so:
<pre><code class="lang-bash"># Add bash alias for PHPUnit
RUN echo 'alias phpunit="vendor/bin/phpunit"' &gt;&gt; ~/.bashrc
RUN source ~/.bashrc
</code></pre>
After building the image, there is no need to type the lengthy command anymore. Just run the new alias and my tests would run as usual!
<pre><code class="lang-bash">$ phpunit
</code></pre>
Moreover, you can make use of the same technique and create bash aliases for other lengthy commands in your Docker container.


I remember my times using Lumen. I did not know composer scripts back then so I had to type `vendor/bin/phpunit` painstakingly when running my tests.

I used bash aliases to shorten commands. I have the alias created on my `Dockerfile` on build-time. Like so:

```bash
# Add bash alias for PHPUnit
RUN echo 'alias phpunit="vendor/bin/phpunit"' >> ~/.bashrc
RUN source ~/.bashrc
```

After building the image, there is no need to type the lengthy command anymore. Just run the new alias and my tests would run as usual!

```bash
$ phpunit
```

Moreover, you can make use of the same technique and create bash aliases for other lengthy commands in your Docker container.

jgrivera.dev

jgrivera.dev

Using bash aliases to shorten lengthy commands