Olikub is my Omakase (chef's choice) setup, based on DHH's Omakub, with my own customizations and tweaks. To install it on a fresh Ubuntu 26.04+ system, run:
wget -qO- https://raw.githubusercontent.com/olipet284/olikub/main/boot.sh | bashChoose another checkout location with --directory:
wget -qO- https://raw.githubusercontent.com/olipet284/olikub/main/boot.sh | bash -s -- --directory "$HOME/repos/olikub/main"Without an option, Olikub uses ~/.local/share/olikub by default and offers a
directory prompt when run in a terminal. Running boot.sh from an existing
Olikub main checkout reuses that checkout. Existing paths must be the official
repository on main; Olikub does not delete or replace them.
Olikub turns a fresh Ubuntu installation into a fully configured, modern web development system with a single command.
Use feature branches or worktrees for development; keep the runtime checkout on
the official main branch. The bootstrap and self-updater use main, so merge
changes there before expecting a normal install or update to include them.
Create a separate worktree for a feature with:
git worktree add ../olikub-feature -b feat/my-change mainOptional applications live in apps/<kind>/<topic>/<app>.sh, where kind is
cli, tui, or gui, and topic groups apps by use (coding-harness,
browser, multiplexer, ...). Each app file defines APP_NAME,
APP_DESCRIPTION, APP_DEFAULT, and the functions app_installed,
app_install, and app_uninstall. app_installed decides whether the app
appears under Install or Uninstall; when it is omitted, Olikub checks APP_BIN
(or the file name) on PATH.
Apps with APP_DEFAULT=1 are installed by install.sh. Everything else is
available from the Olikub menu. To inspect or manage a single app directly:
olikub apps
olikub apps install lazygit
olikub apps uninstall lazygitUninstall removes programs but keeps user configuration by default.
Open the Olikub app, press Super+Shift+T, or run olikub theme in a shell to
choose a theme. Btop uses the
stable olikub theme name; changing palettes replaces
~/.config/btop/themes/olikub.theme without rewriting the rest of
~/.config/btop/btop.conf. On upgrade, Olikub migrates an existing regular
Btop config from an Olikub theme name to olikub; config symlinks are left
alone.
GNOME custom shortcuts are loaded from
${XDG_CONFIG_HOME:-$HOME/.config}/olikub/hotkeys/*.sh. Olikub creates a sample
file if the directory is missing and leaves existing user directories alone.
The files use add_custom_keybinding 'Name' 'command' '<Binding>' and can be
symlinked from a dotfiles repository.
Olikub builds on Omakub. See omakub.org for the upstream introduction and documentation, and Omakub extensions for community add-ons.
Olikub is released under the MIT License.