cp2004 / octopluginstats

Site tracking my OctoPrint plugin statistics over time.

Hey there 👋

Here are some of my featured projects:

• 🔦 WS281x LED Status

• 🔦 WLED Connection

• ✏️ Marlin EEPROM Editor

• ⚙️ OneDrive Backup

• ⬆️ OctoPrint Upgrade To Python 3

• 📈 Statistics of my plugins: OctoPluginStats

Recent releases 🔖

• ✨ OneDrive File Sync plugin
• Marlin EEPROM Editor 3.3.0
• Gcode Macro 1.3.0
• OneDrive Backup 1.0.1
• WS281x LED Status 0.8.0
• Virtual Printer Settings 2022.07.04
• WLED Connection plugin 0.2.0

Supporting my projects

Enjoyed using a plugin? You can support their development through GitHub Sponsors. Sponsor monthly, one-time and choose a custom amount. You can choose!

❤️ Sponsor

octopluginstats's Issues

Investigate using React, Material UI and ReCharts to create site

Fun project for sometime maybe?

Syncing changes with downstream forks

@Sebclem - this one is for you, since I noticed you were trying to sync changes. This is something I've thought about before, but not actually looked into.

I've just implemented some changes to simplify the way this works, so that anyone can hopefully develop the default branch and be able to PR or merge upstream changes (ie. from me) into their fork.

It goes like this:

• next branch - the site powered by Next.js, React, Material UI
• deploy branch - the branch containing the data, and the one deployed to Vercel. There's a way that Next.js can be deployed to GH pages, but I like Vercel since it was so easy & fast.

The next branch automatically merges to the deploy branch any commits, like a mirror. Then the 'update stats' action runs and commits against the deploy branch as well. The deploy branch is yours, and won't ever be merged anywhere else.

Changes, should you want to implement this:

• Pull upstream workflow changes
• Create a deploy branch
• Change the 'Production' branch in Vercel - I'm not sure if you have set this up or not, or if it is deployed there by default because it is a fork of mine. No idea 🤷‍♂️.
  

I think that is how it should work. Feel free to adjust if necessary.

Sort data by largest install count

The tracking data from https://data.octoprint.org/export used to be sorted, but it was also hitting the upper limits on queries.

When the query limit was fixed, the data was no longer sorted by install count for individual versions.

So I need to sort the data in the get_data.js script before saving it to the file.