This guide shows per example the installation of the Java SDK versions 8
(LTS, already installed) and 11
(LTS).
apt --names-only search "openjdk-.*jre$"
> Sorting... Done
#!/bin/bash | |
# Step 1: Confirm the path to the .AppImage file | |
APPIMAGE_PATH="$HOME/Applications/cursor-0.8.6.AppImage" | |
echo "Using AppImage path: $APPIMAGE_PATH" | |
# Step 1.5: Download the Cursor logo | |
ICON_PATH="$HOME/.local/share/icons/cursor-icon.svg" | |
curl -o $ICON_PATH "https://www.cursor.so/brand/icon.svg" | |
echo "Downloaded logo to: $ICON_PATH" |
#!/bin/bash | |
# Step 1: Confirm the path to the .AppImage file | |
APPIMAGE_PATH="$HOME/Applications/cursor-0.8.6.AppImage" | |
echo "Using AppImage path: $APPIMAGE_PATH" | |
# Step 1.5: Download the Cursor logo | |
ICON_PATH="$HOME/.local/share/icons/cursor-icon.svg" | |
curl -o $ICON_PATH "https://www.cursor.so/brand/icon.svg" | |
echo "Downloaded logo to: $ICON_PATH" |
Vault secures, stores, and tightly controls access to tokens, passwords, certificates, API keys, and other secrets in modern computing. Vault is primarily used in production environments to manage secrets. Vault is a complex system that has many different pieces. There is a clear separation of components that are inside or outside of the security barrier. Only the storage backend and the HTTP API are outside, all other components are inside the barrier.
Figure 1: Architecture of Vault and Spring App (Click to enlarge)
The storage backend is untrusted and is used to durably store encrypted data. When the Vault server is started, it must be provided with a storage backend so that data is available across restarts. The HTTP API similarly must be started by the Vault server on start so that clients can interact with it.
cd /home/<user>/ | |
sudo apt-get install unzip | |
wget https://dl.google.com/android/repository/sdk-tools-linux-4333796.zip | |
unzip sdk-tools-linux-4333796.zip -d Android | |
rm sdk-tools-linux-4333796.zip | |
sudo apt-get install -y lib32z1 openjdk-8-jdk | |
export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 | |
export PATH=$PATH:$JAVA_HOME/bin | |
printf "\n\nexport JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64\nexport PATH=\$PATH:\$JAVA_HOME/bin" >> ~/.bashrc | |
cd Android/tools/bin |
It sometimes happen you need change code on a machine from which you cannot push to the repo.
You’re ready to copy/paste what diff
outputs to your local working copy.
You think there must be a better way to proceed and you’re right. It’s a simple 2 steps process:
1. Generate the patch:
git diff > some-changes.patch
pipeline { | |
agent { | |
label 'agentId' //The id of the slave/agent where the build should be executed, if it doesn't matter use "agent any" instead. | |
} | |
triggers { | |
cron('H */8 * * *') //regular builds | |
pollSCM('* * * * *') //polling for changes, here once a minute | |
} |
Sub Main(args) | |
url$ = "file:///index.html" | |
if args <> invalid and args.Count() > 0 then | |
url$ = args[0] | |
end if | |
print "url = ";url$ | |
DoCanonicalInit() |