-
Notifications
You must be signed in to change notification settings - Fork 62
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.
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
Revive Hits - Better (Much Faster!) than Ever #50
Conversation
Codecov Report
@@ Coverage Diff @@
## master #50 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 1 8 +7
Lines 19 105 +86
=====================================
+ Hits 19 105 +86
Continue to review full report at Codecov.
|
@iteles no "rush" to Merge this, but would be good at |
@nelsonic I just didn't know whether it was ready for merging 😊 |
Added basic UI for creating Badges on the Homepage: http://hits.dwyl.io |
@iteles PR assigned. thanks for reviewing/merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look at all this!
And with a badge-maker! 🎉
@iteles thank you! ❤️ |
@iteles this PR dusts off the "Hits" project so that we can use it as a "beginners" node.js tutorial.
Issues resolved:
Fix/Revive the "Hits" project fixes Hit Count not working repo-badges#27 and is hit count working? repo-badges#24
Deploy to "better" (faster/cheaper) hosting service Deployment? #37
Created service: http://hits.dwyl.io / http://hits.dwyl.com (MVP) add hits as a dwyl service available to everyone at hits.dwyl.io ? #22 to avoid the (slow) Heroku startup time.
Remove use of shields.io "proxy badge" relying on shields.io is costing us ... we need to re-consider this... #30 which was super slow! instead use our own SVG template. ✅
fixes: Update dependencies #41 (update dependencies), Browser Language? #43 (record browser language), Simplify /lib/hits.js to do only *one* thing #44 (simplify code!), Format hit data to user friendly format #45 (format data in a user-friendly way in browser), Better Error Logging/Reporting #47 (error logging on server when something goes wrong!).
Using the "curl" response time command https://stackoverflow.com/a/22625150/1148249
we see that response is consistently around 300ms on my crappy 3G connection in PT!
This will form part of the next dwyl "learn" tutorial.
But right now I just want to ship the progress "so far".