There are a few minor differences between Device Analytics (our first target for production deployment) and Page Analytics. Resolving these will make future code maintenance easier.
- Device Analytics has a configuration/configuration.go file Page Analytics calls this file configuration/config.go. Note: kask and service-scaffold-golang both have a similar file in the root directory, by the name config.go. It seems that Device Analytics is the outlier here, probably when we introduced the "configuration" package. Was there a reason we went with "configuration" and not "config"? If we choose "configuration", we should consider (later, not now) pushing that change back up to the scaffolding level.
- The Device Analytics version of the configuration allows setting various things about the Cassandra connection (via a "cassandra" struct). We should add that to Page Analytics
- There are some other minor unnecessary differences between the files. It'd be good to diff them and make them as consistent as possible. That'll make it easier, if we're debugging something related to config that works in one service but not another. It'll also make it easier if we decide to extract config from the individual services and move it up to a higher level (aqsassist, servicelib, etc.).
- In similar fashion, there are minor unnecessary differences in not_found_handler.go