search

publiclab / community-toolbox

Tools to understand and welcome people into a contributor community
https://code.publiclab.org
MIT License
142 stars 196 forks source link

Discussion on non-functional nature of website on local dev environment #442

Open waridrox opened 3 years ago

waridrox commented 3 years ago

Please describe the problem (or idea)

While testing the website for development, I ran into a problem where the data could not be fetched and displayed. This could possibly be due to some rate limit on the API that is fetching a lot of data on each reload if I'm not mistaken 🤔 or maybe this issue is specific to me.

The waiting time to restore the functionality is not great either and possibly takes longer than 10-15 mins. This is a great barrier for many to test the website locally in the first place.

Screenshot 2021-03-22 at 8 22 38 PM

We can have a discussion for the same for the possible solutions so that we can finally settle upon something meaningful that doesn't take a lot of time to restore.

Browser, version, and operating system

Chrome v89

welcome[bot] commented 3 years ago

Thanks for opening your first issue here! Please follow the issue template to help us help you 👍🎉😄 If you have screenshots to share demonstrating the issue, that's really helpful! 📸 You can make a gif too!

YogeshSharma01 commented 3 years ago

Hi, @waridrox this issue is fixed now.

441

Thanks

waridrox commented 3 years ago

Hi, @waridrox this issue is fixed now.

441

Hi @YogeshSharma01, in this issue, I'm not talking about the duplicate navbar that was fixed in the pr but the non-availability of the content regarding issues, contributors list etc due to rate limit on API or db in local dev environment. Do you face the same issue or do we have to put our GitHub API token in a .env file to make it work ? 😅

govindgoel commented 3 years ago

@waridrox No, you don't have to do that. Ideally, it fetches the data there is no issue. And if the API limit exceeds you should be able to fetch after some time.