BitcoinDesign
Gemfile update
A few peeps have/had problems running the site locally. Mr. AI is telling me that this may be an issue with webrick and later versions of Ruby.
This update is based on recommendations by said Mr. AI. Let's test and see if these fixes help resolve the problems, and we can iterate as needed.
Check the preview <-- should look exactly the same as the live site
Deploy Preview for bitcoin-design-site ready!
| Name | Link |
|---|---|
| Latest commit | f0fb979117e8e4cb6ad7d47622798c9fbea1bbe7 |
| Latest deploy log | https://app.netlify.com/projects/bitcoin-design-site/deploys/687df1694227ac0008ea5c90 |
| Deploy Preview | https://deploy-preview-1187--bitcoin-design-site.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify project configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Great. Let's make sure we get some people to test this locally before we merge.
I tested this build on a windows system and it had two major errors:
- io-event -
fatal error: sys/wait.h: No such file or directory - wdm -
error: implicit declaration of function 'rb_thread_call_without_gvl'
Mr. AI told me to delete these two lines with the trade off not being able to run the link-checker locally (html-proofer) and not being able to detect file changes automatically (wdm).
gem "html-proofer"
gem "wdm", "~> 0.1.1"
After deleting these two lines the build ran as expected but with the trade offs mentioned above.
I asked Mr. AI for a better solution and it recommend to use wsl. wsl worked but I had to configure wsl.conf file for it to work.
I tested this build on a windows system and it had two major errors:
- io-event -
fatal error: sys/wait.h: No such file or directory- wdm -
error: implicit declaration of function 'rb_thread_call_without_gvl'Mr. AI told me to delete these two lines with the trade off not being able to run the link-checker locally (html-proofer) and not being able to detect file changes automatically (wdm).
gem "html-proofer"gem "wdm", "~> 0.1.1"After deleting these two lines the build ran as expected but with the trade offs mentioned above.
I asked Mr. AI for a better solution and it recommend to use wsl. wsl worked but I had to configure
wsl.conffile for it to work.
If modifying .wsl.conf is a better solution than losing the link checker and file change detection, should we recommend this as the default way for Windows users to run the design guide locally? Are there any known trade-offs with this .wsl.conf configuration approach?
I would say yes WSL is a better approach for local build in a windows machine. And the changes required in wsl.conf are to prevent WSL from automatically appending the windows PATH. This is a preventive measure as to when we run bundle install(or any other command) it doesn't try to access the windows PATH and throw a error.
We just need to add these two lines in the wsl.conf file:
[interop]
appendWindowsPath = false
Deploy Preview for bitcoin-design-site ready!
| Name | Link |
|---|---|
| Latest commit | 8527b142c4ee5244aac1e62ab24e57d37e1f399e |
| Latest deploy log | https://app.netlify.com/projects/bitcoin-design-site/deploys/68dbcb6c19ad140008d697d7 |
| Deploy Preview | https://deploy-preview-1187--bitcoin-design-site.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify project configuration.
Sorry, this PR has gone a bit stale. How about we try to wrap it up, and then create a new one for the wsl addition? If that's OK with you, could you maybe test updating and running your setup locally with this PR and see if it works?
I believe @rabbitholiness has sometimes problems running the site, is that right? If so, could you maybe give it a whirl?
Sorry, this PR has gone a bit stale. How about we try to wrap it up, and then create a new one for the wsl addition? If that's OK with you, could you maybe test updating and running your setup locally with this PR and see if it works?
I believe @rabbitholiness has sometimes problems running the site, is that right? If so, could you maybe give it a whirl?
Sounds good to me. I think a separate ticket to troubleshoot windows issues makes the most sense.