<p>Use <code>41149926c108c71831cfe8d244c83b0ee4bf5c8a</code> as specified <a href="https://github.com/input-output-hk/plutus-pioneer-program/blob/main/code/week01/cabal.project#L63" rel="nofollow noreferrer">here</a></p>

CC BY-SA 4.0
2022-06-21T21:23:18.263Z
answer is insufficient, does not follow good practices as stated: https://stackoverflow.com/help/closed-questions
Igodlab
CC BY-SA 4.0
2022-01-13T09:48:46.203Z
2022-01-13T09:48:46.203Z
ymegdiche
<p>You can find it in the <a href="https://github.com/input-output-hk/plutus-pioneer-program/blob/main/code/week01/cabal.project#L63" rel="nofollow noreferrer">Plutus Pioneer Program cabal.project</a> file under the plutus-apps dependency entry.</p>

CC BY-SA 4.0
2022-01-13T09:34:06.033Z
2022-01-13T09:34:06.033Z
Will
<p>Update and detailed answer Feb 4, 2022.</p>
<p>For the purposes of the Plutus Pioneer Program, the checkout information can be found in the weekly cabal.project file, located (for Week04, as an example, and on my system) at</p>
<blockquote><pre>
~/plutus/plutus-pioneer-program/code/week04/cabal.project
</pre></blockquote>
I have developed a system using aliases that load when I enter my shell (using a text file sourced from within .zshrc) and my nix-shell (same file, but sourced from .bashrc which is what nix uses). Among those aliases are:
<blockquote><pre>
alias pp='cd ~/plutus/plutus; ls -laFh; pwd'
alias ppa='cd ~/plutus/plutus-apps; ls -laFh; pwd'
alias ppp='cd ~/plutus/plutus-pioneer-program; ls -laFh; pwd'
alias pppw4='cd ~/plutus/plutus-pioneer-program/code/week04; ls -laFh; pwd'
</pre></blockquote>
<p>So now my sequence is</p>
<blockquote><pre>
pp
git pull
ppp
git pull
ppa
git pull
pppw4
cat cabal.project
</pre></blockquote>
<p>The &quot;git pull&quot; following the &quot;ppp&quot; is what brings in the weekly lesson/project files.</p>
<p>I then look within cabal.project for the following section (the key portion is directly under &quot;plutus-apps.git&quot;) Be careful because there are numerous other tags in that file.</p>
<blockquote><pre>
package cardano-wallet-core-integration
&nbsp;&nbsp;optimization: False
&nbsp;&nbsp;
source-repository-package
&nbsp;&nbsp;type: git
&nbsp;&nbsp;location: https://github.com/input-output-hk/plutus-apps.git
&nbsp;&nbsp;tag:ea1bfc6a49ee731c67ada3bfb326ee798001701a
&nbsp;&nbsp;subdir:
&nbsp;&nbsp;&nbsp;&nbsp;freer-extras
&nbsp;&nbsp;&nbsp;&nbsp;playground-common
&nbsp;&nbsp;&nbsp;&nbsp;plutus-chain-index-core
&nbsp;&nbsp;&nbsp;&nbsp;plutus-contract
&nbsp;&nbsp;&nbsp;&nbsp;plutus-ledger
&nbsp;&nbsp;&nbsp;&nbsp;plutus-ledger-constraints
&nbsp;&nbsp;&nbsp;&nbsp;quickcheck-dynamic
&nbsp;&nbsp;
-- Direct dependency.
-- Are you thinking of updating this tag to some other commit?
</pre></blockquote>
<p>I then use this info to add an alias to my aliases file.</p>
<blockquote><pre>
alias pppcheckoutw4='cd ~/plutus/plutus-apps; git checkout ea1bfc6a49ee731c67ada3bfb326ee798001701a'
</pre></blockquote>
That way I can easily do the git checkout in the future with
<blockquote><pre>
pppcheckoutw4
</pre></blockquote>
and then enter the nix shell (always from within the Plutus-apps directory!)
 
