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
Transfer website build to alternative infrastructure #13612
Comments
@zackbloom Not exactly, as I mention in the mail, it's deployed on Heroku ;) The build process was running on my server, then pushed to Heroku to serve the content. As this part is almost fully automatic already, unless something was broken, maybe it can be hosted directly inside Cloudflare's infra, just will need some revise on cdnjs/buildScript |
This is super helpful, thank you @PeterDaveHello. Just to clarify, that build step is still running on your personal machine? Has the hardware issue been resolved? |
@zackbloom It's not running currently, the problem hasn't been resolved yet, would really appreciate if Cloudflare can help this part, the hardware requirement is basically the same as the bot's server, let me know if I can help. Thanks. |
We can do that! cc @xtuc |
Could we move the website to GitHub pages? |
This comment has been minimized.
This comment has been minimized.
@zackbloom I am working on some website redesign and will tackle the build system. |
Regarding a website redesign, this is something I've been working toward for a while now. I've got a milestone set up on the website repo for everything I'd like to get resolved with the current site before we start redesigning it: https://github.com/cdnjs/new-website/milestone/1 Once that's done, we have a set of mocks for a new website design in the brand repo, which can be found here: https://github.com/cdnjs/brand/tree/master/website Alongside this, however, I do agree that we should definitely revisit the infra side of things with the site. Getting the build process and deployment process as simple as possible would be great, I have no visibility into what happens currently. The server-side scripting for the website could also do with an overhaul, the beginnings of which were outlined in this issue: cdnjs/new-website#175 |
@zackbloom on further investigation I don't have the resources to run the build. So will pass the infrastructure onto you guys. I will work on redesign and documentation updates though. |
bootstrap link is not updated, please update that too |
Has Cloudflare already decided to sponsor build server? |
Yes we will run the build server, 👍
…On Thu, Dec 19 2019 at 7:32 PM, < ***@***.*** > wrote:
Has Cloudflare already decided to sponsor build server?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
#13612?email_source=notifications&email_token=AAANQM3AY6FXXWZBFPS3JZ3QZQOEHA5CNFSM4JM2O6BKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHLSW7Y#issuecomment-567749503
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AAANQM3VAHYYURSMF3O3DNDQZQOEHANCNFSM4JM2O6BA
).
|
that's done |
Historically the cdnjs website has been built and deployed on the server of @PeterDaveHello. Unfortunately due to hardware issues on his machine that is not currently happening, meaning new projects will not appear in the search there. What does the community think is the best way to manage this going forward? @cdnjs/cloudflare would be happy to donate compute capacity and the SRE work to maintain it, if that's what the community decides. It may also be possible to use something like GitHub Actions to do the deploy?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: