mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2025-12-24 15:11:38 +00:00
Update for leanpub preview
This commit is contained in:
AutoPenguin
@@ -39,13 +39,4 @@ Name | Description | Badges
|
||||
[funkypenguin/turtle-pool](https://hub.docker.com/r/funkypenguin/turtle-pool/)<br/>[](https://hub.docker.com/r/funkypenguin/turtle-pool//)| turtle-pool |[](https://hub.docker.com/r/funkypenguin/turtle-pool/)<br/>[](https://hub.docker.com/r/funkypenguin/turtle-pool/)
|
||||
[funkypenguin/turtlecoin](https://hub.docker.com/r/funkypenguin/turtlecoin/)<br/>[](https://hub.docker.com/r/funkypenguin/turtlecoin/)| turtlecoin |[](https://hub.docker.com/r/funkypenguin/turtlecoin/)<br/>[](https://hub.docker.com/r/funkypenguin/turtlecoin/)
|
||||
[funkypenguin/x-cash](https://hub.docker.com/r/funkypenguin/x-cash/)<br/>[](https://hub.docker.com/r/funkypenguin/x-cash/)| X-CASH cryptocurrency daemon/services |[](https://hub.docker.com/r/funkypenguin/x-cash/)<br/>[](https://hub.docker.com/r/funkypenguin/x-cash/)
|
||||
[funkypenguin/xmrig-cpu](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)<br/>[](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)| xmrig-cpu |[](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)<br/>[](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)|
|
||||
|
||||
|
||||
## Chef's Notes
|
||||
|
||||
### Tip your waiter (support me) 👏
|
||||
|
||||
Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏
|
||||
|
||||
### Your comments? 💬
|
||||
[funkypenguin/xmrig-cpu](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)<br/>[](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)| xmrig-cpu |[](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)<br/>[](https://hub.docker.com/r/funkypenguin/xmrig-cpu/)|
|
||||
@@ -1,6 +1,6 @@
|
||||
# Data layout
|
||||
|
||||
The applications deployed in the stack utilize a combination of data-at-rest (_static config, files, etc_) and runtime data (_live database files_). The realtime data can't be [backed up](/recipes/duplicity) with a simple copy-paste, so where we employ databases, we also include containers to perform a regular export of database data to a filesystem location.
|
||||
The applications deployed in the stack utilize a combination of data-at-rest (_static config, files, etc_) and runtime data (_live database files_). The realtime data can't be [backed up](https://geek-cookbook.funkypenguin.co.nz/)recipes/duplicity) with a simple copy-paste, so where we employ databases, we also include containers to perform a regular export of database data to a filesystem location.
|
||||
|
||||
So that we can confidently backup all our data, I've setup a data layout as follows:
|
||||
|
||||
@@ -14,13 +14,4 @@ Realtime data (typically database files or files-in-use) are stored in /var/data
|
||||
|
||||
## Static data
|
||||
|
||||
Static data goes into /var/data/[recipe name], and includes anything that can be safely backed up while a container is running. This includes database exports of the runtime data above.
|
||||
|
||||
|
||||
## Chef's Notes
|
||||
|
||||
### Tip your waiter (support me) 👏
|
||||
|
||||
Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you!
|
||||
|
||||
### Your comments?
|
||||
Static data goes into /var/data/[recipe name], and includes anything that can be safely backed up while a container is running. This includes database exports of the runtime data above.
|
||||
@@ -49,13 +49,4 @@ The key's randomart image is:
|
||||
+----[SHA256]-----+
|
||||
```
|
||||
|
||||
Now add the contents of /var/data/git-docker/data/.ssh/id_ed25519.pub to your git account, and off you go - just run "git" from your Atomic host as usual, and pretend that you have the client installed!
|
||||
|
||||
|
||||
## Chef's Notes
|
||||
|
||||
### Tip your waiter (support me) 👏
|
||||
|
||||
Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you!
|
||||
|
||||
### Your comments?
|
||||
Now add the contents of /var/data/git-docker/data/.ssh/id_ed25519.pub to your git account, and off you go - just run "git" from your Atomic host as usual, and pretend that you have the client installed!
|
||||
@@ -53,14 +53,4 @@ Network | Range
|
||||
[Magento](https://geek-cookbook.funkypenguin.co.nz/recipes/magento/) | 172.16.51.0/24
|
||||
[Graylog](https://geek-cookbook.funkypenguin.co.nz/recipes/graylog/) | 172.16.52.0/24
|
||||
[Harbor](https://geek-cookbook.funkypenguin.co.nz/recipes/graylog/) | 172.16.53.0/24
|
||||
[Harbor-Clair](https://geek-cookbook.funkypenguin.co.nz/recipes/graylog/) | 172.16.54.0/24
|
||||
|
||||
|
||||
|
||||
## Chef's Notes
|
||||
|
||||
### Tip your waiter (support me) 👏
|
||||
|
||||
Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you!
|
||||
|
||||
### Your comments?
|
||||
[Harbor-Clair](https://geek-cookbook.funkypenguin.co.nz/recipes/graylog/) | 172.16.54.0/24
|
||||
@@ -15,7 +15,7 @@ This is the role of the OAuth proxy.
|
||||
When employing the **OAuth proxy** , the proxy sits in the middle of this transaction - traefik sends the web client to the OAuth proxy, the proxy authenticates the user against a 3rd-party source (_GitHub, Google, etc_), and then passes authenticated requests on to the web app in the container.
|
||||
|
||||
Illustrated below:
|
||||
|
||||
images/oauth_proxy.png)
|
||||
|
||||
The advantage under this design is additional security. If I'm deploying a web app which I expect only myself to require access to, I'll put the oauth_proxy in front of it. The overhead is negligible, and the additional layer of security is well-worth it.
|
||||
|
||||
@@ -47,7 +47,7 @@ I created **/var/data/oauth_proxy/authenticated-emails.txt**, and add my own ema
|
||||
|
||||
### Configure stack
|
||||
|
||||
You'll need to define a service for the oauth_proxy in every stack which you want to protect. Here's an example from the [Wekan](/recipes/wekan/) recipe:
|
||||
You'll need to define a service for the oauth_proxy in every stack which you want to protect. Here's an example from the [Wekan](https://geek-cookbook.funkypenguin.co.nz/)recipes/wekan/) recipe:
|
||||
|
||||
```
|
||||
proxy:
|
||||
@@ -76,13 +76,4 @@ proxy:
|
||||
Note above how:
|
||||
* Labels are required to tell Traefik to forward the traffic to the proxy, rather than the backend container running the app
|
||||
* An environment file is defined, but..
|
||||
* The redirect URL must still be passed to the oauth_proxy in the command argument
|
||||
|
||||
|
||||
## Chef's Notes
|
||||
|
||||
### Tip your waiter (support me) 👏
|
||||
|
||||
Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you!
|
||||
|
||||
### Your comments?
|
||||
* The redirect URL must still be passed to the oauth_proxy in the command argument
|
||||
@@ -55,13 +55,4 @@ docker run -d --name vpn-client \
|
||||
ekristen/openvpn-client --config /vpn/my-host-config.ovpn
|
||||
```
|
||||
|
||||
Now every time my node boots, it establishes a VPN tunnel back to my pfsense host and (_by using custom configuration directives in OpenVPN_) is assigned a static VPN IP.
|
||||
|
||||
|
||||
## Chef's Notes
|
||||
|
||||
### Tip your waiter (support me) 👏
|
||||
|
||||
Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you!
|
||||
|
||||
### Your comments?
|
||||
Now every time my node boots, it establishes a VPN tunnel back to my pfsense host and (_by using custom configuration directives in OpenVPN_) is assigned a static VPN IP.
|
||||
@@ -23,12 +23,4 @@ For a visual "top-like" display of your container's activity (_as well as a [det
|
||||
To execute, simply run `docker run --rm -ti --name ctop -v /var/run/docker.sock:/var/run/docker.sock quay.io/vektorlab/ctop:latest`
|
||||
|
||||
Example:
|
||||
|
||||
|
||||
## Chef's Notes
|
||||
|
||||
### Tip your waiter (support me) 👏
|
||||
|
||||
Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you!
|
||||
|
||||
### Your comments?
|
||||
|
||||
Reference in New Issue
Block a user