-
Notifications
You must be signed in to change notification settings - Fork 173
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.
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
Add install make, npm to LORIS 21.0 installation documentation. #5250
Comments
Thanks @coreyAbout - 2 clarification questions:
To do:
|
@christinerogers |
* Corey's ticket aces#5250 points out that `make` and `npm` should be installed initially. *Revert this commit* if disagreement ensues.
corey's issue aces#5250 points out that make and npm installation should be specified *Revert this commit* (and the previous one) if disagreement ensues
Right now we don't go "in depth" into how to get the LORIS system dependencies installed, including PHP, Apache, MariaDB/MySQL, Composer, and npm. We also don't describe how to install The process of getting an environment ready to run software is referred to as "bootstrapping" and there are many approach to this, such as containerization (e.g. Docker, Vagrant), package managers (e.g. a We don't really have any bootstrapping support or documentation at this time, either for development installs or full production installs. This is a long-standing issue. See #4365 and #3981. To respond to the above points:
|
@johnsaigle Thanks for the comment. Right now we DO have guidelines on how to get LORIS system dependencies installed. Check it out here: https://github.com/aces/Loris/wiki/Installing-Loris-in-Depth#getting-prerequisites |
You're right, there is that Wiki page. It's incomplete though, and out of date as you've noted. |
This should now be clarified by the new install documentation. |
Installing Loris in Depth:
Running the Install Script section
step 9:
Run make (for production instances) or make dev (for development sandboxes)
Problems:
sudo apt install make
firstThe text was updated successfully, but these errors were encountered: