There are a few tweaks prior to the 1.0.0 milestone of Meeseeker, but the main reason for marking it released is because I haven't had a lot of changes in a few months.
So far, Meeseeker has been pretty reliable for my production deployments. I have two primary tasks and some other smaller ones that haven't had any issues aside from occasional problems related to rate-limiting.
The most important instance I currently run is used to back steem-engine.rocks, and that has been the most reliable aspect of the project.
So I'm confidant in marking this project complete (for a change).
What Changed ...
Handle rate limiting d2b27e1
This will automatically retry requests after a short delay. This commit also addresses a bug in the docker image, which you can try out (see: related docs):
docker run inertia/meeseeker:latest
Activate Travis (continuous integration) a5c76fc
Now, each commit to the master branch will invoke the testing suite.
See: https://travis-ci.org/inertia186/meeseeker
To update your gem:
gem update meeseeker
Previous posts:
- Meeseeker Handling JSON-RPC Batch - 0.0.9
- Meeseeker Steem Engine Virtual Transaction Support - 0.0.8
- Meeseeker Mosly Minor Steem Engine Fixes - 0.0.7
- Meeseeker Steem Engine Support - 0.0.6
- Meeseeker Op Timestamps - 0.0.5
- Meeseeker Witness Schedule Pub/Sub - 0.0.4
- Meeseeker on Docker
- Meeseeker Update - 0.0.3pre1
- I'm Mr. Meeseeks! Look at me!