These are chat archives for reactioncommerce/reaction

16th
Jan 2019
Isha Saran
@ishasaran
Jan 16 06:27
@here to create a product we have a meteor method in reaction but to have a no-meter service for the same it doesn't seem to be there out of the box. Is this something that one has to then build by themselves?
I know it isn't that difficult to replicate a no-meteor service for creating a product in the starterkit
But I am just making sure that I am not missing something out, because I searched for the same everywhere
Manny Laporte
@laportem
Jan 16 08:26
Does version 2.0 comes with PWA enabled out of the box or do we have to configure PWA ourselves. If so any, tips on how we go about doing this.
Anne
@voordev
Jan 16 10:03
hello everyone, i followed setup instructions but im unable to open localhost:3000 it gives a 404
all docker containers are fully loaded no errors on 'make start' firewall is off ( running osx latest) anyone could perhaps point me in the right direction why i can't open the admin ui?
Loan Laux
@loan-laux
Jan 16 10:06
@ishasaran For now, the legacy Meteor-served UI is used to administer Reaction Commerce websites (which includes managing inventory). As far as I'm aware, nothing is available yet for interacting with admin-level stuff through GraphQL. But it's just a matter of time, of course.
Anne
@voordev
Jan 16 10:07
it seems i have the same issues with installation as someone else recently and the docs are not correct? nothing runs on the ports that listed in the docs
Isha Saran
@ishasaran
Jan 16 10:08
Thank you for your feedback @loan-laux appreciate it
Loan Laux
@loan-laux
Jan 16 10:08
@laportem Version 2.0 doesn't come with PWA features out of the box, but adding them to the starter kit would be fairly easy, just as on any Next.js project. The only one that would require a bit of work would be push notifications, but other than that I'd say you're looking at maybe an hour worth of work.
@anton6 @ryansdwilson Hey guys, sorry about the late response, I've been away from Gitter for a bit. @ryansdwilson nailed the difference between a multi-shop setup and a full-fledged marketplace. Basically, a multi-shop setup would be pointing multiple different domains to a single Reaction setup and letting Reaction figure out which shop are users browsing based on the domain they landed with (with the help of the Shops collection of course). For example, this would enable you to run sites for totally different brands but administered by the same company.
@voordev What error are you running into?
Isha Saran
@ishasaran
Jan 16 10:12
@voordev if you could share a screenshot of the logs of docker container, that would be helpful
Anne
@voordev
Jan 16 10:13
@loan-laux I followed the install instructions but nothing runs on the specified ports i havent debugged it further
Loan Laux
@loan-laux
Jan 16 10:13
+1 @ishasaran, log output from your containers would be helpful @voordev
Anne
@voordev
Jan 16 10:13
i assumed port after make start localhost:3000 would provide the admin ui(?)
Loan Laux
@loan-laux
Jan 16 10:13
That's correct
First of all, have you allocated more RAM to Docker than the default setting?
Anne
@voordev
Jan 16 10:14
is there an easy way to spit out the logs for those containers? i havent used docker for ages
Loan Laux
@loan-laux
Jan 16 10:14
docker ps will give you a lit of the containers, and then run docker logs -f [container_id] for both the next-starterkit and the reaction backend
Anne
@voordev
Jan 16 10:14
memor is on 2gb currently (Default osx settings)
Loan Laux
@loan-laux
Jan 16 10:15
Okay, so that is most likely your problem. You need to increase that to at least 4GB or else you'll be limited.
Isha Saran
@ishasaran
Jan 16 10:15
@voordev
I would suggest going trying these out on each docker container for logs -- https://docs.docker.com/compose/reference/logs/
Loan Laux
@loan-laux
Jan 16 10:15
This is a well known issue, the default Docker memory setting is simply not enough for running all of the Reaction services at once
Isha Saran
@ishasaran
Jan 16 10:16
and yes as @loan-laux suggests for the memory issues which have been documented in https://docs.reactioncommerce.com/docs/troubleshooting-development#memory-errors-or-errors-about-meteor-rawlogs
Anne
@voordev
Jan 16 10:16
I understand perhaps a good idea for the docs , i have modified it and retry if fails post log
Loan Laux
@loan-laux
Jan 16 10:17
Pretty sure it's in the docs already, but most likely not visible enough as lots of people still can't figure out why their reaction-platform doesn't start up
Anne
@voordev
Jan 16 10:17
i did not get any errors on make start though stating memory issues they all went status 'done' strange. now reloading all
on 4gb it still fails will post the logs now
Loan Laux
@loan-laux
Jan 16 10:17
Yeah this is strange, usually you'd get memory heap errors. But let's try anyways.
Alright, let's see the logs then
Anne
@voordev
Jan 16 10:19
the log for next-starterkit states it runs on port 4000 so i tried opening port 4000 and it seems to compile pages now still waiting for it to load
Loan Laux
@loan-laux
Jan 16 10:20
Is the backend operational on 3000?
Usually that's the one that fails if something's wrong
Loan Laux
@loan-laux
Jan 16 10:22
reaction_reaction is still building the project :)
Anne
@voordev
Jan 16 10:24
loan that was not obvisous to me but it seems stale, how long should a build take then?
Loan Laux
@loan-laux
Jan 16 10:24
Here's the thing, Meteor has a really poorly optimized compiler that can take around 15~20 minutes to fully build Reaction's backend on some machines. Luckilly though, that's only on the first start-up. Wait with the backend's logs open and look for a line saying that it's now listening on localhost:3000
Anne
@voordev
Jan 16 10:25
ok thats very long did not knew, im on a fairly brand new macbook pro2018 highest spec
thank you Loan perhaps an good idea to add this to the installation instructions i think many new people without the meteor / js stack experience will be confused by this
Loan Laux
@loan-laux
Jan 16 10:26
That shouldn't take long, but still it takes considerably more than most web projects out there to build. Patience is key. :key:
I agree @voordev
Anne
@voordev
Jan 16 10:26
it now runs (Y) im very excited to testdrive it it seems you did amazing job on the ui/ux also
Isha Saran
@ishasaran
Jan 16 10:27
I second @loan-laux on that thought, yes we're altogether need to make this a better experience of ourselves and everyone, just need to be really really patient :) and congratulations! Keep in touch.
Loan Laux
@loan-laux
Jan 16 10:27
The Reaction team has always been pretty good at that, yep. One of the reasons why I loved RC at first sight haha.
Anyways congrats on getting it running and don't hesitate if you have any question! We'll try to help you as much as possible
Anne
@voordev
Jan 16 10:28
although its a bit memory heavy to run a simple e-commerce shop in regards to pricing for the hosting compared to more simple solutions. would you need the full stack or would it be possible to run it 'light'? sorry for these newbie questions
Loan Laux
@loan-laux
Jan 16 10:29
@voordev There's no such thing as a lightweight version, but keep in mind that a production build will obviously be a lot more easy on the RAM and CPU
Anne
@voordev
Jan 16 10:30
just a quick question where would i find the admin ui? i now browse the demo storefront im very interested in react/gatsby 'new stack' also looked at the meteor products so this is a great learning resource
what is actually the business model of the reaction company? since this is all opensource
enterprise version?
Loan Laux
@loan-laux
Jan 16 10:31
I'd say you could fit both the back-end and the front-end on a single small EC2 instance, but I wouldn't recommend it. My go-to architecture for site with little traffic would be a MongoDB replica set on MDB Atlas ($20/month for a basic one), an EC2 for the back-end + Hydra (let's say another $20/month) and an EC2 for the front-end (maybe $10/month for a lightweight one). Now if you want to scale things up, I would highly recommend just using AWS ECS and let it manage EC2s on your behalf with auto-scaling. But you get the idea of what a minimalistic architecture would look like.
@voordev Your customer-facing storefront is on port 4000 and your admin UI is on 3000 (that's the legacy storefront and it's now used for administration only)
Anne
@voordev
Jan 16 10:33
@loan clear writeup get the idea. port 3000 and 4000 both show the storefront no management ui
Loan Laux
@loan-laux
Jan 16 10:33
@voordev On their business model, they've published a blog post about this: https://blog.reactioncommerce.com/product-updates-how-does-reaction-make-money/
Isha Saran
@ishasaran
Jan 16 10:34
@voordev You have to login as an admin on 3000 meteor app, and then you should see an edit slider
that will make the admin panel visible
Loan Laux
@loan-laux
Jan 16 10:35
@voordev The legacy storefront on 3000 hasn't yet been fully converted to an admin-only interface, although that's coming and I believe there's a PR for that (along with a brand new, updated UI)
+1 @ishasaran, you have to log in using your admin credentials and the whole thing will turn into an admin interface
Anne
@voordev
Jan 16 10:36
where exactly should one login? there is only the email, pasword dropdown menu option in the header
since i did not had to give any admin credentials with the installation
Isha Saran
@ishasaran
Jan 16 10:36
yes and to that you need to enter credentials from the logs to 3000
Anne
@voordev
Jan 16 10:37
ah right i see it now :) thank ou
Isha Saran
@ishasaran
Jan 16 10:38
No problem, yes it's confusing on the first go. Try keeping an eye on the logs and another eye on their documentation, otherwise gitter, forum & blogs are great help! :)
Loan Laux
@loan-laux
Jan 16 10:40
@voordev One more thing, the new operator UI is available on RC8 of the 2.0 version. Check it out here: reactioncommerce/reaction#4896
Anne
@voordev
Jan 16 10:41
wow that looks beatefull im a backend developer swithing more to frontend but really like good design and ui
is there a way to test that ui by installing a non stable version somehow true docker? i shall rtfm on docker this week
Loan Laux
@loan-laux
Jan 16 10:44
Sure, simply cd to your reaction directory, change branches and let the container rebuild
It's linked to your host machine's filesystem so it's just like running a CLI tool on your native shell
You may need to stop and re-start the container though, because there most likely are changes in the package.json that you want yarn to pick up
Patrick Newell
@pnewell4_twitter
Jan 16 10:48
:wave: from the DC-area... nice to see all the chatter this morning!
Loan Laux
@loan-laux
Jan 16 10:48
:wave: @pnewell4_twitter
Abhishek
@thegtagamer
Jan 16 11:42
Guys has anyone worked with Apache Solr ??
Anne
@voordev
Jan 16 12:25
I have used it before Abhishek not in regard to reaction
Ali Avci
@aiavci
Jan 16 12:49
I'm really confused.
I am confused about the new Reaction Starter Kit and Reaction Platform. As a person starting from scratch, is it worthwhile to invest development time in the Meteor based Reaction app and deploy this to production? I'm worried about having to re-develop everything and going through a difficult migration process (Especially DB migration if one exists)
In other words, when should I switch from a reaction only project to the reaction platform project and is this switch goig to b
Going to be easy
Sorry for the typos
Loan Laux
@loan-laux
Jan 16 13:55
@aiavci If you're starting from scratch, just direct your efforts towards the Next.js storefront and Reaction 2.0. The legacy Meteor-served storefront is deprecated and you shouldn't use it in production.
Ali Avci
@aiavci
Jan 16 15:09
Thank you very much @loan-laux ! Is it safe to use the Next.js storefront in production?
Loan Laux
@loan-laux
Jan 16 15:10
As of now, yes. It is the recommended way of deploying and using Reaction Commerce. Updates are very frequent as well so you are sure that potentials bugs are fixed quickly.