Last active
October 5, 2018 20:21
-
-
Save richbodo/ab6afd6892451168e3321be12f40f0c1 to your computer and use it in GitHub Desktop.
Config a new pixelbook crostini container for smart contract developement
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Basic stuff I need to get all the other stuff | |
# I think git, curl, and python were in the container already | |
sudo dpkg-reconfigure tzdata | |
sudo apt-get update | |
sudo apt-get upgrade | |
sudo apt-get install apt-file | |
sudo apt-file update | |
sudo apt-get install python emacs-nox screen git ssh wget curl gnupg build-essential iputils-ping telnet netcat | |
# Web-dev packaging stuff | |
# From: https://github.com/creationix/nvm#install-script | |
wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh | bash | |
nvm install 10 | |
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - | |
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list | |
sudo apt remove cmdtest | |
sudo apt-get update && sudo apt-get install --no-install-recommends yarn | |
# Truffle, ganach, etc install - from: https://truffleframework.com/boxes/drizzle | |
npm install -g truffle | |
npm install -g ganache-cli | |
# This has to be done in an empty directory | |
cd | |
mkdir src | |
cd src | |
mkdir td_example | |
cd td_example | |
truffle unbox drizzle | tee ../unbox.log | |
# Thats all the install/command-line config required | |
# You have been dumped at step 3 of this tutorial: https://truffleframework.com/boxes/drizzle | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: I have no idea why a curl - bash pipeline is the official way of installing nvm. It's unnerving, really. The maintainers must be sweating bullets. I have been avoiding node for all but experimenting. Doesn't seem avoidable at this point. Experienced node app maintainers will surely have better ways of obtaining audited, signed, trusted versions of these packages, but there is no movement to support a deb package that I could find.