Environment
Conda Installation and Use
· β˜• 2 min read
1. Installing conda 1 2 3 wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh bash Miniconda3-latest-Linux-x86_64.sh rm -rf Miniconda3-latest-Linux-x86_64.sh However, Miniconda cannot be used for free at large-scale commercial deployments, so you can use Miniforge as a drop-in alternative. 1 2 wget "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh" bash Miniforge3-$(uname)-$(uname -m).sh 2. Changing the default configuration 2.1 Initializing the Shell Without initialization, activating an environment reports CondaError: Run 'conda init' before 'conda activate'.
The Definition of Application Runtime Under Multiple Environments
· β˜• 4 min read
1. Why We Need to Define the Application Runtime There are more runtime choices. Traditional application runtimes include physical machines, virtual machines, and cloud hosts. In the container era, the common runtimes are Docker and Kubernetes. These runtimes no longer present us with a single runtime choice. Application topologies are more complex.
Installing and Configuring Zsh on CentOS 7
· β˜• 1 min read
1. Install zsh 1 sudo yum install -y zsh 2. Install oh-my-zsh 1 sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)" It is recommended to set Zsh as the default shell. 3. Install Plugins 3.1 Install autojump 1 sudo yum install -y epel-release 1 sudo yum install -y autojump-zsh 3.2 Install zsh-autosuggestions 1 git clone git://github.
Installing and Configuring Homebrew on CentOS 7
· β˜• 4 min read
When installing packages on CentOS you usually have to hunt down all sorts of repositories; with Homebrew that hassle goes away. This article uses CentOS 7.6 β€” other system versions may differ. 1. Create a Non-root User Homebrew refuses to run as root, so a new user has to be created.
Installing a Java Development Environment on CentOS 7
· β˜• 2 min read
1. Compilation Error: java.nio.file.NoSuchFileException When compiling a Jenkins plugin, the following error is reported: 1 2 3 4 mvn package Compilation failure [ERROR] java.nio.file.NoSuchFileException: /root/java/target/classes/META-INF/annotations/hudson.Extension It turns out that Maven uses JAVA_HOME rather than PATH, so it cannot find a Java runtime. Java 11 does not work either β€” only Java 1.