Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make npm install script cross-platform (starting with Linux and OS X) #25

Open
jmakeig opened this issue Sep 8, 2016 · 3 comments
Open

Make npm install script cross-platform (starting with Linux and OS X) #25

jmakeig opened this issue Sep 8, 2016 · 3 comments
Assignees
@jmakeig
Labels
ⓧ cross-platform ⚑ important task
Milestone
1.0

Comments

@jmakeig
Copy link
Owner

jmakeig commented Sep 8, 2016 •
edited
Loading

The npm install script runs after an npm install mltap. It needs to do two things:

  • Set up the MarkLogic security settings (config)
  • Deploy the modules to a modules database or the Modules directory of the MarkLogic installation (deploy)

File system deployment requires sudo on Linux (and probably admin on Windows) because MarkLogic is installed into /opt/MarkLogic. On OS X, MarkLogic is installed in the user’s home directory and thus doesn’t require sudo.

Note that on Travis sudo npm … won’t work because npm isn't in the root user’s PATH, because Travis is using nvm.
@jmakeig jmakeig added this to the 1.0 milestone Sep 8, 2016
@jmakeig jmakeig self-assigned this Sep 8, 2016
This was referenced Sep 8, 2016
Closed
Open
@jmakeig
Copy link
Owner Author

jmakeig commented Sep 29, 2016 •
edited
Loading

ncp can help with moving files.

  • Windows: C:\Program Files\MarkLogic\
  • Linux: /opt/MarkLogic

jmakeig added a commit that referenced this issue Jan 10, 2017
@jmakeig
Adds auto-detection of ML_HOME (#69)
d27727c 
Uses $(uname) to detect the OS and set the location of the MarkLogic install accordingly. This is related to #25. mltap should also be able to be installed in a Modules database in the future.
@jmakeig jmakeig mentioned this issue Jan 10, 2017
Merged
jmakeig added a commit that referenced this issue Jan 30, 2017
@jmakeig
Adds auto-detection of ML_HOME (#69)
958ce4f 
Uses $(uname) to detect the OS and set the location of the MarkLogic install accordingly. This is related to #25. mltap should also be able to be installed in a Modules database in the future.
Fixes path substitution and quotes.
jmakeig added a commit that referenced this issue Jan 30, 2017
@jmakeig
Adds auto-detection of ML_HOME (#69)
fb867dd 
Uses $(uname) to detect the OS and set the location of the MarkLogic install accordingly. This is related to #25. mltap should also be able to be installed in a Modules database in the future.
Fixes path substitution and quotes.
@jmakeig
Copy link
Owner Author

jmakeig commented Apr 16, 2017

The best practice for production is to load (your own) modules into a modules database. For development, however, it’s more convenient and better supports SCM workflows to run modules directly off the filesystem. An installer should be able to support both scenarios.

@jmakeig
Copy link
Owner Author

jmakeig commented Apr 16, 2017

Checkout https://www.npmjs.com/package/walk for recursive, async file walker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jmakeig jmakeig

Labels
ⓧ cross-platform ⚑ important task
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@jmakeig