2
0
Fork
You've already forked devtools
0
No description
  • Shell 59.1%
  • TypeScript 40.9%
2023年09月02日 10:52:50 -07:00
entanglement.garden keto updates 2023年09月02日 10:52:50 -07:00
haproxy start devtools repo 2023年03月26日 14:50:55 -07:00
libvirt start devtools repo 2023年03月26日 14:50:55 -07:00
ory keto updates 2023年09月02日 10:52:50 -07:00
.gitignore initial keto work 2023年07月30日 16:09:49 -07:00
clean-libvirt.sh start devtools repo 2023年03月26日 14:50:55 -07:00
COPYING start devtools repo 2023年03月26日 14:50:55 -07:00
default-config.sh initial keto work 2023年07月30日 16:09:49 -07:00
entanglement-common.env add EG_DOMAIN to common.env 2023年07月20日 12:23:12 -07:00
README.md minor readme improvements 2023年03月26日 14:57:15 -07:00
start-networking.sh start devtools repo 2023年03月26日 14:50:55 -07:00
start-services.sh initial keto work 2023年07月30日 16:09:49 -07:00
stop-networking.sh start devtools repo 2023年03月26日 14:50:55 -07:00
stop-services.sh initial keto work 2023年07月30日 16:09:49 -07:00

Entanglement Garden Local Development Environment

some helpers to setup an Entanglement Garden development environment on your local machine with podman

usage

  • Install dependencies: libvirt-daemon-system openvswitch-switch podman jq golang-go
  • Configure networking: sudo ./start-networking.sh
  • Start the required services: ./start-services.sh
    • This will configure all entanglement services and support services.
    • When everything is running, you will be shown admin credentials that can be used to log in to the web UI.
  • After all services have started, you will need to run the rhyzome agent:
    • From ../rhyzome.git: cp rhyzome.localdev.json rhyzome.json then go run ./cmd/rhyzome-agent

Unfortunately, some components struggle with specifying a port in some URLs. start-services.sh will expose Oathkeeper on port 4455, I've been using socat to redirect localhost:443 to localhost:4455:

sudo socat tcp-listen:443,fork tcp-connect:localhost:4455

When everything is running, visit https://console.entanglement.garden.localtest.me and click through the certificate validation failure. When you login for the first time, you will need to click through another such warning when redirected to Kratos.

other info

  • persistant state is stored in state/ directory. Due to container weirdness, it cannot be deleted by your user (i sudo rm -rf when i need to clear it)
  • there are several configurable options, listed in default-config.sh. To override any of them, create config.sh and add overrides
  • most of the services have a dev-server.sh in their repo that will build the a container and launch it into the devtools network.
    • You will need to stop the the container that start-services.sh started
  • start-services.sh and start-networking.sh have stop- counterparts that tear down the system
  • running stop-services.sh will not delete any VMs or disks or other libvirt objects, but maybe it should. In the mean time, use clean-libvirt.sh