-
Notifications
You must be signed in to change notification settings - Fork 0
/
fetchdependencies.html
31 lines (24 loc) · 1.97 KB
/
fetchdependencies.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
---
layout: default
head_title: "LESK: Fetch dependencies"
title: Fetch dependencies
---
<div class="row">
<div class="12u">
<h2>Composer</h2>
<p>This project includes the file 'composer.lock'. The purpose of the 'composer.lock' file is to lock the version of the various packages needed by a project as this one. By using the included lock file you are sure to use the same version of those packages as were used during the design.</p>
<p>Fetch all dependencies using Composer by issuing one of the following commands depending on which environment you are trying to configure:</p>
<p>For a development environment use:</p>
<pre><code>composer install</code></pre>
<p>For a production environment use:</p>
<pre><code>composer install --no-dev</code></pre>
<p><strong>NOTE 1:</strong> To bypass the lock on package versions run the command composer update.
<p><strong>NOTE 2:</strong> On a production server, prior to running the composer install command, you will want to deploy a copy of your file composer.lock from your development server, to guarantee that the exact version of the various packages that you have developed and tested gets installed. Never run the composer update command on a production server.</p>
<p><strong>NOTE 3:</strong> If the composer command fails with a memory allocation error, see the Troubleshooting section.</p>
<h2>Node.js</h2>
<p>Fetch all dependencies for Node.js using npm by using the following command:</p>
<pre><code>npm install</code></pre>
<p><strong>NOTE 4:</strong> If the npm install command fails or hangs, check the tip on Node.js in the Troubleshooting section.</p>
</div>
</div>
{% include footer.html prev_page="acquirecopy" prev_title="Acquire a copy" next_page="basicconfiguration" next_title="Basic configuration" %}