Videos? Several in the [`screenshots`](./screenshots) directory.
Videos available. Run `ls | grep mp4` in the [`screenshots`](./screenshots) directory to access them.
## Installation
## Basic Installation
Assumes basic knowledge of command line, git and file system management.
1. Copy repository source code.
2. Run `make install` to move `bin/archuro` to `/usr/local/bin`.
3. Run `archuro init` to install build essentials. Add `-S` to proceed with GNU Stow.
4. Finally, run `archuro install` to install dependencies.
To uninstall run `make uninstall` from project root directory.
Repeat steps 2-3 on an [Extended Build](#extended-builds) of Arch Linux to share your dotfiles.
To uninstall run `make uninstall` from project root.
## Usage
Run `archuro --help` after installation for usage instructions. To get a disposabe Arch Linux container run `archuro tty`. To get a reusable container run `archuro save && archuro run`. Run `archuro ps` to view running containers and `archuro attach` to attach a tty otherwise.
Once you've stowed with `archuro init -S` you may continue using `brew bundle` just like you normally would and Archuro will help you keep track of your dependencies.
Once dotfiles are stowed with `archuro init -S` a simple `archuro update` will update configured applications.
## VSCode Setup
## Homebrew
Archuro assumes all macOS development dependencies are managed using a manifest file known as a `Brewfile`. The Brewfile keeps track dependencies and may also influence Homebrew how to tweak app installations specific for an environment. The manifest lives in `stow/dot-Homebrew` file which becomes symlinked to `~/.Brewfile` for use by the current user during `archuro init` using the `-S` flag.
## VSCode
Settings and extensions are kept in the `stow/dot-vscode` directory under the project root:
@ -64,7 +79,11 @@ For more info on extensions see [User and Workspace settings](https://vscode.rea
## Extended builds
Run `archuro save` to build and tag an `extended` image. Update `Dockerfile` to customize build as desired. Rerun `archuro save` anytime to tag a new image. View all `archlinux` images by running `archuro ls`.
Spinning up a disposable Arch Linux tty is great. But throwing away work during repetitive tasks isn't. For this reason Archuro provides a method for persisting state and heavily caching development dependencies on Arch Linux using Docker.
Run `archuro save` to build and tag an `extended` Arch Linux image. Think of it as your own custom build of the OS and update the `Dockerfile` provided to customize as desired. Rerun `archuro save` anytime to build and tag a new docker image (or use `docker` cli directly).
View tagged Arch Linux builds by running `archuro ls`.