Once in the nix shell I do "$ pppw4" (or whichever week it is) and then "$ cabal update" and then "$ cabal repl" and I am ready to work.
<p>So now I have an efficient and organized system for doing my &quot;git pull&quot;s and &quot;git checkout&quot; before diving into my nix shell and then my cabal repl. May you find your way as pleasant.</p>
<p>=========== Original Question ===========</p>
<p>When setting up plutus-playground, I have seen comments and at least one other source that advised running</p>
<blockquote>
git checkout 3746610e53654a1167aeb4c6294c6096d16b0502<br>
#Newer??<br>
git checkout 7f53f18dfc788bf6aa929f47d840efa1247e11fd<br>
</blockquote>
inside the plutus-apps directory, prior to running
<blockquote>
[$] nix-build -A plutus-playground.client<br>
[$] nix-build -A plutus-playground.server
</blockquote>
This seemed to be the key for me to successfully build and run the playground, yet it is not in the canonical instructions and I have no idea how I could have deduced this on my own. Where does that line(code) come from (I assume github, but where?) and should it be included in the canonical instructions? How is it different from "git commit"? Does it have anything to do with the similar codes in the cabal.project files in plutus and plutus-apps? Still learning, explanation appreciated!

<plutus-pioneer-program><plutus-playground>
Where do I find correct and current git checkout?
# Where do I find correct and current git checkout?

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

Update and detailed answer Feb 4, 2022.
For the purposes of the Plutus Pioneer Program, the checkout information can be found in the weekly cabal.project file, located (for Week04, as an example, and on my system) at

~/plutus/plutus-pioneer-program/code/week04/cabal.project

I have developed a system using aliases that load when I enter my shell (using a text file sourced from within .zshrc) and my nix-shell (same file, but sourced from .bashrc which is what nix uses). Among those aliases are:

alias pp='cd ~/plutus/plutus; ls -laFh; pwd'
alias ppa='cd ~/plutus/plutus-apps; ls -laFh; pwd'
alias ppp='cd ~/plutus/plutus-pioneer-program; ls -laFh; pwd'
alias pppw4='cd ~/plutus/plutus-pioneer-program/code/week04; ls -laFh; pwd'

So now my sequence is

pp
git pull
ppp
git pull
ppa
git pull
pppw4
cat cabal.project

The "git pull" following the "ppp" is what brings in the weekly lesson/project files.
I then look within cabal.project for the following section (the key portion is directly under "plutus-apps.git") Be careful because there are numerous other tags in that file.

package cardano-wallet-core-integration
  optimization: False
  
source-repository-package
  type: git
  location: https://github.com/input-output-hk/plutus-apps.git
  tag:ea1bfc6a49ee731c67ada3bfb326ee798001701a
  subdir:
    freer-extras
    playground-common
    plutus-chain-index-core
    plutus-contract
    plutus-ledger
    plutus-ledger-constraints
    quickcheck-dynamic
  
-- Direct dependency.
-- Are you thinking of updating this tag to some other commit?

I then use this info to add an alias to my aliases file.

alias pppcheckoutw4='cd ~/plutus/plutus-apps; git checkout ea1bfc6a49ee731c67ada3bfb326ee798001701a'

That way I can easily do the git checkout in the future with

pppcheckoutw4

and then enter the nix shell (always from within the Plutus-apps directory!)
 
Once in the nix shell I do "$ pppw4" (or whichever week it is) and then "$ cabal update" and then "$ cabal repl" and I am ready to work.
So now I have an efficient and organized system for doing my "git pull"s and "git checkout" before diving into my nix shell and then my cabal repl. May you find your way as pleasant.
=========== Original Question ===========
When setting up plutus-playground, I have seen comments and at least one other source that advised running

git checkout 3746610e53654a1167aeb4c6294c6096d16b0502
#Newer??
git checkout 7f53f18dfc788bf6aa929f47d840efa1247e11fd

inside the plutus-apps directory, prior to running

[$] nix-build -A plutus-playground.client
[$] nix-build -A plutus-playground.server

This seemed to be the key for me to successfully build and run the playground, yet it is not in the canonical instructions and I have no idea how I could have deduced this on my own. Where does that line(code) come from (I assume github, but where?) and should it be included in the canonical instructions? How is it different from "git commit"? Does it have anything to do with the similar codes in the cabal.project files in plutus and plutus-apps? Still learning, explanation appreciated!

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

---

## 2 answers

### Answer by username_3 on 2022-01-13. Score: 4

You can find it in the [Plutus Pioneer Program cabal.project](https://github.com/input-output-hk/plutus-pioneer-program/blob/main/code/week01/cabal.project#L63) file under the plutus-apps dependency entry.


---

### Answer by username_1 on 2022-01-13. Score: -2

Use `41149926c108c71831cfe8d244c83b0ee4bf5c8a` as specified [here](https://github.com/input-output-hk/plutus-pioneer-program/blob/main/code/week01/cabal.project#L63)

> **Comments:**
> **username_2**: answer is insufficient, does not follow good practices as stated: https://stackoverflow.com/help/closed-questions  

---

