docker-compose service files and caddy reverse proxy config for eutychia.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Kay c6fd66894a license typo 2 weeks ago
host newlicense 2 weeks ago
proxy newlicense 2 weeks ago
.README.template.md newlicense 2 weeks ago
.gitlab-ci.yml newlicense 2 weeks ago
CHANGELOG.md newlicense 2 weeks ago
LICENSE license typo 2 weeks ago
README.md newlicense 2 weeks ago

README.md

eutychia-org-services

docker-compose service files and caddy reverse proxy config for eutychia.org

features

  • machine A (home computer)
    • runs all services via docker-compose
    • all services load-balanced by traefik
    • is wireguard host
  • machine B (cheap vps)
    • is wireguard client
    • reverse-proxies all traffic with Caddy2

machine a (host)

requirements:

  • docker
  • docker-compose

run:

  • first ./host/_traefik
  • then all services in ./host/*

there is ./host/crontab ran as root to clean logs and run cron job for nextcloud until i make it a container thingy

machine b (proxy)

see ./proxy/init.sh for an idea of how to setup the proxy

custom caddy build with

  • layer4
  • gandi dns

easiest way is to go to https://caddyserver.com/download you can download custom builds

the configuration i use is in ./proxy/Caddyfile.json

see https://github.com/libdns/gandi for how to generate creds and set GANDI_API_KEY environment var so that the service can access it (if running with systemd systemctl edit caddy and google how to add overrides to a system service)

i use systemd and had to edit the caddy.service file because by default it uses Caddyfile

there is no "json" adapter (don't try, wasted many time on that), instead you simply need to make sure the config file ends with .json and it should work (yeah because caddy devs really like to think filename suffixes make the format, cant just put json in Caddyfile directly) /rant

TODO

  • proper fix comfy center (wildcards without tls ???)

License

Most all of my work is now licensed under a modified CC-BY-NC-SA 4.0 AFEdit plus accounting for states existing in our world on top of capitalism.

This is a weird choice for code right?

Here are a few key reasons:

  • my definition of "open" involves being able to share and modify, you are able to do such things, just not make money off of it, or oppress people
  • my definition of "free" involves being able to share and modify, you are able to do such things, not just make money off of it, or oppressing people

So no, amongst other things, this list is not exhaustive,

  • you cannot have somebody work on my tool and redistribute it to your employees
  • you cannot resell copies of this because in this age distribution is not done with floppy disks and the internet is a thing
  • you cannot use it to generate revenue yourself
  • you cannot use it to "generate value" in a capitalistic sense
  • you cannot use it in any military capacity
  • you cannot use it in any law enforcement capacity
  • you cannot use it in any state backed capacity
  • you cannot use it in any surveillance capacity
  • you cannot use it if you represent the interests of a state
  • you cannot use it to oppress, spy, control in any capacity
  • you cannot use it to injure, harm, kill, whether physically or psychologically

You can, however,

  • change it to do whatever you please
  • share it to anyone you please with attribution and under the same license
  • use it as much as you please
  • and probably a bunch of other cool things that are possible outside of a capitalistic, imperialistic frame of reference that permeates the tech scene

Most of the "arguments" for how "free" and "open" source licenses are done still to this day stem from archaic concepts that might not even be relevant these days and I fail to see the issue with this license not being "interoperable" with a bunch of what I deem to be "bad" licenses, as they all allow for commercial usage.

I also will not make any attempts to monetize these works and will at most ever offer the possibility to donate to me directly if you enjoy what I do.

Thank you that is all.

Development

To clone the repository locally:

$ git clone https://code.juke.fr/kay/eutychia-org-services.git

Contributing

More to come later.

Issues

Open new issues by mailing eutychia.gitlab+eutychia-org-services-issue@gmail.com


beep boop