@@ -7,6 +7,7 @@ This project aims at building your Docker stack for [OroCommerce](https://oroinc
77
88* [ Installation] ( #installation )
99* [ Usage] ( #usage )
10+ * [ Frequently Asked Questions] ( #frequently-asked-questions )
1011* [ Supported versions and flavors] ( #supported-versions-and-flavours )
1112 * [ OroPlatform] ( #oroplatform )
1213 * [ OroCRM] ( #orocrm )
@@ -60,6 +61,10 @@ You can invoke the following command that will guess what you need and a wizard
6061
6162` kloud stack:init `
6263
64+ Once the command is finished, you will have a file named ` .env.dist ` containing the required environment variables for the stack.
65+ This file has to be renamed to ` .env ` in order to be used by Docker Compose.
66+ The command have set some ports values for all services, you may wish to change them depending on your environment.
67+
6368#### Available command line options
6469
6570* Database engine selection
@@ -107,6 +112,193 @@ If you need to test if the images you are using are following every constraint y
107112
108113` kloud image:test `
109114
115+ Frequently Asked Questions
116+ ---
117+
118+ ### I am having some warnings while launching ` docker-compose up ` for the first time
119+
120+ If you are having this sort of messages:
121+
122+ ```
123+ WARNING: The MAILCATCHER_PORT variable is not set. Defaulting to a blank string.
124+ ERROR: The Compose file './docker-compose.yml' is invalid because:
125+ services.mail.ports contains an invalid type, it should be a number, or an object
126+ ```
127+
128+ Those warnings and errors are due to missing environment variables, probably because you did
129+ not copy the ` .env.dist ` file to a ` .env ` file.
130+
131+ ### What is the use of the ` I_AM_DEVELOPER_DISABLE_INDEX_IP_CHECK ` environment variable?
132+
133+ This environment variable is used to disable the IP check in the ` public/index_dev.php ` file.
134+ To benefit from this feature, you will need to apply the following patch:
135+
136+ ``` patch
137+ Index: public/index_dev.php
138+ IDEA additional info:
139+ Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
140+ <+>UTF-8
141+ ===================================================================
142+ --- public/index_dev.php
143+ +++ public/index_dev.php
144+ @@ -13,9 +13,12 @@
145+
146+ // This check prevents access to debug front controllers that are deployed by accident to production servers.
147+ // Feel free to remove this, extend it, or make something more sophisticated.
148+ - if (isset($_SERVER['HTTP_CLIENT_IP'])
149+ - || isset($_SERVER['HTTP_X_FORWARDED_FOR'])
150+ - || !in_array(@$_SERVER['REMOTE_ADDR'], array('127.0.0.1', 'fe80::1', '::1'))
151+ + if (!isset($_ENV['I_AM_DEVELOPER_DISABLE_INDEX_IP_CHECK'])
152+ + && (
153+ + isset($_SERVER['HTTP_CLIENT_IP'])
154+ + || isset($_SERVER['HTTP_X_FORWARDED_FOR'])
155+ + || !in_array(@$_SERVER['REMOTE_ADDR'], array('127.0.0.1', 'fe80::1', '::1'))
156+ + )
157+ ) {
158+ header('HTTP/1.0 403 Forbidden');
159+ exit('You are not allowed to access this file. Check '.basename(__FILE__).' for more information.');
160+ ```
161+
162+ ### How to access My application's frontend?
163+
164+ The application frontend can be accessed through the port defined in the ` HTTP_PORT `
165+ environment variable value.
166+
167+ ### How to configure the mailer in the ` parameters.yml ` file?
168+
169+ The parameters should be set as the following:
170+
171+ ``` yaml
172+ parameters :
173+ mailer_transport : smtp
174+ mailer_host : mail
175+ mailer_port : 1025
176+ mailer_encryption : null
177+ mailer_user : null
178+ mailer_password : null
179+ ` ` `
180+
181+ Notice that the ` MAILER_PORT` variable is not used, as this port is the one from your
182+ computer's point of view, not a container's point of view in the stack.
183+
184+ # ## How to configure the websocket service in the `parameters.yml` file?
185+
186+ The parameters should be set as the following on Oro 4.1+ :
187+
188+ ` ` ` yaml
189+ parameters:
190+ websocket_bind_address: 0.0.0.0
191+ websocket_bind_port: 8080
192+ websocket_frontend_host: '*'
193+ websocket_frontend_port: '%env(WEBSOCKET_PORT)%'
194+ websocket_frontend_path: ''
195+ websocket_backend_host: '*'
196+ websocket_backend_port: '%env(WEBSOCKET_PORT)%'
197+ websocket_backend_path: ''
198+ websocket_backend_transport: tcp
199+ websocket_backend_ssl_context_options: { }
200+ ` ` `
201+
202+ Notice that the `WEBSOCKET_PORT` variable is not used for the `websocket_bind_port`, as this
203+ port is the one from your computer's point of view, not a container's point of view in the stack.
204+
205+ # ## How to configure the database service in the `parameters.yml` file?
206+
207+ The parameters should be set as the following on Oro 4.1+ :
208+
209+ ` ` ` yaml
210+ parameters:
211+ database_driver: pdo_pgsql
212+ database_host: sql
213+ database_port: null
214+ database_name: '%env(DATABASE_NAME)%'
215+ database_user: '%env(DATABASE_USER)%'
216+ database_password: '%env(DATABASE_PASS)%'
217+ database_driver_options: { }
218+ ` ` `
219+
220+ Notice that the `DATABASE_PORT` variable is not used, as this port is the one from your
221+ computer's point of view, not a container's point of view in the stack.
222+
223+ # ## How to configure the search engine service in the `parameters.yml` file?
224+
225+ The parameters should be set as the following :
226+
227+ ` ` ` yaml
228+ parameters:
229+ search_engine_name: elastic_search
230+ search_engine_host: elasticsearch
231+ search_engine_port: null
232+ search_engine_index_prefix: oro_search
233+ search_engine_username: null
234+ search_engine_password: null
235+ search_engine_ssl_verification: null
236+ search_engine_ssl_cert: null
237+ search_engine_ssl_cert_password: null
238+ search_engine_ssl_key: null
239+ search_engine_ssl_key_password: null
240+ website_search_engine_index_prefix: oro_website_search
241+ ` ` `
242+
243+ Notice that the `ELASTICSEARCH_PORT` variable is not used, as this port is the one from your
244+ computer's point of view, not a container's point of view in the stack.
245+
246+ # ## How to configure the message queue service in the `parameters.yml` file?
247+
248+ The parameters should be set as the following :
249+
250+ ` ` ` yaml
251+ parameters:
252+ message_queue_transport: amqp
253+ message_queue_transport_config:
254+ host: amqp
255+ port: '5672'
256+ user: '%env(RABBITMQ_USER)%'
257+ password: '%env(RABBITMQ_PASSWORD)%'
258+ vhost: /
259+ ` ` `
260+
261+ Notice that the `ELASTICSEARCH_PORT` variable is not used, as this port is the one from your
262+ computer's point of view, not a container's point of view in the stack.
263+
264+ # ## How to access to Mailcatcher's interface?
265+
266+ The Mailcatcher interface can be accessed through the port defined in the `MAILCATCHER_PORT`
267+ environment variable value.
268+
269+ # ## How to access RabbitMQ manager's interface?
270+
271+ The RabbitMQ manager interface can be accessed through the port defined in the `RABBITMQ_PORT`
272+ environment variable value.
273+
274+ # ## How to access Dejavu's interface for Elasticsearch?
275+
276+ The Dejavu interface can be accessed through the port defined in the `DEJAVU_PORT`
277+ environment variable value.
278+
279+ Additionnally, the `ELASTICSEARCH_PORT` variable should be defined in order to make
280+ Elasticsearch's API accessible from your computer.
281+
282+ # ## How to access Elasticsearch's API?
283+
284+ The Elasticsearch API can be accessed through the port defined in the `ELASTICSEARCH_PORT`
285+ environment variable value.
286+
287+ # ## How to access Kibana's interface?
288+
289+ The Kibana interface can be accessed through the port defined in the `KIBANA_PORT`
290+ environment variable value.
291+
292+ # ## How to access Redis service from your computer?
293+
294+ The Redis servcie can be accessed through the port defined in the `REDIS_PORT`
295+ environment variable value.
296+
297+ # ## How to access MySQL or PostgreSQL service from your computer?
298+
299+ The MySQL or PostgreSQL servcie can be accessed through the port defined in the `SQL_PORT`
300+ environment variable value.
301+
110302Supported versions and flavours
111303---
112304
0 commit comments