This commit is contained in:
DoTheEvo 2022-10-31 08:54:58 +01:00
parent 1ac10fab9b
commit c8da4ead86
4 changed files with 12 additions and 23 deletions

View File

@ -46,7 +46,7 @@ And **just works** means fully works. No additional configuration needed
for https redirect, or special services if target is not a container, for https redirect, or special services if target is not a container,
or need to deal with load balancer, or need to add boilerplate headers or need to deal with load balancer, or need to add boilerplate headers
for x-forward, or other extra work.<br> for x-forward, or other extra work.<br>
In short, it has great out of the box defaults, fitting majority of uses It has great out of the box defaults, fitting majority of uses
and only some special casess with extra functionality need extra work. and only some special casess with extra functionality need extra work.
![url](https://i.imgur.com/iTjzPc0.png) ![url](https://i.imgur.com/iTjzPc0.png)
@ -239,8 +239,8 @@ networks:
You are on your local network and you are likely running the docker host You are on your local network and you are likely running the docker host
inside the same network.<br> inside the same network.<br>
If that's the case then shit will not work without editing the hosts file.<br> If that's the case then shit will not work without editing the hosts file.<br>
Reason being that when you write that `a.{$MY_DOMAIN}` in to your browser, Reason being that when you write that `a.example.com` in to your browser,
you are asking google's DNS for `a.{$MY_DOMAIN}` IP address. you are asking google's DNS for `a.example.com` IP address.
It will give you your own public IP, and most routers/firewalls wont allow It will give you your own public IP, and most routers/firewalls wont allow
this loopback, where your requests should go out and then right back. this loopback, where your requests should go out and then right back.

View File

@ -15,7 +15,8 @@ Minecraft is written in Java.<br>
This setup is using [itzg](https://github.com/itzg/docker-minecraft-server) This setup is using [itzg](https://github.com/itzg/docker-minecraft-server)
maintend docker image. Specificly [Purpur](https://purpurmc.org/docs/) maintend docker image. Specificly [Purpur](https://purpurmc.org/docs/)
version which is a fork of version which is a fork of
[paper](https://www.spigotmc.org/wiki/what-is-spigot-craftbukkit-bukkit-vanilla-forg/). [Paper](https://www.spigotmc.org/wiki/what-is-spigot-craftbukkit-bukkit-vanilla-forg/)
which is a fork of [Spigot](https://www.spigotmc.org/wiki/what-is-spigot-craftbukkit-bukkit-vanilla-forg/).
Few plugings are used which allow to host multiple worlds on the same server.<br> Few plugings are used which allow to host multiple worlds on the same server.<br>
Also [docker-rcon-web-admin](https://github.com/itzg/docker-rcon-web-admin) Also [docker-rcon-web-admin](https://github.com/itzg/docker-rcon-web-admin)
container is runnig to be able to do basic console tasks from web interface. container is runnig to be able to do basic console tasks from web interface.
@ -164,7 +165,7 @@ Should they be able to bring stuff from one world to another? No?<br>
Well you need `multiverse inventory`.<br> Well you need `multiverse inventory`.<br>
Should the connecting of worlds with their nether be easy?<br> Should the connecting of worlds with their nether be easy?<br>
Well you need `multiverse netherportals`.<br> Well you need `multiverse netherportals`.<br>
Should they spawn in lobby on connecting, Should they spawn in lobby on start,
but also remember the position in the worlds when entering portals?<br> but also remember the position in the worlds when entering portals?<br>
Well you need the rest of that shit, `EssentialsX` and `EssentialsX Spawn`. Well you need the rest of that shit, `EssentialsX` and `EssentialsX Spawn`.

View File

@ -127,8 +127,8 @@ services:
volumes: volumes:
- ./prometheus.yml:/etc/prometheus/prometheus.yml - ./prometheus.yml:/etc/prometheus/prometheus.yml
- ./prometheus_data:/prometheus - ./prometheus_data:/prometheus
expose: ports:
- 9090 - 9090:9090
labels: labels:
org.label-schema.group: "monitoring" org.label-schema.group: "monitoring"
@ -335,22 +335,8 @@ Caddy v2 is used, details
[here](https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/caddy_v2).</br> [here](https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/caddy_v2).</br>
The setup is accessed through grafana. The setup is accessed through grafana.
But occasionally there might be need to check with prometheus, But occasionally there might be need to check with prometheus or pushgateway
which will be available on \<docker-host-ip>:9090.</br> which are available on \<docker-host-ip>:9090.</br>
For that to work, Caddy will also need port 9090 published.
`Caddyfile`
```
grafana.{$MY_DOMAIN} {
reverse_proxy grafana:3000
}
:9090 {
reverse_proxy prometheus:9090
}
```
*Extra info:* `:9090` is short notation for `localhost:9090`
--- ---

View File

@ -26,6 +26,8 @@ This setup runs directly on the host machine, not in a container.<br>
Most of the stuff here is based on Arch wiki and Most of the stuff here is based on Arch wiki and
[this tutorial](https://securityespresso.org/tutorials/2019/03/22/vpn-server-using-wireguard-on-ubuntu/). [this tutorial](https://securityespresso.org/tutorials/2019/03/22/vpn-server-using-wireguard-on-ubuntu/).
[This](https://github.com/mikeroyal/WireGuard-Guide) also seems rich in content.
# Files and directory structure # Files and directory structure
``` ```