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
[](http://isitmaintained.com/project/mblaschke/typo3-docker-boilerplate"Average time to resolve an issue")
6
6
[](http://isitmaintained.com/project/mblaschke/typo3-docker-boilerplate"Percentage of issues still open")
7
7
8
-
9
-
This is a boilerplate utilizing Docker based with support
10
-
for **TYPO3_CONTEXT** and **FLOW_CONTEXT** for TYPO3, FLOW, NEOS.
11
-
It also supports Symfony and any other PHP base project.
8
+
This is an easy customizable docker boilerplate for any PHP based projects like _TYPO3 CMS_, _TYPO3 NEOS_, _TYPO3 FLOW_, _Symfony Framework_ and many other.
12
9
13
10
Supports:
14
11
15
12
- Nginx or Apache HTTPd
16
-
- PHP-FPM (with Xdebug and Xhprof)
13
+
- PHP-FPM (with Xdebug)
17
14
- MySQL, MariaDB or PerconaDB
18
-
- Solr (disabled, without EXT:solr configuration)
15
+
- Solr (disabled, with TYPO3 CMS EXT:solr configuration as example)
19
16
- Elasticsearch (disabled, without configuration)
20
17
- Redis (disabled)
21
18
- Memcached (disabled)
19
+
- Mailcatcher (if no mail sandbox is used, eg. [Vagrant Development VM](https://github.com/mblaschke/vagrant-development))
20
+
- Support for `TYPO3_CONTEXT` and `FLOW_CONTEXT` for TYPO3, FLOW, NEOS.
22
21
- maybe more later...
23
22
24
23
This Docker boilerplate based on the best practises and don't use too much magic.
@@ -27,9 +26,9 @@ Configuration of each docker container is available in the `docker/` directory -
27
26
This boilerplate can also be used for any other web project eg. Symfony, Magento and more.
28
27
Just customize the makefile for your needs
29
28
30
-
Warning: Don't use this Docker containers for production - they are only for development!
29
+
Warning: Don't use this Docker containers for production - they are only for development. If you find it usefull for production please contact me.
31
30
32
-
Use can use my [Vagrant Development VM](https://github.com/mblaschke/vagrant-development) for this Docker boilerplate.
31
+
Use can use my [Vagrant Development VM](https://github.com/mblaschke/vagrant-development) for this Docker boilerplate, eg. for easy creating new boilerplate installations with an easy shell command: `ct docker:create directory`
33
32
34
33
## Requirements
35
34
@@ -41,7 +40,7 @@ Use can use my [Vagrant Development VM](https://github.com/mblaschke/vagrant-dev
41
40
If you want to run a Docker VM make sure you're using VMware or Parallels Desktop because of
42
41
the much faster virtualisation (networking, disk access, shared folders) compared to VirtualBox.
43
42
44
-
For more convenience use [CliTools.phar](https://github.com/mblaschke/vagrant-clitools) (will also run on native Linux, not only Vagrant)
43
+
For more convenience use [CliTools.phar](https://github.com/mblaschke/vagrant-clitools) (will also run on native Linux, not only inside a Vagrant box)
45
44
46
45
## Docker short introduction
47
46
@@ -114,7 +113,7 @@ main | Main container with PHP-FPM and tools (your entrypoi
114
113
storage | Storage container, eg. for Solr data
115
114
web | Apache HTTPD or Nginx webserver
116
115
mysql | MySQL database
117
-
solr | Apache Solr server
116
+
solr (optional) | Apache Solr server
118
117
elasticsearch (optional) | Elasticsearch server
119
118
memcached (optional) | Memcached server
120
119
redis (optional) | Redis server
@@ -198,13 +197,22 @@ Setting | Value
198
197
Host | memcached
199
198
Port | 11211
200
199
200
+
### Mailcatcher
201
+
202
+
Setting | Value
203
+
------------- | -------------
204
+
Host | mail
205
+
SMTP port | 1025
206
+
Web port | 1080
207
+
201
208
### Environment settings
202
209
203
210
Environment | Description
204
211
--------------------- | -------------
205
212
DOCUMENT_ROOT | Document root for Nginx and Apache HTTPD, can be absolute or relative (to /docker inside the container).
206
213
DOCUMENT_INDEX | Default document index file for Nginx and Apache HTTPd
207
214
CLI_SCRIPT | Target for "cli" command of main container
215
+
CLI_USER | User which should be used to run CLI scripts (normally www-data, equals php-fpm user)
208
216
<br> |
209
217
TYPO3_CONTEXT | Context for TYPO3, can be used for TypoScript conditions and AdditionalConfiguration
210
218
FLOW_CONTEXT | Context for FLOW and NEOS
@@ -253,7 +261,7 @@ Use this boilerplate as template and customize it for each project. Put this Doc
253
261
configuration for each project into seperate git repositories.
254
262
255
263
Now set your existing project repository to be a git submodule in `code/`.
256
-
Every developer now needs only to clone the Docker repository with **--recursive**
264
+
Every developer now needs only to clone the Docker repository with `--recursive` option
257
265
to get both, the Docker configuration and the TYPO3 installation.
258
266
259
267
For better useability track a whole branch (eg. develop or master) as submodule and not just a single commit.
@@ -263,3 +271,4 @@ For better useability track a whole branch (eg. develop or master) as submodule
263
271
This Docker layout is based on https://github.com/denderello/symfony-docker-example/
264
272
265
273
Thanks to [cron IT GmbH](http://www.cron.eu/) for the inspiration for this Docker boilerplate.
274
+
Also thanks to Ingo Pfennigstorf for testing and some usefull ideas.
0 commit comments