These are chat archives for reactioncommerce/reaction

24th
Mar 2017
Willy Aguirre
@marti1125
Mar 24 2017 04:44
Hello guys!
Brent Hoover
@zenweasel
Mar 24 2017 04:44
Hello
Willy Aguirre
@marti1125
Mar 24 2017 04:44
I have a problem start the project
Brent Hoover
@zenweasel
Mar 24 2017 04:45
Ok, what’s the problem?
Brent Hoover
@zenweasel
Mar 24 2017 04:46
Yeah, you are on OS X? You will need to increase your open file limit.
Willy Aguirre
@marti1125
Mar 24 2017 04:47
os yep is
OS X
Brent Hoover
@zenweasel
Mar 24 2017 04:48
I think that SO question covers it pretty well for the different versions
Willy Aguirre
@marti1125
Mar 24 2017 04:49
thanks a lot :D
Brent Hoover
@zenweasel
Mar 24 2017 04:49
:+1:
Willy Aguirre
@marti1125
Mar 24 2017 05:18
http://blog.mact.me/2014/10/22/yosemite-upgrade-changes-open-file-limit I can not change it, If anyone have the same problem?
l0qii
@l0qii
Mar 24 2017 17:54
if I'm maintaining my plugin as a separate project from reaction, is there a way to install that plugin into a docker container at deploy time? I'm trying to avoid cloning all of reaction locally and creating a custom build image manually.
Jeremy Shimko
@jshimko
Mar 24 2017 18:11
No, there’s no avoiding creating a custom build. Deploy time and build time are 2 separate steps. You can’t/shouldn't do an additional install step at deploy time. However, there’s no reason you can’t automate that custom build.
l0qii
@l0qii
Mar 24 2017 18:16
ok, so I shouldn't be doing that anyway. Thanks. I know there are ways to automate builds, I'll probably set that up once I'm further along
Jeremy Shimko
@jshimko
Mar 24 2017 18:47
All you really need is to have your plugin installed in Reaction and then run
reaction build your-docker-user/reaction:latest
and that’s the only part you’d have to automate. clone your plugin into Reaction plugins folder, run the build command, deploy image