bluzi

Horray! is an experimental micro-library that lets you treat objects as if they were arrays. Note that Horray! extends Object, which considers a bad practice, and therefore it is experimental and not recommended to be used in production.

Feel free to look at the sources: https://github.com/bluzi/jsonstore

Thanks, feel free to create a pull request.

Thanks for sharing! fyi: You can also run jsonstore on your own servers.

Not at all, it has nothing to do with Forter. It's my own personal project.

Thanks, appreciate it. :)

To make it clear:

- jsonstore.io is intended for small projects, mostly for the open-source community. It's not a datastore you can use to store all the logs of your company, and we do have quota limits.

- We do nothing with your data, it's secured and if you want to store sensitive data you may want to encrypt it.

- The idea of this project is to provide the open source community a easy solution for storing casual usage data/settings for their projects.

Just enter the website, copy your link, and start sending HTTP requests to store data.

GitHub: https://github.com/bluzi/jsonstore

lol, noted

Not sure what do you mean

That's an awesome idea, will be a feature for sure.

Thanks for the feedback, we're working on methods to prevent TravisBuddy from commenting if the PR is being rapidly updated or if its comments are not relevant for some reason. One idea is that if the PR has a special label TravisBuddy won't comment on it. Another one is to be able to communicate with TravisBuddy using comments, so when you're sick of it you could just comment: "@TravisBuddy stop", and it'll stop immediately. (Maybe even "@TravisBuddy clear" to remove the previous comments)

Yeah, Jenkins' tests view was one of the inspirations for TravisBuddy :)

Thanks, that's an awesome idea. :)

Thanks for the feedback, the website and any part of the brand is open-source, so if you feel like contributing, you may start a discussion on GitHub or make a PR :)

We have methods to handle big build logs, and we have a backlog full of ideas on how to improve the way we handle big logs.