didenko/pald

pald's Issues

Keep records' sources in the registry

default | fixed | dynamic

Per service address lists

Decide if address lists should be associated with a registered service.

pald responses should not cache in browsers

Add example client code

Integrate with remote configuration stores for port assignments

The server does not persist the state

Choose a place to store configuration

Should persist the port to listen on, dynamic port range min/max, and port mappings state

Figure out what to do with service aliases in standard /etc/services file

Switch from GPLv3 to Apache 2.0 license

Output format

JSON or text/plain? JSON seems to be more flexible. In this case though the output would be great is processed by shell scripts as curl output, for which text/plain fits better.

Aware to actual ports in use

When allocating or fixing a port optionally test that the port is not in actual use on the system (platform-dependant)

Make REST API

Make the HTTP server to run the registry

Make pald friendly to daemon wrappers

pald should detach I/O and fork to background on startup.

Daemon verbs are broken

Specifically, sudo bin/pald status panics:

panic: Unsupported Config Type ""

goroutine 1 [running]:
main.init·1()
    /Users/vlad/Code/pald/src/github.com/didenko/pald/cmd/pald/pald.go:107 +0x353
main.init()
    /Users/vlad/Code/pald/src/github.com/didenko/pald/cmd/pald/pald.go:133 +0x6a

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
    /usr/local/go/src/runtime/asm_amd64.s:2232 +0x1

Truncate to dump file's size after writing

Instead of currently truncating to zero before writing

Dynamic port allocations only

Fixed port assignments are scope creep for now. They complicate unnecessarily and pull the mind to complexity swamp.