Releases: backstrokeapp/server
v2.3.0: Separate operation dispatcher service
Previously, this service handled dispatching of automatic link operations. Now, I've created a new job to do that, which means that the server service should horizontally scale.
New infrastructure diagram:
Also, this pull request adds the other end of the logic required to connect link operations back to their founding link. All this change is doing is reading data from redis that the first part of the migration, a worker change, added there. Here was the first part of the migration: backstrokeapp/worker#3
v2.2.0: Return more information in the checkRepo route
This release adds a small change to the checkRepo route - it now returns details about the parent repository if one exists. We can use this on the frontend to properly assert that a fork is actually the fork of an upstream and not just a fork of something.
v2.1.0: Add mixpanel analytics
To attempt to get a more thorough understanding of traffic within Backstroke, I'm adding mixpanel analytics. The only thing that is currently being tracked is when a user makes a request to any authenticated api route, and the only pieces of data being logged are the route's url and the user details that are associated with that request.
v2.0.1: Deployment Hotfix
There turned out to be a small issue when deploying v2.0.0 - automatic link updates were a bit broken. This was due to three things:
- The heuristic that's used as a first pass prior to making an api call for each link wasn't working. I switched to a more specific regular expression which works much better now.
- One Github API call being made wasn't being passed the proper api token.
- That same api call was being passed a token in a non-standard way which meant that the call wasn't respecting the token, and instead falling back on the unauthenticated request.
Now, automatic link updates seem to be working well for the time being.
v2: Big, Scary Deployment
See #66 for details.