You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there, after looking at this project a bit I realized it's static, correct?
Was curious if you had an idea of how often this should be built to keep up with a project?
I see that https://expressjs.github.io/statusboard/ hasn't been built in something like 4 months, making some of the information out of date. Meaning I clicked through a couple "help wanted" issues which were already closed. (obviously that wasn't so much on purpose but just because this is a WIP)
After thinking about it I realized I don't know how often I'd expect this type of project to be rebuilt.
My first instinct was maybe it should be dynamic then, to keep up to date. But that gets into rate limiting on the GH api, as well as auth'd API calls for non-public projects.
I am likely just overthinking this, a new build on each issue open/close or label change might not be a huge deal. But it does seem inefficient.
I think efficiency talk is a bit too early of optimization here and instead a better question would be:
what level of detail and up to date-ness should this type of project aspire to?
What do you have in mind as the role this could serve for projects like express or others? I've found it useful already for express, where it was up to date.
Edit: Ahh I see now it's not exactly static! I need to dig into the code more I suppose, I just noticed there are requests happening to a json file to get the data. Updating those json files would definitely be more lightweight than doing a full build.
The text was updated successfully, but these errors were encountered:
Hey! I am on vacation and only am able to post on my phone at the moment, but I wanted to make a quick response with a few small answers:
The Express one uses a github action to build. I turned it off because actions were in beta and it was hitting a timeout. It was configured to rebuild every 2 hours, but I think mostly you only need to every day
There are many perf issues I would like to resolve here!
It is static files, but the ui doesn’t bundle the whole data, it requests it on render
I will be back in January and hope to start with some updates, but in the mean time I would love input and collaborators on this! I will try to watch and get back to you, but just might not be able to do serious work until then. Hope that helps.
Hey there, after looking at this project a bit I realized it's static, correct?
Was curious if you had an idea of how often this should be built to keep up with a project?
I see that https://expressjs.github.io/statusboard/ hasn't been built in something like 4 months, making some of the information out of date. Meaning I clicked through a couple "help wanted" issues which were already closed. (obviously that wasn't so much on purpose but just because this is a WIP)
After thinking about it I realized I don't know how often I'd expect this type of project to be rebuilt.
My first instinct was maybe it should be dynamic then, to keep up to date. But that gets into rate limiting on the GH api, as well as auth'd API calls for non-public projects.
I am likely just overthinking this, a new build on each issue open/close or label change might not be a huge deal. But it does seem inefficient.
I think efficiency talk is a bit too early of optimization here and instead a better question would be:
what level of detail and up to date-ness should this type of project aspire to?
What do you have in mind as the role this could serve for projects like express or others? I've found it useful already for express, where it was up to date.
Edit: Ahh I see now it's not exactly static! I need to dig into the code more I suppose, I just noticed there are requests happening to a json file to get the data. Updating those json files would definitely be more lightweight than doing a full build.
The text was updated successfully, but these errors were encountered: