These are chat archives for reactioncommerce/reaction

27th
Feb 2019
Slava Koshevoi
@slavakoshevoi
Feb 27 08:19
Can somebody help me? How I can subscribe for some specific document/collection and get reactive changes? For example, Order/s details.
Does reactivity working in reaction commerce ?
Loan Laux
@loan-laux
Feb 27 08:23
@machon As far as I know, the @reactioncommerce/reaction-components API isn't available in the Next.js starter-kit. That was on the legacy Meteor storefront with the plugin-oriented approach. Now you simply fork the starter-kit and modify whatever you want.
Karbal
@karbal
Feb 27 08:40
Hello @loan-laux
  • In the product collection the two tagIds and tags fields are missing
  • There is no possibility to delete a tag,
  • if you can add an interface for editers the tags and add in addition 3 fields Count of products with the filters (isVisibile, ...), as well as an icon and a thumbnail.
    Thanks
Loan Laux
@loan-laux
Feb 27 08:41
Well, what can I do about it? @karbal
Karbal
@karbal
Feb 27 08:44

I think to add these improvements but as soon as I am going to make an update of your solution I will lose these modifications.

there is no way to add these three fields for tags and still keep basic operation
thanks
@loan-laux

Loan Laux
@loan-laux
Feb 27 08:45
An update of my solution? What do you mean?
Karbal
@karbal
Feb 27 08:48
I mean reactioncommerce solution
it may be that after trade reaction decided to change on tags operation, and like that, it may be that i lose the changes that i made at the tags level
Loan Laux
@loan-laux
Feb 27 08:49
I'm not a core developer, I don't work for Reaction Commerce. Now about your tag issue, are you talking about the migration from tags to navigation trees?
Karbal
@karbal
Feb 27 09:08
I have proposals to improve the reactioncommerce solution and I would like to collaborate with the reaction reaction developers in order to apply these improvements and now can you advise me to whom to address to speak in detail about this?
Janus Reith
@janus-reith
Feb 27 09:10
Depends
Loan Laux
@loan-laux
Feb 27 09:11
For bugs, you can file issues on the starter-kit or backend repo, and then make a PR. For feature requests, there's this repo but it isn't very active: https://github.com/reactioncommerce/reaction-feature-requests/issues
Loan Laux
@loan-laux
Feb 27 09:11
Ha, @janus-reith was faster than me, as usual
Janus Reith
@janus-reith
Feb 27 09:11
:D
But you're right, missed the next-starterkit
Loan Laux
@loan-laux
Feb 27 09:13
I mean let's be honest the Feature Request repo isn't at the top of their priorities right now due to the huge shift in technology that they're undergoing. They have limited resources and a lot going on, so I personally understand that these aren't given the priority. @karbal, if you want to introduce a brand new feature, I'd say talk about it with the core devs on here, and submit a PR if they approve your idea.
Bradley
@bradlead
Feb 27 15:20
Are there any do's/don't that may have changed when it comes to deployment of the reaction-next-starterkit? Having difficulty deploying to both digital ocean and aws! I've been able to deploy a docker image but I can't get anything running away from local? Thinking maybe the docs are relating to deploying the meteor version? for ref: https://docs.reactioncommerce.com/docs/deploying-reaction-using-docker
Philipp Laurim
@EdgarNigel
Feb 27 15:58
@bradlead correct me if I’m wrong but I think you need to deploy and run the whole of reaction(meteor backend etc.) in order to get the starterkit running
Eliot Hills
@elhil
Feb 27 17:09
@EdgarNigel glad I could help ☺️ btw you don’t necessarily need a class-based component, you can take props as an argument to a functional component
Bradley
@bradlead
Feb 27 17:25
@EdgarNigel cheers! That'll be it, thought it could run independently still getting used to docker
Loan Laux
@loan-laux
Feb 27 17:28
@bradlead If you want to run the whole Reaction ecosystem on your own DigitalOcean droplets (or any other VPS for that matter), you may want to look into Portainer and Docker Swarm. If running on AWS, ECS is the way to go. These basically handle deployment of all your Docker containers across different machines. ECS is particularily powerful in that sense since it can provision new EC2s when needed (and if you've enabled auto-scaling).
Bradley
@bradlead
Feb 27 17:32
@loan-laux The plan is to run on ECS I think, theres just so many options that come with aws it can be a bit confusing! Auto-scaling would be super useful once actually deployed
Loan Laux
@loan-laux
Feb 27 17:32
Awesome, ECS is my personal favorite! :+1:
Philipp Laurim
@EdgarNigel
Feb 27 19:28
@elhil you’re right. I’m new to react and kinda started to make class-based components a habit as I currently don’t see the need for function based ones. Not sure if that’s the right direction though ;)
@bradlead let me know if it worked ;)
Eliot Hills
@elhil
Feb 27 19:29
@EdgarNigel until recently it was, but in the future I think it’s recommended to use functional components with hooks, so it might be good to start using that in new code :)
but there’s no wrong answer tbh
Philipp Laurim
@EdgarNigel
Feb 27 19:40
@elhil good to know, thanks. hooks weren’t on my radar at all so far.
Bradley
@bradlead
Feb 27 20:44
@EdgarNigel Quick Q, because there isn't a Dockerfile in the root directory is it best to write one or to deploy reaction; starterkit and hydra onto separate containers within the same cluster?
machiko
@machikoyasuda
Feb 27 22:42
The latest develop branch comes with new scripts for running reaction with the native Node debugger. Here's how to run it: docker-compose run --rm --service-ports reaction yarn inspect-docker and then use Chrome's Node debugger as you would normally
Eliot Hills
@elhil
Feb 27 22:51
@machikoyasuda sorry if this is a stupid question but is that for the starterkit?