-
Notifications
You must be signed in to change notification settings - Fork 16
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
Update dev instructions #72
Conversation
I cloned this branch and I still get this OpenSSL::Cipher::CipherError. portal_1 | Caused by: portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in require' portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in block in require_with_bootsnap_lfi'portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in register' portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in require_with_bootsnap_lfi'portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in require' portal_1 | /usr/local/bundle/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in require'portal_1 | /usr/local/bundle/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in block in require' portal_1 | /usr/local/bundle/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:in load_dependency'portal_1 | /usr/local/bundle/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in require' portal_1 | /usr/local/bundle/gems/railties-6.0.3.1/lib/rails/application.rb:339:in require_environment!'portal_1 | /usr/local/bundle/gems/railties-6.0.3.1/lib/rails/application.rb:523:in block in run_tasks_blocks' portal_1 | /usr/local/bundle/gems/sprockets-rails-3.2.1/lib/sprockets/rails/task.rb:62:in block (2 levels) in define'portal_1 | /usr/local/bundle/gems/railties-6.0.3.1/lib/rails/commands/rake/rake_command.rb:23:in block in perform' portal_1 | /usr/local/bundle/gems/railties-6.0.3.1/lib/rails/commands/rake/rake_command.rb:20:in perform'portal_1 | /usr/local/bundle/gems/railties-6.0.3.1/lib/rails/command.rb:48:in invoke' portal_1 | /usr/local/bundle/gems/railties-6.0.3.1/lib/rails/commands.rb:18:in 'portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in require' portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in block in require_with_bootsnap_lfi'portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in register' portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in require_with_bootsnap_lfi'portal_1 | /usr/local/bundle/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in require' portal_1 | /usr/local/bundle/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in block in require'portal_1 | /usr/local/bundle/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:in load_dependency' portal_1 | /usr/local/bundle/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in require'portal_1 | bin/rails:4:in `' portal_1 | Tasks: TOP => environment portal_1 | (See full trace by running task with --trace) portal_1 | rails aborted! |
Are you trying to run in a production environment or with docker-compose @TonyLeeVT? The changes and instructions in #73 may help with that. The error looks related to the rails credentials. |
I tested this with the following steps:
Works. |
03661b6
to
0a912da
Compare
Co-authored-by: Aaron Olson <934893+honkfestival@users.noreply.github.com>
The failing build is for an unrelated security vulnerability. Will fix that in another PR as soon as a new version of lodash is released. |
This updates the instructions for setting up your local dev environment to get the portal running.
I also added a sample file with local dev environment variables to make configuration a bit easier.
@jeffmaher and @TonyLeeVT can you try following these updated instructions and see if that resolves the issues you were seeing in #61 and #62?