2024-07-20 11:43:49 -07:00
2020-04-26 18:36:20 -07:00
2024-03-10 11:26:07 -07:00
2024-05-06 17:49:27 -07:00
2020-04-25 15:52:39 -07:00
2023-10-06 18:39:10 -07:00
2024-06-30 17:48:44 -07:00
2024-03-15 09:06:34 -07:00
2024-07-18 10:25:47 -07:00
2024-03-16 12:51:12 -07:00
2023-07-20 20:41:28 -07:00
2024-04-27 17:53:04 -07:00
2024-04-27 17:53:04 -07:00
2024-04-22 10:24:49 -07:00
2024-03-17 23:28:27 -07:00
2020-04-27 22:50:01 -07:00
2023-10-02 01:01:57 -07:00
2024-04-21 19:41:30 -07:00
2024-07-19 11:24:57 -07:00
2024-03-10 11:26:07 -07:00
2020-04-25 15:52:39 -07:00
2024-07-18 14:22:56 -07:00
2020-04-25 10:40:59 -07:00
2024-03-17 23:28:27 -07:00
2024-04-24 10:44:57 -07:00
2020-04-28 14:59:52 -07:00
2024-07-20 11:12:40 -07:00
2024-06-27 20:53:15 -07:00
2020-04-25 15:52:39 -07:00
2024-04-24 10:44:57 -07:00
2020-04-28 23:41:40 -07:00
2024-07-19 11:24:57 -07:00
2020-04-25 15:52:39 -07:00
2024-06-24 12:38:22 -07:00
2020-04-16 21:13:59 -07:00
2020-05-18 20:08:26 -07:00
2024-07-18 10:15:04 -07:00

Nick Yeoman's Collection of Docker compose files

Author: Nick Yeoman.

These cookbooks are created with the intent of using Docker's extend feature. This way, you can run multiple containers in different domains but still have only one file to update.

These compose files make a few assumptions:

  1. You are only running on one host.
  2. You are using Nginx Proxy Manager (although most have redundant port access).
  3. Volumes are stored in the project folder under "data", git ignored and backed up externally.

The intended workflow is as follows:

  1. Clone the repository locally git clone git@github.com:nickyeoman/docker-compose-cookbooks.git /git-repos/docker-compose-cookbooks
  2. Create a project directory, usually by domain mkdir /projects/domainname-com
  3. Create a .env file in the project directory touch .env
  4. Add the COOKBOOK Variable to the project's env file: COOKBOOK=/git-repos/docker-compose-cookbooks
  5. Create a .gitignore file in the project directory and ignore "data/"
  6. Create a docker-compose.yml file in the project directory with the external code given in the README file in the container folder.

Example

Here is an example of how your project's docker-compose file might look:

version: '3.4'

networks:
  proxy:
    external: true

services:
  proxy:
    extends:
      file: ${COOKBOOK}/nginx-proxy-manager/docker-compose.yml
      service: proxy
    env_file:
      - .env
    networks:
      - proxy
S
Description
Backup copy
Readme
757 KiB
Languages
Python 31.8%
Shell 29.6%
HTML 22.7%
Dockerfile 15.9%