trent/trentdocs_website
1
0
Fork 0
mirror of https://github.com/TrentSPalmer/trentdocs_website.git synced 2024-11-23 08:01:30 -08:00
Code Issues Projects Releases Wiki Activity

extend docs/arch_redis_nspawn.md minor correction docs/nspawn.md

Browse Source
This commit is contained in:
Trent Palmer 2017-06-29 09:12:27 -07:00
parent 9b33bab0eb
commit 09a172d608
6 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/arch_redis_nspawn.md
View File

@ -1,7 +1,7 @@
# Quick Dirty Redis Nspawn Container on Arch Linux # Quick Dirty Redis Nspawn Container on Arch Linux
Refer to the [Nspawn](nspawn.md) page for setting up the nspawn container. Refer to the [Nspawn](nspawn.md) page for setting up the nspawn container,
install redis, and start/enable redis.service.
Once you have the container running, it seems all you have to do to get Once you have the container running, it seems all you have to do to get
things working in a container subnet is to change the bind address. things working in a container subnet is to change the bind address.

1
docs/nspawn.md
View File

@ -46,7 +46,6 @@ Name=br0
Kind=bridge Kind=bridge
``` ```
```text ```text
# /etc/systemd/network/50-br0.netdev # /etc/systemd/network/50-br0.netdev
[Match] [Match]

5
site/arch_redis_nspawn/index.html
View File

@ -111,8 +111,9 @@
<div class="section"> <div class="section">
<h1 id="quick-dirty-redis-nspawn-container-on-arch-linux">Quick Dirty Redis Nspawn Container on Arch Linux</h1> <h1 id="quick-dirty-redis-nspawn-container-on-arch-linux">Quick Dirty Redis Nspawn Container on Arch Linux</h1>
<p>Refer to the <a href="../nspawn/">Nspawn</a> page for setting up the nspawn container.</p> <p>Refer to the <a href="../nspawn/">Nspawn</a> page for setting up the nspawn container,
<p>Once you have the container running, it seems all you have to do to get install redis, and start/enable redis.service.
Once you have the container running, it seems all you have to do to get
things working in a container subnet is to change the bind address.</p> things working in a container subnet is to change the bind address.</p>
<pre><code class="text"># /etc/redis.conf <pre><code class="text"># /etc/redis.conf
# bind 127.0.0.1 # bind 127.0.0.1

2
site/index.html
View File

@ -174,5 +174,5 @@
<!-- <!--
MkDocs version : 0.16.3 MkDocs version : 0.16.3
Build Date UTC : 2017-06-29 06:20:03 Build Date UTC : 2017-06-29 16:12:17
--> -->

4
site/mkdocs/search_index.json
View File

@ -177,12 +177,12 @@
}, },
{ {
"location": "/arch_redis_nspawn/", "location": "/arch_redis_nspawn/",
"text": "Quick Dirty Redis Nspawn Container on Arch Linux\n\n\nRefer to the \nNspawn\n page for setting up the nspawn container.\n\n\nOnce you have the container running, it seems all you have to do to get\nthings working in a container subnet is to change the bind address.\n\n\n# /etc/redis.conf\n# bind 127.0.0.1\nbind 0.0.0.0\n\n\n\n\nyou can nmap port 6379, be sure to restart redis\n\n\nAgain I would refer you to the Arch Wiki", "text": "Quick Dirty Redis Nspawn Container on Arch Linux\n\n\nRefer to the \nNspawn\n page for setting up the nspawn container,\ninstall redis, and start/enable redis.service.\nOnce you have the container running, it seems all you have to do to get\nthings working in a container subnet is to change the bind address.\n\n\n# /etc/redis.conf\n# bind 127.0.0.1\nbind 0.0.0.0\n\n\n\n\nyou can nmap port 6379, be sure to restart redis\n\n\nAgain I would refer you to the Arch Wiki",
"title": "Quick Dirty Redis Nspawn Container on Arch Linux" "title": "Quick Dirty Redis Nspawn Container on Arch Linux"
}, },
{ {
"location": "/arch_redis_nspawn/#quick-dirty-redis-nspawn-container-on-arch-linux", "location": "/arch_redis_nspawn/#quick-dirty-redis-nspawn-container-on-arch-linux",
"text": "Refer to the Nspawn page for setting up the nspawn container. Once you have the container running, it seems all you have to do to get\nthings working in a container subnet is to change the bind address. # /etc/redis.conf\n# bind 127.0.0.1\nbind 0.0.0.0 you can nmap port 6379, be sure to restart redis Again I would refer you to the Arch Wiki", "text": "Refer to the Nspawn page for setting up the nspawn container,\ninstall redis, and start/enable redis.service.\nOnce you have the container running, it seems all you have to do to get\nthings working in a container subnet is to change the bind address. # /etc/redis.conf\n# bind 127.0.0.1\nbind 0.0.0.0 you can nmap port 6379, be sure to restart redis Again I would refer you to the Arch Wiki",
"title": "Quick Dirty Redis Nspawn Container on Arch Linux" "title": "Quick Dirty Redis Nspawn Container on Arch Linux"
}, },
{ {

10
site/sitemap.xml
View File

@ -4,7 +4,7 @@
<url> <url>
<loc>/</loc> <loc>/</loc>
<lastmod>2017-06-28</lastmod> <lastmod>2017-06-29</lastmod>
<changefreq>daily</changefreq> <changefreq>daily</changefreq>
</url> </url>
@ -12,7 +12,7 @@
<url> <url>
<loc>/serve_and_share_apps_from_your_phone_with_fdroid/</loc> <loc>/serve_and_share_apps_from_your_phone_with_fdroid/</loc>
<lastmod>2017-06-28</lastmod> <lastmod>2017-06-29</lastmod>
<changefreq>daily</changefreq> <changefreq>daily</changefreq>
</url> </url>
@ -20,7 +20,7 @@
<url> <url>
<loc>/nspawn/</loc> <loc>/nspawn/</loc>
<lastmod>2017-06-28</lastmod> <lastmod>2017-06-29</lastmod>
<changefreq>daily</changefreq> <changefreq>daily</changefreq>
</url> </url>
@ -28,7 +28,7 @@
<url> <url>
<loc>/arch_redis_nspawn/</loc> <loc>/arch_redis_nspawn/</loc>
<lastmod>2017-06-28</lastmod> <lastmod>2017-06-29</lastmod>
<changefreq>daily</changefreq> <changefreq>daily</changefreq>
</url> </url>
@ -36,7 +36,7 @@
<url> <url>
<loc>/arch_postgresql_nspawn/</loc> <loc>/arch_postgresql_nspawn/</loc>
<lastmod>2017-06-28</lastmod> <lastmod>2017-06-29</lastmod>
<changefreq>daily</changefreq> <changefreq>daily</changefreq>
</url> </url>