mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2026-02-07 21:01:52 +00:00
Use mkdocs snippets to template common content blocks (#135)
This commit is contained in:
@@ -61,8 +61,7 @@ GITLAB_ROOT_PASSWORD=changeme
|
||||
|
||||
Create a docker swarm config file in docker-compose syntax (v3), something like this:
|
||||
|
||||
!!! tip
|
||||
I share (_with my [sponsors](https://github.com/sponsors/funkypenguin)_) a private "_premix_" git repository, which includes necessary docker-compose and env files for all published recipes. This means that sponsors can launch any recipe with just a ```git pull``` and a ```docker stack deploy``` 👍
|
||||
--8<-- "premix-cta.md"
|
||||
|
||||
````
|
||||
version: '3'
|
||||
@@ -132,9 +131,6 @@ Launch the mail server stack by running ```docker stack deploy gitlab -c <path -
|
||||
|
||||
Log into your new instance at https://[your FQDN], with user "root" and the password you specified in gitlab.env.
|
||||
|
||||
[^1]: I use the **sameersbn/gitlab:latest** image, rather than a specific version. This lets me execute updates simply by redeploying the stack (and why **wouldn't** I want the latest version?)
|
||||
|
||||
## Chef's Notes 📓
|
||||
|
||||
A few comments on decisions taken in this design:
|
||||
|
||||
1. I use the **sameersbn/gitlab:latest** image, rather than a specific version. This lets me execute updates simply by redeploying the stack (and why **wouldn't** I want the latest version?)
|
||||
--8<-- "recipe-footer.md"
|
||||
Reference in New Issue
Block a user