Skip to content

Manual Installation

Fractum can be installed manually using Python virtual environments. This approach provides flexibility for developers and users who need more control over the installation process.

Installation Steps

1. Clone the Repository

git clone https://github.com/katvio/fractum.git
cd fractum
git checkout tags/v1.2.0

2. Bootstrap Your Environment

Choose the bootstrap script for your operating system:

chmod +x bootstrap-linux.sh && ./bootstrap-linux.sh

This script will: - Install required system tools (git, curl, wget, etc.) - Add deadsnakes PPA repository - Install Python 3.12.10 - Create a virtual environment - Install fractum in development mode

chmod +x bootstrap-macos.sh && ./bootstrap-macos.sh

This script will: - Install Xcode Command Line Tools - Install Homebrew (if not present) - Install pyenv - Install Python 3.12.10 - Create a virtual environment - Install fractum in development mode

  1. Open PowerShell as Administrator
  2. Set the execution policy for the current process: 
    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
    then say yes to everything (T)
  3. Run: 
    .\bootstrap-windows.ps1

This script will: - Install Python 3.12.10 (using winget or Chocolatey) - Create a virtual environment - Install fractum CLI on your machine

3. Activate the Virtual Environment

source .venv/bin/activate

.\.venv\Scripts\Activate.ps1

4. Verify Your Installation

python --version          # Should report Python 3.12.10
pip list                  # Should list fractum (editable mode)
fractum --help            # Show CLI usage

Using Fractum After Installation

Once installed, you can use Fractum directly from the command line. For detailed usage instructions and examples:

These guides cover both interactive and command-line modes, with examples for various scenarios and security considerations.

Troubleshooting

If you encounter issues during installation:

  1. Ensure you have the correct Python version installed (3.12.10)
  2. Check that you have permissions to create files in the current directory
  3. On Linux/macOS, verify that the bootstrap script has execute permissions
  4. On Windows, ensure PowerShell execution policy allows script execution