<p>Each week, you should change into the <code>plutus-pioneer-program</code> directory</p>
<pre><code>cd plutus-pioneer-program
</code></pre>
<p>Pull the latest changes from upstream</p>
<pre><code>git pull
</code></pre>
<p>View the <code>plutus-apps</code> git tag for the week in the <code>cabal.project</code> file. For week 2, look at <code>plutus-pioneer-program/code/week02/cabal.project</code>. <a href="https://github.com/input-output-hk/plutus-pioneer-program/blob/main/code/week02/cabal.project#L63" rel="noreferrer">On line 63 you see the git tag</a>.</p>
<pre><code>source-repository-package
  type: git
  location: https://github.com/input-output-hk/plutus-apps.git
  tag: 6aff97d596ac9d59460aab5c65627b1c8c0a1528
</code></pre>
<p>Then change into <code>plutus-apps</code></p>
<pre><code>cd plutus-apps
</code></pre>
<p>Pull the latest changes from upstream</p>
<pre><code>git pull
</code></pre>
<p>And checkout the appropriate tag</p>
<pre><code>git checkout 6aff97d596ac9d59460aab5c65627b1c8c0a1528
</code></pre>
<p>Make sure you're in the <code>plutus-apps</code> directory and that you've checked out the correct tag. From there you can start as many Nix shells as necessary.</p>
<pre><code>nix-shell
</code></pre>
<p>You may or may not want a Nix shell each for:</p>
<ul>
<li>starting the playground server</li>
<li>starting the playground client</li>
<li>building and serving Haddock docs</li>
<li>starting a cabal REPL inside the appropriate week project</li>
<li>building the cabal project</li>
</ul>

CC BY-SA 4.0
2022-01-25T21:01:45.337Z
Thanks @Travis!
punkbit
CC BY-SA 4.0
2022-01-25T20:21:50.773Z
2022-01-25T20:21:50.773Z
Travis
<p>I'd like to know if we should use the week 01 nix-shell?</p>
<p>My expectation is that the week 01 nix-shell, was used to start the playground service and the front-end UI.</p>
<p>Although, it's clear that there's a need to have the *.nix files for <code>nix-shell</code> to work or startup, would be nice to hear from someone more experienced in nix.</p>

<plutus-pioneer-program><plutus-playground><nix-shell>
Use the week 01 Nix-shell for week 02?
# Use the week 01 Nix-shell for week 02?

(Asked by: username_0 on 2022-01-25)

I'd like to know if we should use the week 01 nix-shell?

My expectation is that the week 01 nix-shell, was used to start the playground service and the front-end UI.

Although, it's clear that there's a need to have the \*.nix files for `nix-shell` to work or startup, would be nice to hear from someone more experienced in nix.

**Tags:** plutus-pioneer-program, plutus-playground, nix-shell

---

## 1 answers

### Answer by username_1 on 2022-01-25. Score: 6 | Accepted answer

Each week, you should change into the plutus-pioneer-program directory
cd plutus-pioneer-program

Pull the latest changes from upstream
git pull

View the plutus-apps git tag for the week in the cabal.project file. For week 2, look at plutus-pioneer-program/code/week02/cabal.project. On line 63 you see the git tag.
source-repository-package
  type: git
  location: https://github.com/input-output-hk/plutus-apps.git
  tag: 6aff97d596ac9d59460aab5c65627b1c8c0a1528

Then change into plutus-apps
cd plutus-apps

Pull the latest changes from upstream
git pull

And checkout the appropriate tag
git checkout 6aff97d596ac9d59460aab5c65627b1c8c0a1528

Make sure you're in the plutus-apps directory and that you've checked out the correct tag. From there you can start as many Nix shells as necessary.
nix-shell

You may or may not want a Nix shell each for:

starting the playground server
starting the playground client
building and serving Haddock docs
starting a cabal REPL inside the appropriate week project
building the cabal project

> **Comments:**
> **username_0**: Thanks @Travis!  

---

