Skip to content

Commit 305324e

Browse files
committed
Touch up phalcon README
1 parent 138816b commit 305324e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

phalcon/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
This is a Phalcon application server image based on Apache (with SSL support) and PHP5. In order to use this image effectively, you'll need to mount:
44

5-
- /var/www/phalcon/ for your app code (e.g. using "-v /home/jdoe/myapp/:/var/www/phalcon/app/")
5+
- /var/www/phalcon/ for your app code (e.g. using "-v /home/jdoe/myapp/:/var/www/phalcon/"), with your document root in a directory named public/
66
- /var/log/apache2, optionally, if you want to store logfiles visibly outside the container
77
- /etc/ssl, optionally, if you wish to use SSL with real keys
88

@@ -12,7 +12,7 @@ As per the defaults, Apache will use the bundled "snakeoil" key when serving SSL
1212

1313
## Simple Examples ##
1414

15-
Assuming you have your app code at /home/jdoe/myapp/, with a public/ directory withinit suitable to act as the document root, then the below will be sufficient to serve it. Note that many Docker users encourage mounting data from a storage container, rather than directly from the filesyetem.
15+
Assuming you have your app code at /home/jdoe/myapp/, with a public/ directory within it suitable to act as the document root, then the below will be sufficient to serve it. Note that many Docker users encourage mounting data from a storage container, rather than directly from the filesyetem.
1616

1717
- "It works!": `docker run -p 80:80 -p 443:443 -d eboraas/phalcon` and browse to the host's IP address using http or https
1818
- Serving your own app, with SSL support: `docker run -p 80:80 -p 443:443 -v /home/jdoe/myapp/:/var/www/phalcon/ -d eboraas/phalcon`

0 commit comments

Comments
 (0)