Documentation
/
Guides & Tutorials
/
Multi-Device Setup

Setting Up FileFortress on Multiple Devices
Sync configuration and manage authentication across devices

What You'll Learn
  • Device registration strategies
  • Password vs key file authentication
  • Syncing configuration between devices
  • Best practices for multi-device setups
  • Troubleshooting common issues

Overview

FileFortress supports running on multiple devices simultaneously. Each device maintains its own local database and file index, but they all connect to the same cloud storage accounts. This guide covers best practices for setting up and managing FileFortress across multiple devices.

Authentication Strategies

Option 1: Automatic Encryption (Machine-Specific)

Best for: Personal devices where you don't need to access the same database from multiple machines.

How it works: Each device has its own encrypted database using machine-specific encryption.

Setup:

filefortress init

Pros: No password to remember, automatic encryption

Cons: Each device has independent database, no data sharing between devices

Option 2: Custom Password with Key File

Best for: Accessing the same database from multiple devices.

How it works: Use a custom password and key file that you can copy to other devices.

Setup on first device:

filefortress --password YourSecurePassword init --create-key-file ~/filefortress.key

Setup on additional devices:

  1. Copy the key file to the new device
  2. Run: filefortress --key-file ~/filefortress.key init

Pros: Share database across devices, consistent search results

Cons: Must manage password/key file securely

Multi-Device Setup Workflow

Step 1: Choose Your Strategy

Independent Databases

Each device has its own database

Simple setup
No password management
Separate indexes per device

Shared Database

Same database across all devices

Consistent search results
Shared configuration
Requires password/key management

Step 2: Set Up First Device

For Independent Databases:

filefortress init
filefortress remotes add gdrive
filefortress remotes scan "Google Drive"

For Shared Database:

filefortress --password YourSecurePassword init --create-key-file ~/filefortress.key
filefortress --key-file ~/filefortress.key remotes add gdrive
filefortress --key-file ~/filefortress.key remotes scan "Google Drive"

Step 3: Set Up Additional Devices

For Independent Databases:

Simply repeat the setup on each device:

filefortress init
filefortress remotes add gdrive
filefortress remotes scan "Google Drive"

For Shared Database:

Copy the key file and use it:

# Copy ~/filefortress.key from first device
filefortress --key-file ~/filefortress.key init
filefortress --key-file ~/filefortress.key remotes add gdrive
filefortress --key-file ~/filefortress.key remotes scan "Google Drive"

Key File Management

Secure Storage

Store key files in your home directory with restricted permissions
Use cloud storage (encrypted) to sync key files between devices
Keep backup copies in secure locations
Never commit key files to version control

Setting Permissions (Linux/Mac)

chmod 600 ~/filefortress.key

Keeping Devices Synchronized

Scan Strategy

Option A: Scan on all devices

Each device scans independently. Good for ensuring all devices have up-to-date indexes.

# Run on each device
filefortress remotes scan --all

Option B: Scan on primary device only

Only scan on your primary device. Other devices use the shared database.

Note: Only works with shared database strategy.

Recommended Scan Schedule

Device Type Scan Frequency Rationale
Primary Desktop Daily Keeps index fresh for all devices
Laptop Weekly or as needed Balance between freshness and battery life
Server Hourly (automated) Always up-to-date for team access

Common Scenarios

Scenario 1: Laptop + Desktop (Personal Use)

Recommendation: Shared database with key file

Setup:

  1. Set up desktop with password and key file
  2. Copy key file to laptop (use secure cloud storage or USB)
  3. Initialize laptop with same key file
  4. Scan from whichever device you use most

Scenario 2: Multiple Team Members

Recommendation: Independent databases per person

Setup:

  1. Each team member gets their own registration code
  2. Each person sets up their own device independently
  3. Connect to shared cloud storage accounts (if permissions allow)
  4. Each person maintains their own scan schedule

Scenario 3: Home + Work Computer

Recommendation: Independent databases (security)

Setup:

  1. Use automatic encryption on both devices
  2. Connect to different cloud storage accounts on each
  3. Keep work and personal data separate

Troubleshooting

Key file not working on new device

Solutions:

  • Verify key file was copied correctly (check file size)
  • Ensure file permissions are correct (600 on Linux/Mac)
  • Try using --password directly instead of key file
Search results differ between devices

Causes:

  • Using independent databases (expected behavior)
  • One device hasn't scanned recently
  • Different remotes connected on each device

Solution: Run filefortress remotes scan --all on both devices

Forgot password for shared database

Solution:

  • If you have key file on any device, you can still access
  • If no key file exists, you'll need to reinitialize (loses local database)
  • Your cloud files are safe - only local database is affected

Best Practices

Use descriptive device names during init (e.g., "John-Laptop", "Office-Desktop")
Keep key files backed up in multiple secure locations
Use strong passwords for shared database setups
Scan regularly on at least one device
Document which device is your "primary" for scanning
Test key file access before removing from original device

Related Resources

Encryption Guide
Understanding encryption options
View Guide
init Command
Device initialization reference
View Reference
Automation Guide
Automate scanning across devices
View Guide