cheshire
/
hscloud
forked from hswaw/hscloud
1
0
Fork 0
Code Pull Requests Activity
hscloud/hswaw/oodviewer
History
q3k 97b5cd7b58 go: re-do the entire thing 
This is a mega-change, but attempting to split this up further is
probably not worth the effort.

Summary:

1. Bump up bazel, rules_go, and others.
2. Switch to new go target naming (bye bye go_default_library)
3. Move go deps to go.mod/go.sum, use make gazelle generate from that
4. Bump up Python deps a bit

And also whatever was required to actually get things to work - loads of
small useless changes.

Tested to work on NixOS and Ubuntu 20.04:

   $ bazel build //...
   $ bazel test //...

Change-Id: I8364bdaa1406b9ae4d0385a6b607f3e7989f98a9
Reviewed-on: https://gerrit.hackerspace.pl/c/hscloud/+/1583
Reviewed-by: q3k <q3k@hackerspace.pl>
 		2023-09-22 21:50:19 +00:00
..
secrets hswaw/oodviewer: init 2021-03-07 16:57:02 +01:00
templates go: re-do the entire thing 2023-09-22 21:50:19 +00:00
BUILD.bazel go: re-do the entire thing 2023-09-22 21:50:19 +00:00
OWNERS hswaw/oodviewer: fix OWNERS 2021-03-07 14:47:10 +00:00
README.md hswaw/oodviewer: init 2021-03-07 16:57:02 +01:00
app.go hswaw/oodviewer: init 2021-03-07 16:57:02 +01:00
main.go hswaw/oodviewer: init 2021-03-07 16:57:02 +01:00
prod.jsonnet *: post-certmanager manifests update 2023-06-19 21:20:44 +00:00
views.go hswaw/oodviewer: fix links from index 2021-03-16 20:35:32 +00:00

README.md

Oodviewer

Spartan web interface for the term database of our IRC bot (ood/oof/klacz).

Go rewrite of a shitty old Python script that q3k wrote and hosted on his own infra. Now productionized!

Building and Running

bazel build //hswaw/oodviewer
bazel run //hswaw/oodviewer -- -postgres 'postgres://ood:password@host/ood'

Production deployment

Runs on k0, connects to ood's database on boston. Serves from https://oodviewer.q3k.me/.

To deploy:

bazel run //hswaw/oodviewer:push
# update //hswaw/oodviewer/prod.jsonnet with new image name
kubecfg update prod.jsonnet

Development

Beg and borrow ood admins for psql credentials. Keep in mind that you will not be able to access the production database over the Internet - either develop on Boston or run a port forward over SSH.