What is this?
When I started it, this was my first sizeable piece of Go code (you can certainly tell that if you look at early commits!), so I was a baby gopher:
Can I use it?
Yes. But I can't promise it would be easy at this point. You should be able to build without problems, but installing and running will require reading some deployment code. You will need a physical server or a VPS to run it. I have only tried running it on Linux, but in theory it should run everywhere where Go runs.
Build instructions on Ubuntu 14.04 (older versions might differ a bit):
$ cat scripts/dev-packages.txt | xargs sudo apt-get install -y
- Note: make sure your $GOPATH and $GOBIN are set up (see the docs)
- Node JS (you will need to use http://nodejs.org/download/ or follow
instructions, it doesn't work with the one provided by the package manager)
- Note: make sure
node/bin/dir is in
PATH, build scripts assume that
- Note: make sure
$ npm install -g grunt-cli bower browserify
- Note: don't get surprised when make will take a lot of time and network activity on the first run, it's downloading dependencies.
go get github.com/steinbacher/goose/cmd/goose
You will need go-bindata to build embedded resources. Get it at:
go get -u github.com/go-bindata/go-bindata/...
Here is a useful quick start primer on how to configure postgres for the first time.
The server is meant to start and run without any configuration whatsoever. Currently that is not fully achieved, since the server requires at least a DB connection being configured. But it should at least start and serve the static content.
The sample-server.conf should suit your needs with few simple modifications. The server is looking for config in these locations, in this order:
All the files found will be read, in the order specified above, with options in more specific locations overriding the more generic ones. So if you happen to run a few instances, you can have global stuff configured in one place, leaving local tweaks for each instance.
BSD Simplified, see LICENSE.md.