that doesn't leave anything behind like in other directories?
either way I think it is working
well, based on what you said, we should be okay
Meteor is pretty good about keeping an app encapsulated in the one directory along with the
~/.meteor dir
db and everything is involved as well
when you run
./reaction everything is right there in the directory
except for stuff installed to
~/.meteor/
well that is depressing, it is still showing up blank
so you ran
meteor npm install?
then you run
./reaction and it seems to be ok?
and you visit http://{your-server}:3000 and it’s blank?
yes
what’s the URL?
I just went to my home directory and ran "mkdir random" and permission was denied
then you have some serious issues
drwxr-xr-x
is the home directory
shouldn't fixing that help?
well, it’s not good if you can’t create a directory in your home directory
I'm just not sure what I should do with chmod what is the standard for home? 777 is way to open right, so what would be ideal?
unfortunately it’s not that simple, because there may be config files etc that need to have different permission
I think 755 works as the default
If you chown to yourself and reset everything to 755 you should be most of the way there
well that isn't working even restored it to an early version and nothing
hi reactioncommerce is fully open source?
Yep
want to do a fresh pull from dev after 1.3 upgrade. are there any any special instructions/steps to follow?
No, just
meteor npm install
and
./reaction pull
is this the ecommerce app that use to meteor a few years ago?
:thumbsup: thanks
@watermelonjuice I doubt we are the only ecommerce app on Meteor, but we have been around for a couple years
or more
oh I was confusing with getfwd
so how does this differ from getfwd?
getfwd seems dead now? I first read about it on hacker news many years ago.
I have never heard of getfwd so I can’t answer that
I have Reaction setup except the localhost: 3000 is blank. What else am I missing?
https://reactioncommerce.com/features looks very promising
@dlabadini Are you running locally?
do you need me to make a pull request?
@watermelonjuice pardon?
@zenweasel Yes, locally on OSX
Did you do
meteor npm install?
@zenweasel Yep!
@zenweasel its a blank page linked from the readme file
@dlabadini That’s strange. Someone else was having the same problem this morning
@zenweasel I saw. What's the expected behavior? Any suggestions?
It should render the home page of the default site
@zenweasel I'd be happy to do a screen share if you want to poke around.
Ok
I just tried running it from a fresh install here and not seeing any issues
@zenweasel What's your Skype handle?
@dlabadini I will pm it to you
@zenweasel Sounds good.
@dlabadini, could you see, is there any console warnings in browser?
@thaicares I may know what your issue was/is. Devin was running into the same problem which appeared to be a conflict between the global npm and the local
@watermelonjuice Thanks for letting me know about the blank page. I don’t think we have a repo for our blog pages so I will just someone know
@erendira I have the same ideas with @aaronjudd where problem is. The structure is declared in register.js add new layout
corePageWorkflow, Try to update Shops.layout and make sure it's inside
From the sample data the shop id is a long code, but if I want to create my own shop, how can I create a shop id like that?
@newsiberian yes, thx.
I also encountered the error "bunyan-format/package.json module cannot be found". I solved it by updating this meteor package to 0.3.1
@brianxcli :clap:
would reaction commerce be useful for website doing bespoke tailoring?
or would it be recommend to build a custom website from scratch?
I'm adding some permissions to current users roles like this:
user.roles[shopId].push("accountSellerProducts"); // for access to our own products route
user.roles[shopId].push("accountSellerSellerorders"); // for access to our own orders route
Roles.addUsersToRoles(Meteor.userId(), "accountSellerProducts", shopId);
Meteor.users.update(Meteor.userId(),
{
"$set": {
isSeller: isSeller,
"profile.isDecided": true,
"roles": user.roles
}
}
);But they are not effective immediately. A full page refresh from the browser is needed. Why?
Should I do it differently?
When I had it in the ReactionCore.Hooks.Events.add( "onCreateUser", ...) it worked immediately.
@ScyDev probably needs the routing table refreshed, it checks permissions, and the onCreateUser probably occurs before the routing table is created.. (guessing here)
ReactionRouter.reload() might be a test of that
@watermelonjuice that’s all dependent on your requirements, needs, skills, etc. It could be used for that certainly, but will require customization. If you’re not afraid to build from scratch, then Reaction should be less work than that unless you have just the simplest of requirements.
I will be hiring a developer
I’m thinking the majority of your focus will be around the bespoke product / tailor creator then?
yes
I sometimes find that when using an existing platform for project with big customizations that it can cause more problems than it can solve
I think then it’s quite doable, you’d need to update the product page (or just create a different page) that is your custom creator product, so that’s the majority of the work. (without knowing specifics)
but schemas, order workflow,etc should all support this easily
@aaronjudd Tnx, but "ReactionRouter.reload()" doesn't help, unfortunately.
@zenweasel Ok so what is the problem between the global npm and the local?
@thaicares I was just working with someone else who had the same symptom (blank page). It was because (I suspect) they had run
npm install before they ran meteor npm install. I would try rm -rf’ing the directory again, reclone, and then try just meteor npm install then ./reaction
but that is what I went through with your help the other day...
There were no error messages during the
meteor npm install?
no I don't believe so
also I checked and home dir is the same as the previous time I was able to successfully get reaction up and running! So write for the user is not necessary
Yeah, I don’t think that meteor/reaction require write permissions out anywhere besides the directory and
./meteor
Ah, yes. The other thing you can try is
rm -rf’ing your ~./meteor directory and starting again
thanks @aaronjudd and @ramusus it's working now