I am looking for someone who has experience working in a meteor dev team with different environments.
I have a project with two meteor apps that share the some custom packages. The repo structure is kind of like this:
/
/packages
/adminApp
/mobileApp
and I created symlinks in the adminApp/packages folder that point to the /packages folder.
I read the git support for windows thread with @dandv pushing for support of symlinks on windows but I don’t understand the applied fix. The symlinks on windows appear as files but meteor is not able to find the packages.
How can I have this type of repo that can be cloned in windows ? Or what are the workarounds possible ?
One solution could be to ignore the symlinks the app/packages folders and to run a script after each pull to create them using ln -s or mklink depending on the platform.
What do you think about that ? Could there be an easier approach ?
I thought there was a way to define a global package directory, but I can’t find it in the docs at the moment. Maybe it was for an old version of Meteor.
PACKAGES_DIR is a list of directories in which to look for packages. Directories are delimited by the appropriate separator character (: in linux, ; in windows).
Local package directories are searched first when building an app.
Thanks a lot to you both! I think this is the most simple solution for this problem.
It would be nice that some blogger with a lot readers would a little article on this so that future people in my position would find a solution easily. Or maybe even better: create an “environment variables” section in the docs that list all of the variables used by meteor.
On the same topic. I’ve got the same structure as @elgusto and haven’t quite figured out the workflow for making git commits that pull in package contents. I just end up committing the symlinks.
Does anyone know of a step by step tutorial for getting this working? I’m using a Mac.
@babrahams@elgusto what I do when I need to dissect an app into shared local packages, is to make my git root the topmost folder containing apps and packages
By the way, I should have said this a long time ago … Every time I see a post of yours on these forums, I read it with interest. For me, you’re the voice of reason when things get heated, and a constant source of useful knowledge for all of us. Major respect.
Hi, are you using this with galaxy deploy? I don’t know if this will work. Will deploy command understand package_dirs and upload these folders inside my app or your packages are published in atmosphere?