Getting Started
Prerequisites
No dependencies. For building packages see the Build Packages section
Get Luet
From release
Just grab a release from the release page on GitHub. The binaries are statically compiled.
Or you can install Luet also with a single command:
curl https://luet.io/install.sh | sudo sh
Building Luet from source
Requirements:
- Golang installed in your system.
- make
$> git clone https://github.com/mudler/luet
$> cd luet
$> make build # or just go build
Install it as a system package
In the following section we will see how to install luet with luet itself. We will use a transient luet version that we are going to throw away right after we install it in the system.
# Get a luet release. It will be used to install luet in your system
wget https://github.com/mudler/luet/releases/download/0.8.3/luet-0.8.3-linux-amd64 -O luet
chmod +x luet
# Creates the luet configuration file and add the luet-index repository.
# The luet-index repository contains a collection of repositories which are
# installable and tracked in your system as standard packages.
cat > .luet.yaml <<EOF
repositories:
- name: "mocaccino-repository-index"
description: "MocaccinoOS Repository index"
type: "http"
enable: true
cached: true
priority: 1
urls:
- "https://raw.githubusercontent.com/mocaccinoOS/repository-index/gh-pages"
EOF
# Install the official luet repository to get always the latest luet version
./luet install repository/luet
# Install luet (with luet) in your system
./luet install system/luet
# Remove the temporary luet used for bootstrapping
rm -rf luet
# Copy over the config file to your system
mkdir -p /etc/luet
mv .luet.yaml /etc/luet/luet.yaml
Configuration
Luet stores its configuration files in /etc/luet
. If you wish to override its default settings, create a file /etc/luet/luet.yaml
.
A example of a luet.yaml
file can be found here.
There are a bunch of configuration settings available, but the most relevant are:
logging:
color: true # Enable/Disable colored output
enable_emoji: true # Enable/Disable emoji from output
general:
debug: false # Enable/Disable debug
system:
rootfs: "/" # What's our rootfs. Luet can install packages outside of "/"
database_path: "/var/db/luet" # Where to store DB files
database_engine: "boltdb"
tmpdir_base: "/var/tmp/luet" # The temporary directory to be used
Adding repositories
To add repositories, you can either add a repositories
stanza in your /etc/luet/luet.yaml
or either add one or more yaml files in /etc/luet/repos.conf.d/
.
Configuration in /etc/luet/luet.yaml
logging:
color: true # Enable/Disable colored output
enable_emoji: true # Enable/Disable emoji from output
general:
debug: false # Enable/Disable debug
system:
rootfs: "/" # What's our rootfs. Luet can install packages outside of "/"
database_path: "/var/db/luet" # Where to store DB files
database_engine: "boltdb"
tmpdir_base: "/var/tmp/luet" # The temporary directory to be used
repositories:
- name: "some-repository-name" # Repository name
description: "A beautiful description"
type: "http" # Repository type, disk or http are supported (disk for local path)
enable: true # Enable/Disable repo
cached: true # Enable cache for repository
priority: 3 # Cache priority
urls: # Repository URLs
- "...."
Configuration in /etc/luet/repos.conf.d/
A repository file can be for example:
name: "..." # Repository name
description: "..."
type: "http" # Repository type, disk or http are supported (disk for local path)
enable: true # Enable/Disable repo
cached: true # Enable cache for repository
priority: 3 # Cache priority
urls: # Repository URLs
- "..."
There is available a collection of repositories, which is containing a list of repositories that can be installed in the system with luet install
.
If you installed Luet from the curl command, you just need to run luet search repository
to see a list of all the available repository, and you can install them singularly by running luet install repository/<name>
. Otherwise, add the repository stanzas you need to /etc/luet/luet.yaml
.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.