Skip to content

fluent/fluent-logger-python should use its own account for travis-ci.org and coveralls.io #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 12, 2015
Merged

fluent/fluent-logger-python should use its own account for travis-ci.org and coveralls.io #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7ade638
coveralls/travis-ci settings should belong to fluent organization
yyuu Mar 12, 2015
50a1b20
Update .gitignore
yyuu Mar 12, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@
*.pyc
*.pyo
/*.egg-info
/.coverage
/.eggs
/.tox
/build
/dist
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# A Python structured logger for Fluentd

[![Build Status](https://travis-ci.org/EvaSDK/fluent-logger-python.svg?branch=master)](https://travis-ci.org/EvaSDK/fluent-logger-python)
[![Coverage Status](https://coveralls.io/repos/EvaSDK/fluent-logger-python/badge.png)](https://coveralls.io/r/EvaSDK/fluent-logger-python)
[![Build Status](https://travis-ci.org/fluent/fluent-logger-python.svg?branch=master)](https://travis-ci.org/fluent/fluent-logger-python)
[![Coverage Status](https://coveralls.io/repos/fluent/fluent-logger-python/badge.svg)](https://coveralls.io/r/fluent/fluent-logger-python)

Many web/mobile applications generate huge amount of event logs (c,f. login, logout, purchase, follow, etc). To analyze these event logs could be really valuable for improving the service. However, the challenge is collecting these logs easily and reliably.

Expand Down