Mirror of https://github.com/ssbc/go-ssb-room/ to add Docker image builds with Drone
Go to file
Henry e62d6c06fb web/tempalates: add missing closing a tag to base 2021-02-09 16:11:48 +01:00
.builds typo.. 2021-01-27 11:50:17 +01:00
admindb add missing license headers 2021-02-09 12:53:33 +01:00
cmd add missing license headers 2021-02-09 12:53:33 +01:00
handlers add missing license headers 2021-02-09 12:53:33 +01:00
internal add missing license headers 2021-02-09 12:53:33 +01:00
roomsrv add missing license headers 2021-02-09 12:53:33 +01:00
test add missing license headers 2021-02-09 12:53:33 +01:00
web web/tempalates: add missing closing a tag to base 2021-02-09 16:11:48 +01:00
README.md add insert-user steps to README 2021-02-09 13:02:51 +01:00
errors.go room sever skeleton 2021-01-25 13:50:51 +01:00
go.mod cleanup go.mod and pin new http/auth version 2021-02-09 13:27:11 +01:00
go.sum use new auth.SetErrorHandler option 2021-02-09 13:40:57 +01:00

README.md

Go-SSB Rooms

This repository contains code for a Secure-Scuttlebutt Room v2 server writen in Go.

It not only includes the secret-handshake+boxstream setup and muxrpc handlers for tunneling connections but also a fully embedded http/html interface for administering the room.

Features

  • Rooms v1 (tunnel.connect, tunnel.endpoints, etc.)
  • Sign-in with SSB
  • Simple allow-listing Currently via .ssb-go-rooms/authorized_keys. To be replaced with a authorization list on the dashboard.
  • Alias managment

Development

The basics just need a recent version of Go. v1.14 and onward should be sufficient.

To build the server and see a list of it's options, run the following:

$ cd cmd/server
$ go build
$ ./server -h
Usage of ./server:
  -dbg string
    	listen addr for metrics and pprof HTTP server (default "localhost:6078")
  -lishttp string
    	address to listen on for HTTP requests (default ":3000")
  -lismux string
    	address to listen on for secret-handshake+muxrpc (default ":8008")
  -nounixsock
    	disable the UNIX socket RPC interface
  -logs string
    	where to write debug output to (default is just stderr)
  -repo string
    	where to put the log and indexes (default "/home/cryptix/.ssb-go-room")
  -shscap string
    	secret-handshake app-key (or capability) (default "1KHLiKZvAvjbY1ziZEHMXawbCEIM6qwjCDm3VYRan/s=")
  -version
    	print version number and build date

If you are working on the html templates or assets for them, build the server with go build -tags dev. This way it won't use the assets that are embedded in the binary but read them directly from the local filesystem.

Once you are done with your changes run go generate in package web to update them.

Tooling

mocks

counterfeiter enables generating mocks for defined interfaces. To update them run go generate in package admindb.

TODO: automate setup of tool

No ORM

We use sqlboiler to generate type-safe Go code code directly from SQL statements and table definitions. This approach suits the programming language much more then classical ORM approaches, which usually rely havily on reflection for (un)packing structs.

To generate them run the following commands. This will populate admindb/sqlite/models:

cd admindb/sqlite
rm generate.db
sqlite3 generate.db < schema-v1.sql
sqlboiler sqlite3 --wipe

The generated package admindb/sqlite/models is then used to implemente the custom logic of the different services in admindb/sqlite

TODO: automate this with go generate

TODO: we still need to incorporate automatic migrations. Until then use this workaround before starting the server: mkdir $HOME/.ssb-go-room; sqlite3 $HOME/.ssb-go-room/roomdb < $src/admindb/sqlite/schema-v1.sql.

Aside: I would have used sqlc since it's a bit more minimal and uses hand written SQL queries instead of generic query builders but it currently doesn't support sqlite.

Development user creation

cmd/insert-user contains code to create a fallback user. Build it and point it too your database with a username, like so:

cd $src/cmd/insert-user
go build
./insert-user $HOME/.ssb-go-room/roomdb my-user

Then repeat your password twice and you are all set for development.

Testing

Rooms

The folder tests/nodejs contains tests against the JavaScript implementation. To run them, install node and npm and run the following:

cd tests/nodejs
npm ci
go test

Web Dashboard

The folders web/handlers contain the HTTP handlers for the dashboard. Each subfolder comes with unit tests for the specific area (like auth, news, etc.). Simply run go test in one of them or run go test ./web/... in the root of the repo to test them all.

Authors

  • cryptix (@p13zSAiOpguI9nsawkGijsnMfWmFd5rlUNpzekEE+vI=.ed25519)

License

MIT