Skip to content

Commit c88980f

Browse files
authored
Merge pull request #75 from philtrep/update-readme-why-nodock
Added why nodock section to readme
2 parents b62a802 + c7e16c4 commit c88980f

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

README.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,14 @@
11
# NoDock
2-
Docker Compose for Node projects with Node, MySQL, MongoDB, NGINX, Memcached,Certbot and RabbitMQ images
2+
Docker Compose for Node projects with Node, MySQL, MongoDB, NGINX, Memcached, Certbot and RabbitMQ images
3+
4+
<a name="why-nodock"></a>
5+
## Why NoDock?
6+
7+
The [docker Node.js](https://github.com/nodejs/docker-node) image is very simple, you give it an entrypoint and it runs it. This is fine for very simple/small scripts but for larger projects you'll probably want something a bit more robust.
8+
9+
The goal of NoDock is to provide a complete environment for your node project: Node.js service(s), databases, web servers, queues, etc. while doing the "wiring" for you.
10+
11+
You can use NoDock for simple projects by using one of the [examples](#Examples) or you can build upon them.
312

413
## Contents
514

0 commit comments

Comments
 (0)