-
-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate reporting tools for GitHub into the platform #8
Comments
Is this the repository for the dashboard? |
Yes - that's correct. |
How do I get a Github token for this? |
I was looking at the repository very closely and had a couple of thoughts. It'd be a really big problem without some sort of caching system in place and I'm not sure if my first thought would be to check the website with all the documentation on it for a list of GitHub PRs. Granted it could go along with the leaderboard idea. |
I've had a lot of time to think about this issue. The question I have is how are we going to integrate the server portion into the website. I see something for React. I understand this part fairly well. https://docs.astro.build/en/guides/migrate-to-astro/from-create-react-app/ I need more training when it comes to integrating an ExpressJS server for the server portion of the dashboard. https://docs.astro.build/en/guides/integrations-guide/node/#middleware |
That is a good question. Let me share some context to help you move forward. So, at the minute we build this codebase as a "static" website. The pages and assets (HTML, client-side JS, CSS, images) are generated as part of the "build" process, which Astro takes care as a framework. For deployments, that leaves us with many options, we could take these built assets and put it on some hosting and point the domain at it. The key is the hosting, we use Cloudflare Pages, but it could also be GitHub Pages, or even a plain old virtual machine with some other web server that "serves" a directory. Now, circling back to your question. If we move from "static" site to a "dynamic" site, where we have APIs, or other server side needs - good news is we can still use Astro, following their docs. For the hosting we will simply move from Cloudflare Pages to something else. For example we could use Docker and provision a container running somewhere, like our main platform. |
Meld the
tools.freecodecamp.org
functionality into the contribute platformThe text was updated successfully, but these errors were encountered: