Closed linktoming closed 2 years ago
Runing docker-compose run web rake spree_sample:load
then docker-compose up
didn't help.
The API server is running though, the following command returned API response.
curl --request GET \
--url http://localhost:3000/api/v2/storefront/products \
--header 'Content-Type: application/json'
Run docker-compose run web rake db:create
Run
docker-compose run web rake db:create
Thanks, the output of this command said the DB exists and the problem remains. I suspect it's something related to frontend, as API server could return the response as expected.
mingming@qihans-mbp popinventory2 % docker-compose run web rake db:create
Starting popinventory2_postgres_1 ... done
Starting popinventory2_redis_1 ... done
Creating popinventory2_web_run ... done
[Scout] [08/31/21 00:58:00 +0000 cad8ad8c0444 (1)] INFO : Couldn't find configuration in /app/config/scout_apm.yml for environment: development. Configuration in ENV will still be applied.
Database 'spree_starter_development' already exists
Database 'spree_starter_test' already exists
Running rake assets:precompile
got the *** stack smashing detected ***: terminated
error.
mingming@qihans-mbp popinventory2 % docker-compose run web rake assets:precompile
Creating popinventory2_web_run ... done
*** stack smashing detected ***: terminated
ERROR: 133
Application is up and working, that's a standard message for on the homepage.
Application is up and working, that's a standard message for on the homepage.
I cannot see that standard message ever since. Only showed up once in my installation session seemingly randomly.
This could be a red herring - but it looks like maybe Cannot render console from 172.19.0.1! Allowed networks: 127.0.0.0/127.255.255.255, ::1
might be the problem? It seems at least possible there's some issue with the docker config and/or some allowlisting in the application.
This could be a red herring - but it looks like maybe
Cannot render console from 172.19.0.1! Allowed networks: 127.0.0.0/127.255.255.255, ::1
might be the problem? It seems at least possible there's some issue with the docker config and/or some allowlisting in the application.
Yes, adding the following to development.rb indeed helped.
config.web_console.whitelisted_ips = '172.18.0.1'
Also added the following to Gemfile but not sure it helped
# only needed for MacOS and Ruby 3.0
gem 'sassc', github: 'sass/sassc-ruby', branch: 'master'
Environment
Steps I did
bin/setup
as suggested with the following outputwhile the console will show the following output