Update VNC functionality for Proxmox 7 (#148)
Chown `targets`, Add run and kill scripts
Lol Joe figured it out
* Dude it works holy shit
We need to fix some logistical bugs, probably, and also like remove dead
code lol
* Open VNC session on the node that the VM belongs
Figured out why I couldn't open a session on anything but 01. It was
because I was making the API call on proxmox01-nrh. So that's where the
session opened. I hope that by doing this, it will balance the load
(what little there is) from VNC sessions.
* Update websockify-related tasks
* Remove SSH key from build
* Add option to specify VNC port.
Should be 443 for OKD, probably 8081 for development.
This hosts a smattering of fixes, acutally uses gunicorn properly(?),
launches websockify correctly, and introduces MORE DEAD CODE!
TODO: Fix the scheduling system
* Make things not crash as much :)
* Remove obviously dead code
There's still some code in here that may require more careful
extraction, testing, and review, so I'm saving that for another PR.
* Fix Joe's complaints
* Replace hardcoded URL
2022-07-30 00:56:00 +00:00
|
|
|
#!/bin/bash
|
|
|
|
|
podman run --rm -d --network=proxstar --name=proxstar-redis redis:alpine
|
|
|
|
|
podman run --rm -d --network=proxstar --name=proxstar-postgres -e POSTGRES_PASSWORD=changeme -v ./HACKING/proxstar-postgres/volume:/var/lib/postgresql/data:Z proxstar-postgres
|
|
|
|
|
podman run --rm -d --network=proxstar --name=proxstar-rq-scheduler --env-file=HACKING/.env --entrypoint ./start_scheduler.sh proxstar
|
|
|
|
|
podman run --rm -d --network=proxstar --name=proxstar-rq --env-file=HACKING/.env --entrypoint ./start_worker.sh proxstar
|
2022-08-26 03:36:41 +00:00
|
|
|
podman run --rm -it --network=proxstar --name=proxstar -p 8000:8000 -p 8001:8001 --env-file=HACKING/.env --entrypoint='["gunicorn", "proxstar:app", "--bind=0.0.0.0:8000"]' proxstar
|