bridgefoundry / bridgefoundry.github.io

web site for Bridge Foundry
http://bridgefoundry.org/
0 stars 27 forks source link

How do I use codespaces for this? #165

Open noelleshantler opened 1 year ago

noelleshantler commented 1 year ago

I made a fork and attempted to contribute using codespaces. I couldn't figure out how to modify the codespace to use the correct version of ruby. Does anyone know how to do this?

$ ruby --version
ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [x86_64-linux]

The project requires 2.6.3 And my guess is this is why I get errors when I try to build the website.

ultrasaurus commented 1 year ago

I was pairing with @noelleshantler on this. Tried on my own fork and had same problem. Whether or not the ruby version is the root cause, am curious how to set up dev environment for a codespace. Any githubbers know how? maybe @mxie @kinseydurhamgrace ???

FYI: The full jekyll details:

jekyll 3.9.0 | Error:  no implicit conversion of Hash into Integer
/usr/local/rvm/gems/ruby-3.1.3/gems/pathutil-0.16.2/lib/pathutil.rb:502:in `read': no implicit conversion of Hash into Integer (TypeError)
        from /usr/local/rvm/gems/ruby-3.1.3/gems/pathutil-0.16.2/lib/pathutil.rb:502:in `read'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/utils/platforms.rb:75:in `proc_version'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/utils/platforms.rb:40:in `bash_on_windows?'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/commands/build.rb:77:in `watch'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/commands/build.rb:43:in `process'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/commands/serve.rb:93:in `block in start'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/commands/serve.rb:93:in `each'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/commands/serve.rb:93:in `start'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/lib/jekyll/commands/serve.rb:75:in `block (2 levels) in init_with_program'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        from /usr/local/rvm/gems/ruby-3.1.3/gems/jekyll-3.9.0/exe/jekyll:15:in `<top (required)>'
        from /usr/local/rvm/gems/ruby-3.1.3/bin/jekyll:25:in `load'
        from /usr/local/rvm/gems/ruby-3.1.3/bin/jekyll:25:in `<main>'
        from /usr/local/rvm/gems/ruby-3.1.3/bin/ruby_executable_hooks:22:in `eval'
        from /usr/local/rvm/gems/ruby-3.1.3/bin/ruby_executable_hooks:22:in `<main>'
mxie commented 1 year ago

I think we'd have to configure Codespaces to have the right environment set up for Jekyll development. Will look into this and keep you posted.

ultrasaurus commented 1 year ago

hmm, I assumed we could set that up in a fork... weird that it would need to be in the original repo, but maybe that's a good idea anyhow!