add things for redis to post 7

Author: hyperdefined

src/posts/7.md

@@ -42,6 +42,29 @@ docker network create --driver bridge --ipv6 --subnet fd00:c0ba:105::/64 cobalt
 
 This creates a network for us to use for our cobalt instance that allows IPv6.
 
+<blockquote class="alert-box">
+<p>If you want to use redis/valkey or a HTTP proxy with your cobalt instance, please read below! If you don't, then you can skip to Section 1.2.</p>
+</blockquote>
+
+This assumes redis/valkey or your HTTP proxy is on your **host machine** and not in another container. If your redis/valkey or proxy is in another container, simply add those containers to the cobalt network and use the container's name as the IP address. If not, follow below.
+
+Create the cobalt network with a static IPv4 address, just so it doesn't change. If you made the network earlier, you need to delete and remake it below. If the IP space clashes, change it to anything else.
+```bash
+docker network create --driver bridge --ipv6 --subnet fd00:c0ba:105::/64 --subnet 192.168.105.0/24 --gateway 192.168.105.1 cobalt
+```
+
+Once you create the network, you need to let traffic through your firewall. If you are using something like `ufw`, you can do so below:
+```bash
+ufw allow from 192.168.105.0/24 to any port 6379 comment "cobalt network to redis on host"
+```
+You'll need to do this for any port. The command above is for redis, but you need to do anymore if needed.
+
+Once that is done, you can tell cobalt to use redis like so:
+```
+API_REDIS_URL=redis://192.168.105.1:6379
+```
+You would use the gateway IP from the network you created. You also want to make sure your service is binded to `0.0.0.0` and **NOT ALLOWED** through your firewall.
+
 ### 1.2 Setup wgcf
 
 Head over to https://github.com/ViRb3/wgcf/releases/latest and download one from the asset list based on your server.