This tutorial is based on a clean install of Debian Buster (10) GNU/Linux, and in combination with Node.js, VS Code, and Java will provide a system to allow the development, testing and support of Daml code.
Operating System (OS): Debian Buster (10) Kernel: Linux version 4.19.0-14-amd64 Desktop Environment: XFCE 4.12 Terminal: xfce4-terminal 0.8.7.4
This tutorial assumes very little GNU/Linux Command Line Interface (CLI) knowledge, other than that you can open a Terminal, and follow instructions. If you are proficient, feel free to skim through this tutorial as needs be.
A complete Daml/VS Code installation will require these packages:
- The use of # is similar to a comment in a program, for information only.
- The use of $ indicates the terminal prompt from the system user perspective, and is this case, the $user is ‘quid’. If the #ROOT user is to be used, the terminal prompt will be displayed like this:
- This tutorial is aimed at the absolute novice, and has simple commands that are very sequential, even repetitive.
- If any of the following packages already exist on your system, execute the commands anyway, it will cause no issue, other than warnings.
- Every word or abbreviation after the $ is a command to be executed. Type the short commands in directly but use Copy & Paste for others.
- This tutorial commences in a Terminal in the /home/your_user directory.
# Verify if Curl is installed $ which curl $ curl bash: curl: command not found # Update the APT package $ sudo apt update # Install Curl $ sudo apt install curl # Current Curl VERSION $ curl --version curl 7.64.0 (x86_64-pc-linux-gnu) ...
Systems Building Packages
# autoconf automake autotools-dev bison build-essential # dpkg-dev gcc g++ make # Update the APT package cache $ sudo apt update # Install the systems building packages $ sudo apt install autoconf automake autotools-dev bison\ build-essential dpkg-dev gcc g++ make
# Verify if Git is installed $ which git $ dpkg --list | grep ii | git bash: git: command not found # Update the APT package cache $ sudo apt update # Install Git $ sudo apt install git # Verify Git is installed $ which git /usr/bin/git # Current Git VERSION $ git --version git version 2.20.1
# https://nodejs.org/en/download/package-manager/\ #debian-and-ubuntu-based-linux-distributions # https://github.com/nodesource/distributions/blob/master/README.md # Verify if Node.js is installed $ which node $ dpkg --list | grep ii | node bash: node: command not found bash: $: command not found # Update the APT package cache $ sudo apt update # Install the latest Node.js (Node.js v15.x) as the ROOT user $ su root root@host:/home/quid# apt update root@host:/home/quid# curl -fsSL https://deb.nodesource.com/\ setup_15.x | bash - # Exit ROOT user, to normal $user root@host:/home/quid# exit # Install Node.js latest $ sudo apt install nodejs # Current Node.js VERSION $ node --version v15.11.0
# Verify if Java is installed $ which java /usr/bin/java # Simple Java version $ java --version openjdk 220.127.116.11 2020-11-04 OpenJDK Runtime Environment (...) OpenJDK 64-Bit Server VM (...) # Identify exact Java version $ ls /usr/lib/jvm default-java java-1.11.0-openjdk-amd64 java-11-openjdk-amd64 # Add Java_PATH to your User settings (~/.bashrc) # Refer to above for exact JAVA_VERSION which in # this case is 'java-1.11.0-openjdk-amd64' $ echo "export JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64" >> ~/.bashrc # Update USER_SETTINGS $ source ~/.bashrc # Verify the correct JAVA_HOME is set $ echo $JAVA_HOME /usr/lib/jvm/java-1.11.0-openjdk-amd64
# https://code.visualstudio.com/download # Verify if VS Code (code) is installed $ which code $ dpkg --list | grep ii | code bash: code: command not found # Go to the VS Code Editor site $ firefox https://code.visualstudio.com/docs/setup/setup-overview # Select Linux section and scroll down to the # 'Debian and Ubuntu based distributions section' # # There are two (2) install methods: # # Method 1: # Download the .deb and install using DPKG # Download the required .deb file using a web browser $ firefox https://code.visualstudio.com/docs/?dv=linux64_deb # # Method 2: # Import the repository package GPG signing key, # and use Debian's APT to install the package, which # ensures that it will be subject to regular functional & security updates # In this example, I will use Method 2 # Change to Downloads directory $ cd ~/Downloads # Import the Microsoft GPG signing key $ wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > packages.microsoft.gpg # Backup the 'sources.list' file $ sudo cp -v /etc/apt/sources.list /etc/apt/sources.list.bak # Install the Microsoft GPG signing key $ sudo install -o root -g root -m 644 packages.microsoft.gpg /etc/apt/trusted.gpg.d/ # Modify the APT SOURCES_LIST $ sudo sh -c 'echo "deb [arch=amd64,arm64,armhf signed-by=/etc/apt/trusted.gpg.d/packages.microsoft.gpg] https://packages.microsoft.com/repos/code stable main" > /etc/apt/sources.list.d/vscode.list' # Update the APT package cache $ sudo apt update # Install apt-transport-https $ sudo apt install apt-transport-https # Update the APT package cache $ sudo apt update # Install VS Code, using either of the following commands: $ sudo apt install code # Option 1 $ sudo apt install code-insiders # Option 2 # Current VS Code (code) VERSION $ code --version 1.54.1 f30a9b73e8ffc278e71575118b6bf568f04587c8 x64 # Test it works directly from the command line $ code # Test from System Menu XFCE >> Applications >> Development >> Visual Studio Code
# Install the Daml Software Development Kit (SDK) # Visit the correct page using your web browser $ firefox https://docs.daml.com/getting-started/installation.html # There are two (2) install methods: # # Method 1 [Automatic installation & configuration]: # https://docs.daml.com/getting-started/installation.html # To install the SDK on Mac or Linux, do this: $ curl -sSL https://get.daml.com/ | sh # Note: The installer will setup the PATH variable for you. In order # for it to take effect, you will have to log out and log in again. # # Method 2 [Manual installation & configuration]: # Download the compressed tarball, verify the associated signature, # extract and manually execute the install script. # Navigate to https://github.com/digital-asset/daml/releases $ firefox https://github.com/digital-asset/daml/releases # Confirm there is a valid security certificate for this domain # In this instance, I will use Daml ver. 1.11.1, which is located at # https://github.com/digital-asset/daml/releases/tag/v1.11.1 # Just after the Release Notes is a section titled 'Assets' # There are two (2) files relating to Linux that we will need, the first # is the actual compressed archive and the second is the GPG signing key(?) # https://github.com/digital-asset/daml/releases/download/v1.11.1/daml-sdk-1.11.1-linux.tar.gz # https://github.com/digital-asset/daml/releases/download/v1.11.1/daml-sdk-1.11.1-linux.tar.gz.asc # Next, download these two (2) files into '~/Downloads' # Change to Downloads directory $ cd ~/Downloads $ wget https://github.com/digital-asset/daml/releases/download/v1.11.1/daml-sdk-1.11.1-linux.tar.gz $ wget https://github.com/digital-asset/daml/releases/download/v1.11.1/daml-sdk-1.11.1-linux.tar.gz.asc To verify the package signature, you will need the GnuPG (gpg) package # Check if it is installed $ gpg --version gpg (GnuPG) 2.2.12 libgcrypt 1.8.4 Copyright (C) 2018 Free Software Foundation, Inc. ... If there is no output from this command, then likely GnuPGP is not installed. If so, install the 'GnuPGP' package. # Update APT package cache $ sudo apt update $ sudo apt install gpg # Verify successful installation $ gpg --version gpg (GnuPG) 2.2.12 libgcrypt 1.8.4 Copyright (C) 2018 Free Software Foundation, Inc. ... Now that GnuPG is correctly installed, you can verify the signature, after importing the Digital Asset Security Public Key into your keychain. # Import the package key $ gpg --keyserver pool.sks-keyservers.net --search 4911A8DFE976ACDFA07130DBE8372C0C1C734C51 gpg: data source: http://xxx.xxx.xxx.xxx:xxxxx [Note #1] (1) Digital Asset Holdings, LLC <email@example.com> [Note #2] 2048 bit RSA key E8372C0C1C734C51, created: 2019-05-16, expires: 2021-05-15 [Note #3] Keys 1-1 of 1 for "4911A8DFE976ACDFA07130DBE8372C0C1C734C51". Enter number(s), N)ext, or Q)uit > 1 gpg: /home/quid/.gnupg/trustdb.gpg: trustdb created gpg: key E8372C0C1C734C51: public key "Digital Asset Holdings, LLC <firstname.lastname@example.org>" imported gpg: Total number processed: 1 gpg: imported: 1 # [Note]: The IP address of this keyserver is concealed as this forum is publically # indexible, and in my mind, this would present an unnecessary attack vector. # If any of the details in [Note #2] or [Note #3] are different, contact Digital Asset # Holdings, LLC immediately. # Ensure that you are still in the Downloads directory $ pwd /home/quid/Downloads $ ls -al total 431368 drwxr-xr-x 2 quid quid 4096 Mar 8 18:05 . drwxr-xr-x 19 quid quid 4096 Mar 8 15:48 .. -rw-r--r-- 1 quid quid 441701989 Mar 4 09:14 daml-sdk-1.11.1-linux.tar.gz -rw-r--r-- 1 quid quid 473 Mar 4 09:14 daml-sdk-1.11.1-linux.tar.gz.asc -rw-r--r-- 1 quid quid 641 Mar 8 15:40 packages.microsoft.gpg # Now that the key has been successfully imported and verified, use GnuPG to verify # that the package that you downloaded was in fact, signed by the new key. $ gpg --verify daml-sdk-1.11.1-linux.tar.gz.asc gpg: assuming signed data in 'daml-sdk-1.11.1-linux.tar.gz' gpg: Signature made Thu 04 Mar 2021 09:14:21 NZDT gpg: using RSA key E8372C0C1C734C51 gpg: Good signature from "Digital Asset Holdings, LLC <email@example.com>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4911 A8DF E976 ACDF A071 30DB E837 2C0C 1C73 4C51 [Note]: This warning indicates that GnuPG has not been instructed to trust this key. [Note]: Regardless of the warning, the key has been verified as having signed the package. # Now that I have confidence in the origin and security of the package, it can be installed # Identify the correct file $ ls *.tar.gz daml-sdk-1.11.1-linux.tar.gz $ tar xzf daml-sdk-1.11.1-linux.tar.gz # Change directory into the new 'sdk-1.11.1' directory $ cd sdk-1.11.1 # Execute the installation script ./install.sh Installing SDK release from directory. Add DAML Assistant executable to your PATH (in .bash_profile)? [Yes] No Yes Your /home/quid/.bash_profile has been updated. You need to logout and login again for the change to take effect. Bash completions installed for DAML assistant. Zsh completions installed for DAML assistant. To use them, add '~/.daml/zsh' to your $fpath, e.g. by adding the following to the beginning of '~/.zshrc' before you call 'compinit': fpath=(~/.daml/zsh $fpath) # Update your USER_PROFILE by either logging out & back in, # or source the USER_PROFILE in the current terminal. $ source ~/.bash_profile # Verify the Daml installation has been successful $ daml version SDK versions: 1.10.0 (not installed) 1.10.2 (default SDK version for new projects) # [Note]: Adding the Daml Assistant executable to ~/.bash_profile did not # work on this system. Whereas adding it to ~/.bashrc did.
- Convert tutorial into commands, with minor headings
- Convert tutorial into commands, with no headings ← 20%
- Adapt into Bash script for Debian/Variants ← 20%
- Convert Bash script into Haskell program for Debian/Variants
- Repeat for x86_32/64 and ARMv5/7 arch Not supported
- Get a life
If there is any feedback, please reply to this message thread.