1.5. Developer Install (Console Isolated)¶
This console install (aka --isolated
) guide provides a developer focused installation process that runs DRP from the Linux or MacOS command line instead of systemd.
This sub-install guide is a Quick Start Guide supplement designed for code and operations development with Digital Rebar. The command line install is especially useful for debugging and rapid testing where a minimial instalation footprint is required.
Please consult other installation paths for more details:
Quick Start Guide is a basic systemd install for new users
Production Install details more complex installs including offline/airgap.
Production Install details more complex installs including offline/airgap.
Container Install (Docker/Podman) for trial users minimizing their install requirements
Cloud & VM Install (Non-PXE environments) is non-PXE / Cloud-Only installation process (no DHCP required)
Airgap Install for users installing on an airgapped system
Edge Lab with RPi is self-contained Digital Rebar inexpensive lab using Raspberry Pi computers.
Each of these environments requires careful setup up of your network environment and consideration with regard to competing DHCP services. The setup of these environments is outside the scope of this document.
You must install Digital Rebar to use it, there is no SaaS version. Why do I have to install Digital Rebar locally?
1.5.1. Preparation¶
Unlike the Quick Start Hardware, this guide expects that users to run Digital Rebar in their primary work environment. This makes it easy to monitor and reset the Digital Rebar endpoint.
This document refers to the Digital Rebar Provision Command Line Interface (CLI) for manipulating the dr-provision
service; however, the --isolated
installation does not install drpcli
automatically.
Please make sure your environment doesn’t have any conflicts or issues that might cause port conflicts (see Ports) or cause PXE booting to fail.
1.5.2. Install¶
To begin, execute the following commands in a shell or terminal:
mkdir drp ; cd drp
curl -fsSL get.rebar.digital/stable | bash -s -- install --isolated --version=tip
The command will pull the latest dr-provision
bundle and checksum from github, extract the files, verify prerequisites are installed, and create some initial directories and links.
The install script used by our installs has many additional options that are documented in its help and explored in other install guides.
Once you have Digital Rebar working in this fashion, you should be able to upgrade the endpoint by simply replacing the dr-provision
binary and restarting the process. The ability to quickly reset the environment is a primary benefit of this approach.
1.5.3. Manually Start Digital Rebar¶
Once the install has completed, your terminal should provide next steps similar to those below.
# Run the following commands to start up dr-provision in a local isolated way.
# The server will store information and serve files from the ./drp-data directory.
sudo ./dr-provision --base-root=`pwd`/drp-data |& tee log.out
1.5.4. Install RackN License¶
If you have obtained a RackN license file using the process from UX and License, then you can bypass this step in subsequent resets by uploading the rackn-license.json
file via the CLI.
drpcli contents upload rackn-license.json
1.5.5. Back to Regular Install¶
Once Digital Rebar is running in isolated mode, it is exactly the same as any other installation
1.5.6. Clean Up¶
Once you are finished exploring Digital Rebar Provision in isolated mode, the system can cleaned or reset by removing the directory containing the isolated install. In the previous sections, we used ‘’drp’’ as the directory containing the isolated install. Removing this directory will clean up the installed files.