wp2txt
A command-line toolkit to extract text content and category data from Wikipedia dump files (by yohasebe)
nezekan
Rails security interfaces (by zarkiel)
wp2txt | nezekan | |
---|---|---|
1 | 1 | |
168 | 0 | |
- | - | |
2.5 | 10.0 | |
12 months ago | over 1 year ago | |
Ruby | Ruby | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wp2txt
Posts with mentions or reviews of wp2txt.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-10.
-
Day 11: CI for wp2txt Ruby project
After a while I found the wp2txt project. Adding GitHub Actions to this was quite simple though it was different from the previous one. Here is the pull-request and below you'll find a copy of the configuration file as I sent it.
nezekan
Posts with mentions or reviews of nezekan.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-10.
-
Day 11: CI for wp2txt Ruby project
First I looked at a project called nezekan. I tried to run the tests locally, but failed. I am not sure if I was even trying to run them as the authors intended, but this error seem to be genuine. It is a case-sensitivity issue. After I fixed that locally I bumped into and reported another issue.