nickmerwin
Please follow the status page (https://status.coveralls.io) for updates.
Thank you for your patience here. We'll be back soon.
As for a % badge, you can use our new Coveralls GitHub Action to post your coverage data to https://coveralls.io, then add the badge to your readme:
https://github.com/marketplace/actions/coveralls-github-acti...
But I'd say the real value is in not needing to support an additional deployment platform -- their Docker based approach is like Heroku for on-prem, it abstracts the infrastructure details and just works.
Around a month ago the source file table on Coveralls.io[0] hit a transaction wraparound, and put us in read-only mode for over 24 hours while RDS engineers performed a full vacuum (that's not something that can be done manually as a customer). On a managed database I'm paying thousands a month for, I was hoping there would be some sort of early warning system. Well, apparently there is, but it's buried in the logs, and won't trigger any app exceptions so went un-noticed.
What's worse is there's 0 indication of how long a vacuum is going to take, nor progress updates while it's going. So for a production web app with customers, this means damage control language like:
"Our engineers have identified a database performance issue and working to mitigate. Unfortunately we do not have an ETA at this time."
About a week later, more calamity hit: the INT "id" field on the same table exceeded the max length. My first thought was change it to a BIGINT, but after ~4 hrs into the migration without any indication of how much longer it would take, I pulled the plug and sharded the table instead.
Moral of the story is that web devs should be aware of these pitfalls, and that no matter how much trust you put into a managed database service, it still could happen to you (queue ominous background music).
Anyway I'm glad to see this lurking monster in our beloved database tamed, thank you Mr Haas!
I'd recommend checking them out too since they're Docker based and have a significant roster: Travis, NPM, Code Climate, etc.
[0]: https://www.youtube.com/watch?v=V6e_A9VzPy8
CircleCI and Semaphore now supported by Coveralls.io - coverage stats and badges
Show HN: NPR.io - minimal NPR player built in CoffeeScript/Jekyll
It's a Jekyll app mostly written in CoffeeScript, deployed to S3 with CloudFront CDN'ing.
Here's a lengthier introduction for anyone interested: http://nickmerwin.com/2012/02/25/npr-io/
Show HN: Coveralls.io - track code coverage over time and badge your repo
You can see an example here:
Enter "yickster", then passphrase "hackernews"
We developed the application to work transparently with git to update the entire company as to what individuals are working on without the communication overhead of having to actually send someone a status update; now we all just "sup" each other.
Review my app: utsup.com, simple team awareness for projects that use git
http://www.google.com/insights/search/#cat=31&q=django%2...
I always wondered why Python consistently ranks higher than Ruby outside of the webapp sphere. Could it be the scientific/academic community's interest in Python's superior number crunching?
http://extjs.com/blog/2008/02/24/tasks2/
pretty sexy stuff!
Knowing how to wield a library like Prototype or JQuery will increase your javascript speed and efficiency 10 fold!