The proxy is written in idiomatic Go and uses standard tools. If you know Go, you'll be able to read the code and run the server.
Athens uses Go Modules for dependency management. You will need Go v1.11 or later to get started on Athens.
See our Contributing Guide for tips on how to submit a pull request when you are ready.
Athens is developed on Go 1.11+.
To point Athens to a different version of Go set the following environment variable:
GO_BINARY_PATH=go1.11.X
# or whichever binary you want to use with athens
If you're inside GOPATH, make sure GO111MODULE=on
, if you're outside GOPATH, then Go Modules are on by default.
The main package is inside cmd/proxy
and is run like any go project as follows:
cd cmd/proxy
go build
./proxy
After the server starts, you'll see some console output like:
Starting application at 127.0.0.1:3000
Athens relies on several services (i.e. databases, etc...) to function properly. We use Docker images to configure and run those services. However, Athens does not require any storage dependencies by default. The default storage is in memory, you can opt-in to using the fs
which would also require no dependencies. But if you'd like to test out Athens against a real storage backend (such as MongoDB, Minio, S3 etc), continue reading this section:
If you're not familiar with Docker, that's ok. We've tried to make it easy to get up and running:
- Download and install docker-compose (docker-compose is a tool for easily starting and stopping lots of services at once)
- Run
make dev
from the root of this repository
That's it! After the make dev
command is done, everything will be up and running and you can move
on to the next step.
If you want to stop everything at any time, run make down
.
Note that make dev
only runs the minimum amount of dependencies needed for things to work. If you'd like to run all the possible dependencies run make alldeps
or directly the services available in the docker-compose.yml
file. Keep in mind, though, that make alldeps
does not start up Athens, but only its dependencies.
There are two methods for running unit tests:
This method uses Docker Compose to set up and run all the unit tests completely inside Docker containers.
We highly recommend you use this approach to run unit tests on your local machine.
It's nice because:
- You don't have to set up anything in advance or clean anything up
- It's completely isolated
- All you need is to have Docker Compose installed
To run unit tests in this manner, use this command:
make test-unit-docker
This method uses Docker Compose to set up all the dependencies of the unit tests (databases, etc...), but runs the unit tests directly on your host, not in a Docker container. This is a nice approach because you can keep all the dependency services running at all times, and you can run the actual unit tests very quickly.
To run unit tests in this manner, first run this command to set up all the dependencies:
make alldeps
Then run this to execute the unit tests themselves:
make test-unit
And when you're done with unit tests and want to clean up all the dependencies, run this command:
make dev-teardown
End to end tests ensure that the Athens server behaves as expected from the go
CLI tool. These tests run exclusively inside Docker containers using Docker Compose, so you'll have to have those dependencies installed. To run the tests, execute this command:
make test-e2e-docker
This will create the e2e test containers, run the tests themselves, and then shut everything down.
To get started with developing the docs we provide a docker image, which runs Hugo to render the docs. Using the docker image, we mount the /docs
directory into the container. To get it up and running, from the project root run:
make docs
docker run -it --rm \
--name hugo-server \
-p 1313:1313 \
-v ${PWD}/docs:/src:cached \
gomods/hugo
Then open http://localhost:1313.
In our CI/CD pass, we use golint, so feel free to install and run it locally beforehand:
go get golang.org/x/lint/golint