7 ms·
I started with writing open source Ruby gem https://github.com/ArturT/knapsack https://github.com/ArturT/knapsack for running tests in parallel on CI and later
by ArturT 7y ago
I started with writing open source Ruby gem https://github.com/ArturT/knapsack https://github.com/ArturT/knapsack for running tests in parallel on CI and later I gave a talk on local meetup event for Ruby developers.
With time I wrote more blog posts https://docs.knapsackpro.com https://docs.knapsackpro.com and shared on Reddit, Twitter, LinkedIn profile or Ruby groups. From time to time posts landed in RubyWeekly newsletter.
Also asking users for recommendation might help.
I connected with each person on LinkedIn I talked to or who signed up and I followed them on Twitter. People who like your product can easily see you publish new content and can like or share it.
- komuW 7y agoknapsack[1] and knapsack_pro[2] are both under MIT license and seem to have the same code. How do you keep companies/people from using the pro without paying? 1. https://github.com/ArturT/knapsack https://github.com/ArturT/knapsack 2. https://github.com/KnapsackPro/knapsack_pro-ruby https://github.com/KnapsackPro/knapsack_pro-ruby
- pknerd 7y agoSupport may be?
- ArturT 7y agoknapsack_pro gem uses Knapsack Pro API which is paid. See more at https://knapsackpro.com https://knapsackpro.com It works similarly like tools for exceptions tracking, i.e https://www.honeybadger.io https://www.honeybadger.io is paid but has MIT client https://github.com/honeybadger-io/honeybadger-ruby https://github.com/honeybadger-io/honeybadger-ruby Other than that I do support paying customers.