Skip to content

Commit e0d500e

Browse files
committed
update license and README
1 parent 6da0434 commit e0d500e

File tree

2 files changed

+18
-33
lines changed

2 files changed

+18
-33
lines changed

LICENSE

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
The MIT License (MIT)
22

3-
Copyright (c) 2014-2017 Pascal Cremer
3+
Copyright (c) 2014-2023 Geek Cell
44

55
Permission is hereby granted, free of charge, to any person obtaining a copy
66
of this software and associated documentation files (the "Software"), to deal

README.md

Lines changed: 17 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -6,35 +6,40 @@ https://medium.com/@b00giZm/building-the-next-version-of-compose-node-86eef3c23d
66

77
## Motivation
88

9-
[Docker Compose](http://docs.docker.com/compose/) is an awesome tool for creating isolated development environments with [Docker](http://docker.com) by using simple configurations with [YAML](http://www.yaml.org/). It's clean and easy enough to wrap your head around, even if you are new to Docker. Even though, the official website is lacking some practial, real world examples for getting started with Docker Compose and Nodejs.
9+
[Docker Compose](http://docs.docker.com/compose/) is an awesome tool for creating isolated development environments with [Docker](http://docker.com) by using simple configurations with [YAML](http://www.yaml.org/). It's clean and easy enough to wrap your head around, even if you are new to Docker.
1010

11-
If you're like me, you are using a development server like [nodemon](https://github.com/remy/nodemon) that watches all your file changes and restarts your app accordingly. Bringing this workflow over to Docker Compose (née Fig) is a bit tricky. You can find many Github repositories that aim to show you how to do it, but not one (at least of the ones I found) of them are not suitable for "real world" development. Most of them even require you to rebuild your Dockerfile to reflect file changes - _seriously?!_
12-
13-
I hope the following real world examples will save you from some headache (like I had) while trying to figure out how to (pragmatically) use Docker Compose for your Nodejs apps.
11+
If you're like us, you're using a development server like [nodemon](https://github.com/remy/nodemon) that watches all your file changes and reloads your app. Bringing this workflow over to Docker Compose is a bit tricky. We hope the following real world examples will save you from headaches while trying to figure out how to (pragmatically) use Docker Compose for your Nodejs apps.
1412

1513
## Examples
1614

1715
### Basic skeleton with Express app generator
18-
[https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/00-basic-express-generator](https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/00-basic-express-generator)
16+
[https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/00-basic-express-generator](https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/00-basic-express-generator)
1917

2018
### Express app with nodemon development server
21-
[https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/01-express-nodemon](https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/01-express-nodemon)
19+
[https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/01-express-nodemon](https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/01-express-nodemon)
2220

2321
### Express app with Redis and nodemon development server
24-
[https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/02-express-redis-nodemon](https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/02-express-redis-nodemon)
22+
[https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/02-express-redis-nodemon](https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/02-express-redis-nodemon)
2523

2624
### Express app with Gulp.js build system
27-
[https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/03-express-gulp-watch](https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/03-express-gulp-watch)
25+
[https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/03-express-gulp-watch](https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/03-express-gulp-watch)
2826

2927
### Express app with Grunt.js build system
30-
[https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/04-express-grunt-watch](https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/04-express-grunt-watch)
28+
[https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/04-express-grunt-watch](https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/04-express-grunt-watch)
3129

3230
### Nginx, Express, Redis and nodemon
33-
[https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/05-nginx-express-redis-nodemon](https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/05-nginx-express-redis-nodemon)
31+
[https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/05-nginx-express-redis-nodemon](https://github.com/geekcell/docker-compose-nodejs-examples/tree/master/05-nginx-express-redis-nodemon)
3432

3533
More to come...
3634

37-
## Maintainer
35+
## Maintainers
36+
37+
Geek Cell
38+
39+
* Twitter: [@thegeekcell](https://twitter.com/thegeekcell)
40+
* Web: [https://geekcell.io](https://geekcell.io)
41+
42+
### Previous Maintainer
3843

3944
Pascal Cremer
4045

@@ -44,24 +49,4 @@ Pascal Cremer
4449

4550
## License
4651

47-
> The MIT License (MIT)
48-
>
49-
> Copyright (c) 2014-2017 Pascal Cremer
50-
>
51-
>Permission is hereby granted, free of charge, to any person obtaining a copy
52-
>of this software and associated documentation files (the "Software"), to deal
53-
>in the Software without restriction, including without limitation the rights
54-
>to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
55-
>copies of the Software, and to permit persons to whom the Software is
56-
>furnished to do so, subject to the following conditions:
57-
>
58-
>The above copyright notice and this permission notice shall be included in all
59-
>copies or substantial portions of the Software.
60-
>
61-
>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
62-
>IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
63-
>FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
64-
>AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
65-
>LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
66-
>OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
67-
>SOFTWARE.
52+
[MIT](https://choosealicense.com/licenses/mit/)

0 commit comments

Comments
 (0)