Closed chcorbato closed 2 years ago
If I remember correctly, for some reason during development the hyperlinks go to the live website, therefore as the software page does not exist, it will give you a page not found. However, if you manually type in /software after the localhost:4000 URL, you will get the page I developed. Seeing as accepting the pull request would cause a kaslab/software page to exist, I figured while live the error resolves itself as the hyperlink now goes to an existing page
However, if you manually type in /software after the localhost:4000 URL, you will get the page I developed.
Somehow this was not working for me either. I just tested by switching the settings in the repo to use the software branch and then merged your Pull request.
I keep this issue open because it would be helpful if someone figures out how to properly test our website updates.
To test locally you should run the webpage with this command:
bundle exec jekyll serve
Instead of:
bundle exec jekyll liveserve
with this, the base url becomes localhost:4000
Trying to review Pull request #6 locally the behavior of the website is that hyperlinks refer to the github server, see screenshot:
I explored this error as a potential cause:
GitHub Metadata: No GitHub API authentication could be found. Some fields may be missing or have incorrect data.
I think I solved that error following part of these instructions: https://idratherbewriting.com/documentation-theme-jekyll/mydoc_install_jekyll_on_mac.html#githuberror Concretely, I added the token to my .bashrc (I could not do the other part with a file) However, the issue persists.have you tested locally @EGAlberts ? How do you do it?