These are chat archives for reactioncommerce/reaction

11th
Sep 2015
Spencer Norman
@spencern
Sep 11 2015 05:43
:clap:
Aaron Judd
@aaronjudd
Sep 11 2015 05:56
sadly, it’s going to be a bit rough for a little bit… but that was one branch that was just out of control!
Mike Murray
@mikemurray
Sep 11 2015 05:57
yea.. It was supposed to be the accounts-ui rewrite. Then we went crazy
Aaron Judd
@aaronjudd
Sep 11 2015 05:59
:bomb: :boom: :bow:
Sara Hicks
@saralouhicks
Sep 11 2015 06:00
👏
Aaron Judd
@aaronjudd
Sep 11 2015 06:09
and we’re not even in the office to watch the light show!
Sara Hicks
@saralouhicks
Sep 11 2015 06:10
Ha! I thought the same thing!
Aaron Judd
@aaronjudd
Sep 11 2015 07:16
@spencern if you don’t use the bin/clone-packages.sh script, you should check it out. easiest way to get updates.. YMMV
Bogi
@boboci9
Sep 11 2015 13:05
Hi, I want to create a new theme package for my application, how can I stop the recreation of the reaction-core theme files in my client/themes/bootstrap folder? Because untill these are there my new style is overwritten
Tom De Caluwé
@tdecaluwe
Sep 11 2015 13:09
When using the latest commits from reaction and reaction-core, I get an ".admin-controls" panel rendered below the footer, mentioning "No controls for this view". Something wrong here?
Bogi
@boboci9
Sep 11 2015 13:57
Also when I add the `reactioncommerce:bootstrap-theme' I get
meteor add reactioncommerce:bootstrap-theme
 => Errors while adding packages:             

While loading plugin `theme-configurator` from package
`reactioncommerce:bootstrap-theme`:
packages/meteor/startup_server.js:2:1: __meteor_bootstrap__ is not defined
at Object.Meteor.startup (packages/meteor/startup_server.js:2:1)
at Package (packages/webapp/webapp_server.js:175:1)
at <runJavaScript-59>:818:4
at <runJavaScript-59>:829:3
Does anyone know what am I doing wrong?
Aaron Judd
@aaronjudd
Sep 11 2015 14:59
@boboci9 re: first question: you can edit the *.json files in the client/themese/bootstrap folder to enable/disable particular elements. also wherever those .json files are located is where the build will put the files. You don’t need to keep them there, or you could put your own in “client/themese/mytheme”. Re: error, not sure, that’s new to me... maybe needs nemo64:bootstrap as well?
Bogi
@boboci9
Sep 11 2015 15:02
I cloned the reactioncommerce:core-theme and I would like to have my own theme package instead of just overwriting the files in the client/themes/folder
but I'm not sure what to change in the bootstrap-theme to load mine, because I can't change anything because of the error
I tried with nemo64:bootstap but it says it has been already added and the error persists
Aaron Judd
@aaronjudd
Sep 11 2015 15:11
to do a completely new theme package (vs just your own less files for a theme) you’d need to create both a “my-bootstrap-theme” and a “my-theme”. The docs should cover both these cases. but essentially “bootstrap-theme” is the builder/loader of “core-theme” so it’s kind of a matched pair. (meteor limitations on preprocessing forced this structure).
the builder just looks for those .json files are and puts the compiled .less files wherever the .json was found (so if you move custom.*.json to another location, the compiled files location will move to that location)
Aaron Judd
@aaronjudd
Sep 11 2015 15:21
I think the error is a byproduct of module-definitions.js in the builder (bootstrap-theme) not being configured for the new theme (my-core-theme))
@tdecaluwe sounds like either a) you don’t have all the updated packages that go with 0.7.0/development) - they aren’t all published to atmosphere so you need to cloen them manually into a local packages dir (bin/clone-packages.sh can make this easy) or b) you need to refresh your .less files. I use bin/reset to delete all my build files, in this case rm client/themes/bootstrap/*.less is what would reset the themes (but make sure you have your own less customizations located elsewhere)
Angel Ramirez
@ar4mirez
Sep 11 2015 15:57

Hi guys quick question i was trying to run the app but i got this error:

[[[[[ ~/WorkSpaces/OpenSource/reaction ]]]]]  

=> Started proxy.                             
=> Started MongoDB.                           
=> Errors prevented startup:                  

   While selecting package versions:
   error: Conflict: Constraint reactioncommerce:core@0.7.0 is not satisfied by reactioncommerce:core 0.6.4.
   Constraints on package "reactioncommerce:core":
   * reactioncommerce:core@0.7.0 <- reactioncommerce:reaction-accounts 1.0.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-shipping 0.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-paypal 0.8.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-braintree 1.3.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-stripe 1.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-auth-net 0.4.2
   * reactioncommerce:core@0.6.3 <- reactioncommerce:reaction-social 0.2.3
   * reactioncommerce:core@0.4.1 <- spencern:reaction-analytics 0.0.3

thank in advance for you help

Bogi
@boboci9
Sep 11 2015 16:06
I have created my own bootstrap-theme and change the dependency in the package.js to my-theme but the error is still the same
I couldn't find in the docs what exactly do we have to change except the packages.js file in the bootstrap-theme in order for it to work
Bogi
@boboci9
Sep 11 2015 16:19
but even without any changes, I just simply clone reactioncommerce:bootstrap-theme and reactioncommerce:core-theme and they to add reactioncommerce:bootstrap-theme I get the same __meteor_bootstrap__ is not defined error
Scott Tolinski
@stolinski
Sep 11 2015 17:01
So. How exactly do I overwrite these less variables that are auto generated
Aaron Judd
@aaronjudd
Sep 11 2015 17:05
@angel-cuemby I just pushed some version # updates to help with that. You’ll need to clone all those packages from the reactioncommerce repo, to get the latest. “bin/clone-packages.sh” is a helper we have for this purpose. At least, until they are published to atmosphere
Scott Tolinski
@stolinski
Sep 11 2015 17:06
It seems like no matter what I try @cart-icon-badge cannot be overridden
Angel Ramirez
@ar4mirez
Sep 11 2015 17:07
@aaronjudd thank you :D i’m review the project i would love to contrib :thumbsup:
Mike Murray
@mikemurray
Sep 11 2015 17:09
@stolinski looking into that
Scott Tolinski
@stolinski
Sep 11 2015 17:12
Thanks @mikemurray ! I'm really loving Reaction so far, but theming has been a bit of a pain point
Mike Murray
@mikemurray
Sep 11 2015 17:14
@stolinski if you add variable overrides to custom.reaction.import.less in reaction > client > themes > bootstrap it should work;
that file is best used to override variables and add styles before everything else
Scott Tolinski
@stolinski
Sep 11 2015 17:16
looks like that did it. Thanks!
Mike Murray
@mikemurray
Sep 11 2015 17:17
theres also custom.reaction.overrides.import.less for overriding styles. That file is loaded after everything
Aaron Judd
@aaronjudd
Sep 11 2015 17:19
@stolinski we have the “theming wishlist” discussion quite often. This is mostly due to meteor’s terrible preprocessor / build implementation. This process should be changing with Meteor 1.2, and hopefully we can make it much easier with that update. I’d love to hear a “theme builder’s wishlist”…
Scott Tolinski
@stolinski
Sep 11 2015 17:20
awesome. I'd love to be apart of that discussion. I've been waiting for the 1.2 update myself so that my PostCSS package can actually work as expected
Aaron Judd
@aaronjudd
Sep 11 2015 17:20
don’t get @mikemurray started with PostCSS…
Scott Tolinski
@stolinski
Sep 11 2015 17:20
My biggest item on the wishlist would be to never have to look a .less file ever ;)
Mike Murray
@mikemurray
Sep 11 2015 17:21
You wound me @stolinski ;)
Scott Tolinski
@stolinski
Sep 11 2015 17:21
haha
a big less fan?
Mike Murray
@mikemurray
Sep 11 2015 17:23
I like both less and sass. Bit I think PostCSS would be better since you can have either in style with one pre-processor
But prefer less, as the syntax is less verbose
pun intended
Angel Ramirez
@ar4mirez
Sep 11 2015 17:25
@aaronjudd i tried the ./bin/clone-packages.sh but stil the same error
Scott Tolinski
@stolinski
Sep 11 2015 17:26
Interesting. I've always felt that less is more verbose/clumsy than Sass. Agreed about Post-CSS. My personal stack is something like https://atmospherejs.com/stolinski/stylus-multi usually
But tbh I haven't used Less on any major projects like I have Sass, so it's probably a familiarity thing.
Aaron Judd
@aaronjudd
Sep 11 2015 17:28
@angel-cuemby can you try meteor update ? You can always run with —allow-incompatible-updatesas well. (Oh and pull reaction itself from development branch, to make sure you’re current there as well)
@boboci9 we’re checking it out now
Angel Ramirez
@ar4mirez
Sep 11 2015 17:31
@aaronjudd I think i need to debug a little bit more apparently ractioncommerce:reaction-accounts requires core@0.7.0 but the rest are pointing to 0.6.1 and analytics 0.4.1
@aaronjudd here is the log
--- OpenSource/reaction ‹development› » meteor update --allow-incompatible-update                                                                                                                                                       1 ↵
This project is already at Meteor 1.1.0.3, the latest release.
=> Errors while upgrading packages:           

While selecting package versions:
error: Conflict: Constraint reactioncommerce:core@0.7.0 is not satisfied by reactioncommerce:core 0.6.4.
Constraints on package "reactioncommerce:core":
* reactioncommerce:core@0.7.0 <- reactioncommerce:reaction-accounts 1.0.0
* reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-shipping 0.4.0
* reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-paypal 0.8.0
* reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-braintree 1.3.0
* reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-stripe 1.4.0
* reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-auth-net 0.4.2
* reactioncommerce:core@0.6.3 <- reactioncommerce:reaction-social 0.2.3
* reactioncommerce:core@0.4.1 <- spencern:reaction-analytics 0.0.3
Mike Murray
@mikemurray
Sep 11 2015 17:32
Im looking into Post-CSS for potential dynamic theme customization through the UI
Scott Tolinski
@stolinski
Sep 11 2015 17:33
@mikemurray awesome! I'd love to see how you implement that
Aaron Judd
@aaronjudd
Sep 11 2015 17:37
@angel-cuemby can you pull (or run clone-packages) again? a couple of those versions aren’t current development versions (updated just a bit ago) - I want to make sure your’re at least using cloned packages in your PACKAGE_DIRS, rather than the published atmosphere packages.
Angel Ramirez
@ar4mirez
Sep 11 2015 17:44
@aaronjudd just did a yes i pull the updated packages but when i run meteor still having the same issue :/
Aaron Judd
@aaronjudd
Sep 11 2015 17:50
log output is exactly the same?
Mike Murray
@mikemurray
Sep 11 2015 17:50
@boboci9 I did a fresh clone of reaction, reaction-bootstrap-theme, reaction-core-theme and did the following: https://www.evernote.com/l/ATOZEzYx6vpMTa4Sp9rrG8NCw_DqJUSy_yQ
I changed the name and version in core-theme, and changed the version and name of the package in bootstrap-theme
Angel Ramirez
@ar4mirez
Sep 11 2015 17:55
@aaronjudd yep
Aaron Judd
@aaronjudd
Sep 11 2015 17:59
@angel-cuemby in .meteor/versions do you see
reactioncommerce:bootstrap-theme@1.5.0
reactioncommerce:core@0.7.0
reactioncommerce:core-theme@1.6.0
reactioncommerce:reaction-accounts@1.0.0
reactioncommerce:reaction-auth-net@0.4.2
reactioncommerce:reaction-braintree@1.3.0
reactioncommerce:reaction-paypal@1.0.0
reactioncommerce:reaction-shipping@0.5.0
reactioncommerce:reaction-social@0.2.3
reactioncommerce:reaction-stripe@2.0.1
Bogi
@boboci9
Sep 11 2015 17:59
@mikemurray I tried these changes but the __meteor_bootstrap__ is not defined still persists
it won't let me add the bootstrap theme
could you list what packages you have enabled?
Angel Ramirez
@ar4mirez
Sep 11 2015 18:00
@aaronjudd nop i’m behind in some packages:
reactioncommerce:bootstrap-theme@1.4.0
reactioncommerce:core@0.7.0
reactioncommerce:core-theme@1.5.0
reactioncommerce:reaction-accounts@1.0.0
reactioncommerce:reaction-auth-net@0.4.2
reactioncommerce:reaction-braintree@1.3.0
reactioncommerce:reaction-paypal@1.0.0
reactioncommerce:reaction-shipping@0.4.0
reactioncommerce:reaction-social@0.2.3
reactioncommerce:reaction-stripe@2.0.0
Mike Murray
@mikemurray
Sep 11 2015 18:03
@boboci9
accounts-facebook                    1.0.4  
audit-argument-checks                1.0.3  
less                                 1.0.14 
meteor-platform                      1.2.2  
nemo64:bootstrap                     3.3.5_2
oauth-encryption                     1.0.5  
reactioncommerce:bootstrap-theme     1.5.0+ 
reactioncommerce:core                0.7.0+ 
reactioncommerce:reaction-accounts   0.1.0+ 
reactioncommerce:reaction-auth-net   0.4.2+ 
reactioncommerce:reaction-braintree  1.3.0+ 
reactioncommerce:reaction-paypal     1.0.0+ 
reactioncommerce:reaction-shipping   0.4.0+ 
reactioncommerce:reaction-social     0.2.3+ 
reactioncommerce:reaction-stripe     2.0.0+ 
spencern:reaction-analytics          0.0.3+ 
spencern:reaction-analytics-libs     0.0.1  
spiderable                           1.0.7  
underscore                           1.0.3
Bogi
@boboci9
Sep 11 2015 18:05
I'm only missing the underscore but I doubt that is the cause, but I will try that
and reaction-accounts but that shouldn't interfere with this either
Mike Murray
@mikemurray
Sep 11 2015 18:14
looking into it, __meteor_bootstrap__ has nothing to do with the actual Bootstrap theme. It's something realated to app level bootstraping / startup. lol jeez... naming
Bogi
@boboci9
Sep 11 2015 18:17
now I tried to create a completely new app from scratch, to exclude all other possibility and I get the same issue as @angel-cuemby after just the first step:
git clone https://github.com/reactioncommerce/reaction.git
cd reaction && git checkout development
meteor
Errors prevented startup:                  

   While selecting package versions:
   error: Conflict: Constraint reactioncommerce:core@0.7.0 is not satisfied by
   reactioncommerce:core 0.6.4.
   Constraints on package "reactioncommerce:core":
   * reactioncommerce:core@0.7.0 <- reactioncommerce:reaction-accounts 1.0.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-shipping 0.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-paypal 0.8.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-braintree 1.3.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-stripe 1.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-auth-net 0.4.2
   * reactioncommerce:core@0.6.3 <- reactioncommerce:reaction-social 0.2.3
   * reactioncommerce:core@0.4.1 <- spencern:reaction-analytics 0.0.3

=> Your application has errors. Waiting for file change.
Mike Murray
@mikemurray
Sep 11 2015 18:21
Must've missed a version increment somewhere. Checking
Aaron Judd
@aaronjudd
Sep 11 2015 18:38
@angel-cuemby @boboci9 please try:
cd reaction
git pull
meteor update
bin/clone-packages.sh
meteor
updated @spencern’s analytics to use a reactioncommerce: org updated version, so that the dependancy is updated to 0.7.0
$ meteor list
accounts-facebook                         1.0.4  Login service for Facebook accounts
audit-argument-checks                     1.0.3  Try to detect inadequate input sanitization
less                                      1.0.14  The dynamic stylesheet language
meteor-platform                           1.2.2  Include a standard set of Meteor packages in your app
nemo64:bootstrap                          3.3.5_2  Highly configurable bootstrap integration.
oauth-encryption                          1.0.5  Encrypt account secrets stored in the database
reactioncommerce:bootstrap-theme          1.5.0+ Reaction Commerce Bootstrap theme builder
reactioncommerce:core                     0.7.0+ Reaction Commerce Core
reactioncommerce:reaction-accounts        1.0.0+ Reaction Accounts - Authentication UI for Reaction Commerce
reactioncommerce:reaction-analytics       1.0.0+ Reaction Analytics - Integrate third-party analytics libraries
reactioncommerce:reaction-analytics-libs  1.0.0+ Reaction Commerce - Analytics Libraries
reactioncommerce:reaction-auth-net        0.4.2+ Reaction Authorize.net - Authorize.net payments for Reaction Commerce
reactioncommerce:reaction-braintree       1.3.0+ Reaction Braintree - Braintree payments for Reaction Commerce
reactioncommerce:reaction-paypal          1.0.0+ Reaction Paypal - PayPal payments for Reaction Commerce
reactioncommerce:reaction-shipping        0.5.0+ Reaction Shipping - Flat Rate shipping for Reaction Commerce
reactioncommerce:reaction-social          0.2.3+ Reaction Social - Social Sharing Package for Reaction
reactioncommerce:reaction-stripe          2.0.1+ Reaction Stripe - Stripe payments for Reaction Commerce
spiderable                                1.0.7  Makes the application crawlable to web spiders
underscore                                1.0.3  Collection of small helpers: _.map, _.each, …
Bogi
@boboci9
Sep 11 2015 18:54
@aaronjudd tried this but the error still persists
Aaron Judd
@aaronjudd
Sep 11 2015 18:57
just pushed an updated reactioncommerce:reaction-social as well. Forgot to merge that one, but I’m not able to replicate the issue. Mike started seeing the error, but once we published did meteor update and then clone-packages, the error went away
Bogi
@boboci9
Sep 11 2015 18:59
meteor update just says that it's at the latest release 1.1.0.3 and then the error is shown again While selecting package versions: error: Conflict: Constraint reactioncommerce:core@0.7.0 is not satisfied by reactioncommerce:core 0.6.4.
Aaron Judd
@aaronjudd
Sep 11 2015 19:00
can you give me a meteor list output?
Bogi
@boboci9
Sep 11 2015 19:02
 meteor list
=> Errors while initializing project:         

While selecting package versions:
error: Conflict: Constraint reactioncommerce:core@0.7.0 is not satisfied by
reactioncommerce:core 0.6.4.
Constraints on package "reactioncommerce:core":
but I can list what I have in the .meteor/packages if you want
# Core Meteor Packages
meteor-platform
oauth-encryption
underscore
less

# Optional Meteor Packages
accounts-facebook
spiderable
audit-argument-checks

# Reaction Commerce Packages
reactioncommerce:core
reactioncommerce:bootstrap-theme
reactioncommerce:reaction-accounts
reactioncommerce:reaction-shipping
reactioncommerce:reaction-paypal
reactioncommerce:reaction-braintree
reactioncommerce:reaction-stripe
reactioncommerce:reaction-auth-net
reactioncommerce:reaction-social
reactioncommerce:reaction-analytics-libs
reactioncommerce:reaction-analytics

# Community Packages
nemo64:bootstrap
Aaron Judd
@aaronjudd
Sep 11 2015 19:04
actually I’m curious about the versions that you have, perhaps you can look at .meteor/versions and find the reaction packages?
(you can actually delete that versions file, and then meteor update will recreate it as well)
I’m just trying to determine a) that you have all the development/unpublished packages b) what’s left that might be requiring 0.6.4
Bogi
@boboci9
Sep 11 2015 19:06
reactioncommerce:bootstrap-theme@1.5.0
reactioncommerce:core@0.7.0
reactioncommerce:core-theme@1.6.0
reactioncommerce:reaction-accounts@1.0.0
reactioncommerce:reaction-analytics@1.0.0
reactioncommerce:reaction-analytics-libs@1.0.0
reactioncommerce:reaction-auth-net@0.4.2
reactioncommerce:reaction-braintree@1.3.0
reactioncommerce:reaction-paypal@1.0.0
reactioncommerce:reaction-shipping@0.5.0
reactioncommerce:reaction-social@0.2.3
reactioncommerce:reaction-stripe@2.0.1
Aaron Judd
@aaronjudd
Sep 11 2015 19:07
hmm, that looks good, all except social that I just pushed (so one more clone-packages.sh)
Stefan Smiljkovic
@shtefcs
Sep 11 2015 19:10
@aaronjudd do u know when u gonna put it in production ?
Aaron Judd
@aaronjudd
Sep 11 2015 19:11
pushing for 0.8.x to be the first beta release
Bogi
@boboci9
Sep 11 2015 19:11
:( no luch the error is still there
I will try with a clean version
Aaron Judd
@aaronjudd
Sep 11 2015 19:12
really strange - clean versions are building and tests are passing ok on clean boxes for me (circleci shows failing but that’s some new “other” error)
one thing -> if you have local branches “clone-packages” will not switch to the freshly pulled branch, you’ll need to manually make sure your on the fresh pull (mostly development branch)
I was just debating if I should automatically switch you, but that seems potentially intrusive
Bogi
@boboci9
Sep 11 2015 19:14
I am simply tring
git clone https://github.com/reactioncommerce/reaction.git
cd reaction && git checkout development
bin/clone-packages.sh
meteor
Aaron Judd
@aaronjudd
Sep 11 2015 19:15
that should work
Bogi
@boboci9
Sep 11 2015 19:25
the git clone took a bit more then expected but the error persists
reaction packages from the .meteor/versions
reactioncommerce:bootstrap-theme@1.5.0
reactioncommerce:core@0.7.0
reactioncommerce:core-theme@1.6.0
reactioncommerce:reaction-accounts@1.0.0
reactioncommerce:reaction-analytics@1.0.0
reactioncommerce:reaction-analytics-libs@1.0.0
reactioncommerce:reaction-auth-net@0.4.2
reactioncommerce:reaction-braintree@1.3.0
reactioncommerce:reaction-paypal@1.0.0
reactioncommerce:reaction-shipping@0.5.0
reactioncommerce:reaction-social@0.3.0
reactioncommerce:reaction-stripe@2.0.1
Angel Ramirez
@ar4mirez
Sep 11 2015 19:41
@aaronjudd i did what you suggest before and yes analytics got updated but still throwing the same issue
=> Started proxy.                             
=> Started MongoDB.                           
=> Errors prevented startup:                  

   While selecting package versions:
   error: Conflict: Constraint reactioncommerce:core@0.7.0 is not satisfied by reactioncommerce:core 0.6.4.
   Constraints on package "reactioncommerce:core":
   * reactioncommerce:core@0.7.0 <- reactioncommerce:reaction-accounts 1.0.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-shipping 0.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-paypal 0.8.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-braintree 1.3.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-stripe 1.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-auth-net 0.4.2
   * reactioncommerce:core@0.6.3 <- reactioncommerce:reaction-social 0.2.3
   * reactioncommerce:core@0.7.0 <- reactioncommerce:reaction-analytics 1.0.0

   Conflict: Constraint reactioncommerce:core@0.7.0 is not satisfied by reactioncommerce:core 0.6.4.
   Constraints on package "reactioncommerce:core":
   * reactioncommerce:core@0.7.0 <- reactioncommerce:reaction-accounts 1.0.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-shipping 0.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-paypal 0.8.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-braintree 1.3.0
   * reactioncommerce:core@0.6.1 <- reactioncommerce:reaction-stripe 1.4.0
   * reactioncommerce:core@0.6.0 <- reactioncommerce:reaction-auth-net 0.4.2
   * reactioncommerce:core@0.6.3 <- reactioncommerce:reaction-social 0.2.3
   * reactioncommerce:core@0.7.0 <- reactioncommerce:reaction-analytics 1.0.0
Mike Murray
@mikemurray
Sep 11 2015 19:43
Hmm.. I'm going to try setting up reacton on a fresh server somewhere. Maybe our local config is making it work somehow
Aaron Judd
@aaronjudd
Sep 11 2015 19:44
@angel-cuemby are you able to run 'meteor list'?
Angel Ramirez
@ar4mirez
Sep 11 2015 19:45
@aaronjudd that’s actually the output i got from that command
Aaron Judd
@aaronjudd
Sep 11 2015 19:47
Hmm, ok, I didn't think "list" would try and run the app.
Angel Ramirez
@ar4mirez
Sep 11 2015 19:48
yes looks like uhmm
Mike Murray
@mikemurray
Sep 11 2015 20:22
On a fresh digital ocean droplet, I can confirm I'm getting the same error
Mike Murray
@mikemurray
Sep 11 2015 20:38
@angel-cuemby got one step futher... clone-packages.sh will not work unless you have export PACKAGE_DIRS="/<full-path-to-packages-dir-somewhere>" set in your env variables. Otherwise all the packages will be cloned into /tmp/
However, even after that I get the following:
=> Started proxy.                             
=> Started MongoDB.                           
=> Errors prevented startup:                  

   While selecting package versions:
   error: Conflict: Constraint reactioncommerce:core-theme@1.6.0 is not satisfied by reactioncommerce:core-theme 1.5.0.
   Constraints on package "reactioncommerce:core-theme":
   * reactioncommerce:core-theme@1.6.0 <- reactioncommerce:bootstrap-theme 1.5.0
which is an easy fix
Angel Ramirez
@ar4mirez
Sep 11 2015 20:41
@mikemurray i’ll try that :D
Mike Murray
@mikemurray
Sep 11 2015 20:50
then.. manually cloning reaction-core-theme into that packages dir, resolved the above error. which then gives me:
=> Started proxy.                             
=> Started MongoDB.                           
=> Errors prevented startup:                  

   While building plugin `analyticsConfigurator` in package `reactioncommerce:reaction-analytics`:
   error: File not found: server/buildtools/analyticsSources.js
   error: File not found: server/buildtools/defaultConfiguration.js
   error: File not found: server/buildtools/analyticsConfigurator.js
Aaron Judd
@aaronjudd
Sep 11 2015 20:50
if you don’t have PACKAGE_DIRS set, then it clones to /tmp/reaction-packages, then exports PACKAGE_DIRS=/tmp/reaction-packages. so it should work if you don’t have a regular working area setup.
Mike Murray
@mikemurray
Sep 11 2015 20:56
the export would only work for the duration of the session. So If you're a tabaholic like me, it wouldn't work in to other terminal sessions
Aaron Judd
@aaronjudd
Sep 11 2015 20:56
I’m able to replicate now, give me a few minutes.. :boom:
@mikemurray good point, I’ve never used it in that way
Spencer Norman
@spencern
Sep 11 2015 20:58
Wow, I go offline for half a day and everyone in the channel shows up
Mike Murray
@mikemurray
Sep 11 2015 21:00
also @aaronjudd whould it be better to use /opt or /usr/local instead of /tmp?
Aaron Judd
@aaronjudd
Sep 11 2015 21:05
the use case that I wrote for was just for our test enviroment, but it seems like it could be a handy tool that should be bit less brittle. I’m not sure that /opt is a standard though, and test environments are epheremeral (hence tmp)…
Aaron Judd
@aaronjudd
Sep 11 2015 21:15
ok… I bet it works now for everyone sigh
Mike Murray
@mikemurray
Sep 11 2015 21:17
clone packages or meteor update?
Aaron Judd
@aaronjudd
Sep 11 2015 21:17
you might have to do a meteor update first, because I published the reaction-core-theme package (v.1.6.0) to fix this. The thing about that clone-packages that IS a problem - it doesn’t know about dev dependencies.
we could switch to using the versions file, rather than packages as the source
Mike Murray
@mikemurray
Sep 11 2015 21:19
so now just the analyticsConfigurator issue remains with my instance
@aaronjudd
While building plugin `analyticsConfigurator` in package `reactioncommerce:reaction-analytics`:
error: File not found: server/buildtools/analyticsSources.js
error: File not found: server/buildtools/defaultConfiguration.js
error: File not found: server/buildtools/analyticsConfigurator.js
Aaron Judd
@aaronjudd
Sep 11 2015 21:27
I’m unable to replicate that, from a clean clone-packages - and the analytics packages were already published.
to be absolutely sure, that the published ones aren’t causing some issue I just republished them.
**from the clone-packages checkout
Mike Murray
@mikemurray
Sep 11 2015 21:30
just did a reset, and fresh checkout and still getting that issue
Angel Ramirez
@ar4mirez
Sep 11 2015 21:30
@mikemurray @aaronjudd adding PACKAGE_DIRS works for me finally i have the system up and running there is some frontend errors but no big deal :D
Mike Murray
@mikemurray
Sep 11 2015 21:32
@angel-cuemby great!
OMG @aaronjudd I think I may know what its doing that
Angel Ramirez
@ar4mirez
Sep 11 2015 21:33
@mikemurray @aaronjudd thank both of you for all the help :D
Mike Murray
@mikemurray
Sep 11 2015 21:33
OSX is case-insensitve with file names
its looking for buildtools, the dir is actually buildTools
and I'm on linux
Aaron Judd
@aaronjudd
Sep 11 2015 21:36
interesting possibility, did you test that? I can update it, but wouldn’t explain why it worked the last couple of versions just fine. (and our docker images are linux as well)
but i’m changing now - its’ not our standard anyways
Mike Murray
@mikemurray
Sep 11 2015 21:38
changing it worked
Aaron Judd
@aaronjudd
Sep 11 2015 21:43
ok, committed (and published) the update with case patch
(or maybe it didn’t work before, ahem )
nice catch! I’m curious if this affects the mysterious Circle CI issue I’m having
Mike Murray
@mikemurray
Sep 11 2015 21:45
lol
Aaron Judd
@aaronjudd
Sep 11 2015 21:47
didn’t fix the build test, here’s the current mystery there:
./bin/clone-packages.sh

./bin/clone-packages.sh returned exit code 127

bash: ./bin/clone-packages.sh: No such file or directory Action failed: ./bin/clone-packages.sh
Mike Murray
@mikemurray
Sep 11 2015 21:47
thats easy. No such file or directory! ;)
it may be running it from the wrong directory
somehow
Aaron Judd
@aaronjudd
Sep 11 2015 21:48
it’s supposed to be there.. from circleci env variables
Mike Murray
@mikemurray
Sep 11 2015 21:48
could you log the pwd before it tries to run that command?
Aaron Judd
@aaronjudd
Sep 11 2015 21:48
I just modified it and resaved, trying.. (you know, like windows 95)
Mike Murray
@mikemurray
Sep 11 2015 21:49
did you restart 3 times?
and keep it turned off for at least 60 seconds
Aaron Judd
@aaronjudd
Sep 11 2015 21:52
lol - I wish it was that easy. but starting the third time now...
is there any reason we shouldn’t just check out the packages into reaction/packages if you don’t have a PACKAGE_DIR defined? or is that just too obvious?
Mike Murray
@mikemurray
Sep 11 2015 21:57
we probably could
Angel Ramirez
@ar4mirez
Sep 11 2015 22:05
@mikemurray @aaronjudd what i did is just if is not defined to look at ~/.meteor/reaction-packages i figure since you need to have meteor installed to run it
Aaron Judd
@aaronjudd
Sep 11 2015 22:12
It’s been a while since I wrote this, I had some specifics to the testing env that I needed - to make sure it didn’t get bundled for instance — if I put in packages or ./meteor, I’d also need to make sure that after tests ran, that those directories were cleared before bundling a package less build. I think there were other issues there as well. @jshimko Although that’s probably not needed at all for dev builds, just bundling with packages included would speed up the docker builds a lot.