Interesting picture – couple of posts on discussions servers are very much visible on audioserve popularity (number of stars on github project):
First jump is my post on reddit, second is this post on Hacker News.
Wondering how you project is doing on github and stars and growing over the time? I was (for my favorite project audioserve) so I created ipython notebook for to analyze trend on the time, which some predictions (which are now called AI – even linear regression is now called AI :-).
Continue reading Analyzing Project Popularity on GithubRecently I released new version of audioserve v0.16.5, which brings some interesting changes. I think I’ve described them in previous article and for sure they are also described in README. This release was focused on two major themes – performance and API. Concerning API – I’ve created small funny page using WebAmp audio player (Web recreation of famous WinAmp). It’s just for demo how audioserve API can be easily used, not everything works reasonably as WinAmp was focused on music. I have been using WinAmp some 20+ years back, at dawn of the past century, so I could not resist to play with it when I saw it.
Continue reading Audioserve release and some retro funI’ve used free account on Heroku to load there audioserve live demo (with few of my favorite audio books from librivox). It’s fairly easy to implement a docker image on Heroku (just needed to assure that it uses PORT env. variable to bind HTTP listener to this port and to assure that container can run under arbitrary non-root user). See links below if you want to test. Continue reading Audioserve demo on Heroku
As part of audioserve project I decided to create an Android client. To make this exercise more interesting I decided to write it in Kotlin language (see previous article about Kotlin language). This client should provide roughly similar interface as web client (see this article for web client interface demo), but I hoped to achieve much better caching features, which will enable to play smoothly even when connectivity is temporarily lost ( for half an hour, an hour) and possibility to download and play audiobooks completely offline. Further in this article I’d like to share my experiences with Android development, as beginner in this area. And spoiler is I do not like it. Continue reading Stupidly Complex or Completely Stupid – Android Development
MyBookshelf2 – ebooks management and sharing solution moved to next version – Beta 2 – apart of few small fixes, the main change is an internal revamp to make it compatible with latest Asexor and thus removing dependence on Crossbar.io and Autobahn library. It makes deployment of MyBookshelf2 easier and removes components that did not add much value to the solution, just made it bit overcomplicated. Some effort was given to provide easy implementation in Docker – now there is a script that will guide you through two pre-configured scenarios – development (local code, monitoring of code changes) and stage (code in a volume, JS client built and packed, app server running behind nginx proxy with SSL termination, nginx serving static content).
Check latest code on github. To give it a try just clone repo and run init.sh script in deploy directory (assuming you have Docker installed).