getting this error
at the beging
*begining
i have the same issues with 3.x update failed: Access denied. No allow validators set on restricted collection for method 'update'. git@github.com:/reactioncommerce/reaction-admin.git,reaction-admin,v3.0.0-beta.5
running on windows
Hi everyone. I installed reaction platform using reaction-development-platform. I have all done and works well, but I can't to login admin dashboard. So my question is what's the default email and password of admin user or how can I create new? I tried admin@localhost and r3@cti0n
How I can debug it via VS Code for example
?
@HarisSpahijaPon
@nectar1 You’d have to do
make dev-link-reaction to use the docker-compose.dev.yml file instead of the production-like one. Then, make sure to stop the reaction_api container by running make stop-reaction. And finally, go into your reaction directory and start the API like this to enable the debugger: docker-compose run --rm --service-ports reaction yarn run inspect --service-ports.
Hi, I'm noob here, I trying to install reaction for testing but have an error :
Starting reaction-hydra_postgres_1 ... error
ERROR: for reaction-hydra_postgres_1 Cannot start service postgres: AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default214847281` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default214847281 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'
error: exit status 1
ERROR: for postgres Cannot start service postgres: AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default214847281` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default214847281 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'I have node v12.16 and docker v19. Any idea what's going on?
And I am under ubuntu 19.10 server
is there any deployment production deployment guide/setup for 3.0.0
It seems this deployment guide is outdated https://github.com/reactioncommerce/proxy-traefik/blob/master/docs/SimpleDeploymentGuide.md
It seems this deployment guide is outdated https://github.com/reactioncommerce/proxy-traefik/blob/master/docs/SimpleDeploymentGuide.md
In case this error is coming from the data-factory, when it imports "createFactoryForSchema"
@alefemafra I’m wondering if your
simpl-schema is at the right version… Can you try and reinstall your NPM packages?
@nectar1 Once you’ve done what I said, just connect whatever debugger you want (VS Code’s for example) to localhost:9229. It should work without any issue.
Thanks @loan-laux .
I'm still testing.
I have not been able to run the development platform on a remote server, even by modifying the .env files
I am trying to get it to work on my windows laptop, but I get this error message:
sam@DESKTOP-UC7SSM5:~/reaction-development-platform$ make
Error response from daemon: network with name reaction.localhost already exists
Removed docker.exe development symlink for reaction-hydra
Running pre-build hook script for reaction-hydra.
reaction-hydra post-project-start script invoked.
ERROR:
Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?
Supported filenames: docker-compose.yml, docker-compose.yaml
make: *** [Makefile:209: build-reaction-hydra] Error 1I'm trying to see why. The docker-compose.yml file exists. It is not easy I am not familiar with node and docker. I learn :)
just for information, I have installed node for windows and follow this tutorial for the docker installation and it works :
https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly
https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly
Hello. I'm following this guide https://github.com/reactioncommerce/proxy-traefik/blob/master/docs/SimpleDeploymentGuide.md and I have the example-storefront up and running. When I try to create an account, it just displays
Cannot GET /. I'm new to docker and reactioncommerce so I'm not entirely sure where the issue is but I believe it has something to do with hydra. Would someone be able to take a look at these logs from the hydra startup and confirm whether or not this issue is indeed with hydra?john@ubuntu-s-2vcpu-4gb-nyc3-01:~/reaction-platform/reaction-hydra$ docker-compose up
Starting reaction-hydra_postgres_1 ... done
Starting reaction-hydra_hydra-migrate_1 ... done
Starting reaction-hydra_hydra_1 ... done
Attaching to reaction-hydra_postgres_1, reaction-hydra_hydra-migrate_1, reaction-hydra_hydra_1
hydra-migrate_1 | Config file not found because "Config File ".hydra" Not Found in "[/]""
hydra-migrate_1 | time="2020-02-19T19:53:13Z" level=info msg="No tracer configured - skipping tracing setup"
hydra-migrate_1 | time="2020-02-19T19:53:13Z" level=info msg="Establishing connection with SQL database backend" dsn="postgres://*:*@postgres.reaction.localhost:5432/hydra?sslmode=disable"
hydra-migrate_1 | time="2020-02-19T19:53:13Z" level=info msg="Successfully connected to SQL database backend" dsn="postgres://*:*@postgres.reaction.localhost:5432/hydra?sslmode=disable"
hydra-migrate_1 | The following migration is planned:
hydra-migrate_1 |
hydra-migrate_1 | | DRIVER | MODULE | ID | # | QUERY |
hydra-migrate_1 | |--------|--------|----|---|----------------------|
hydra-migrate_1 | |--------|--------|----|---|----------------------|
hydra-migrate_1 | Successfully applied 0 SQL migrations!
postgres_1 | 2020-02-19 19:53:12.001 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_1 | 2020-02-19 19:53:12.001 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_1 | 2020-02-19 19:53:12.011 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2020-02-19 19:53:12.041 UTC [24] LOG: database system was shut down at 2020-02-19 19:51:49 UTC
postgres_1 | 2020-02-19 19:53:12.050 UTC [1] LOG: database system is ready to accept connections
reaction-hydra_hydra-migrate_1 exited with code 0
hydra_1 | Config file not found because "Config File ".hydra" Not Found in "[/]""
hydra_1 | time="2020-02-19T19:53:14Z" level=info msg="No tracer configured - skipping tracing setup"
hydra_1 | time="2020-02-19T19:53:14Z" level=info msg="Establishing connection with SQL database backend" dsn="postgres://*:*@postgres.reaction.localhost:5432/hydra?sslmode=disable"
hydra_1 | time="2020-02-19T19:53:14Z" level=info msg="Successfully connected to SQL database backend" dsn="postgres://*:*@postgres.reaction.localhost:5432/hydra?sslmode=disable"
hydra_1 | Thank you for using ORY Hydra v1.0.8+oryOS.12!
hydra_1 |
hydra_1 | Take security seriously and subscribe to the ORY Security Newsletter. Stay on top of new patches and security insights.
hydra_1 |
hydra_1 | >> Subscribe now: http://eepurl.com/di390P <<
hydra_1 | time="2020-02-19T19:53:14Z" level=info msg="Software quality assurance features are enabled. Learn more at: https://www.ory.sh/docs/ecosystem/sqa"
hydra_1 | time="2020-02-19T19:53:14Z" level=info msg="Setting up http server on :4445"
hydra_1 | time="2020-02-19T19:53:14Z" level=warning msg="HTTPS disabled. Never do this in production."
hydra_1 | time="2020-02-19T19:53:14Z" level=info msg="Setting up http server on :4444"
hydra_1 | time="2020-02-19T19:53:14Z" level=warning msg="HTTPS disabled. Never do this in production."
These are the hydra logs for when I click create account from the example-storefront:
hydra_1 | time="2020-02-19T19:54:35Z" level=info msg="started handling request" method=GET remote=173.54.55.65 request="/oauth2/auth?loginAction=signup&response_type=code&redirect_uri=https%3A%2F%2Fstorefront.patchamp-store.com%2Fcallback&scope=offline%20openid&state=xNuqnfxrB1FI9Xytuegj8reE&client_id=example-storefront"
hydra_1 | time="2020-02-19T19:54:35Z" level=info msg="completed handling request" measure#hydra/public: https://hydra.patchamp-store.com/.latency=12263330 method=GET remote=173.54.55.65 request="/oauth2/auth?loginAction=signup&response_type=code&redirect_uri=https%3A%2F%2Fstorefront.patchamp-store.com%2Fcallback&scope=offline%20openid&state=xNuqnfxrB1FI9Xytuegj8reE&client_id=example-storefront" status=302 text_status=Found took=12.26333ms
I was able to get it deployed on v3.0 by
- setting the appropriate environment variables on these pages: https://docs.reactioncommerce.com/docs/next/upgrading and https://docs.reactioncommerce.com/docs/next/environment-variables
- creating docker-compose.override.yml files for reaction-identity and reaction-admin
- adding the necessary A DNS records for admin and identity
i am using latest reaction-development-platform (trunk).
reaction-admin is beta5