fluorite / install

Get running in five minutes

Fluorite ships as plain promoted artifacts — a browser binary and its runtime files. No installer, no services, no surprises.

Steps

  1. DownloadGrab the current artifact bundle from the download server. Pick the newest versioned directory.
  2. VerifyCheck the SHA-256 checksums published alongside the artifacts against what you downloaded.
  3. ExtractUnpack into its own directory — for example ~/apps/fluorite/154.0.8021.1/. Versioned directories make upgrades painless.
  4. LaunchStart it with a dedicated profile outside the application directory (see below).
  5. Verify againOpen chrome://version inside the browser and confirm the version matches the tag you downloaded.

The one rule: keep data out of the tree

Fluorite's build directories are disposable by design. Your profile should not live anywhere near them. Launch with an explicit user data directory:

$ mkdir -p ~/.local/share/fluorite/profile
$ ~/apps/fluorite/154.0.8021.1/chrome \
    --user-data-dir=$HOME/.local/share/fluorite/profile

This is the same discipline the build pipeline follows for itself — binaries are replaceable, your browsing history, sessions and passwords are not. It also means you can delete or swap a Fluorite install without ever touching your data.

Tip: create a desktop launcher once with the --user-data-dir flag baked in, so every start is correct by default.

Upgrades

  • Extract the new version next to the old one — both can coexist under ~/apps/fluorite/<version>/.
  • Point your launcher at the new binary; your --user-data-dir stays exactly where it is.
  • Once you're happy, delete the old version's directory. That's the entire migration path.
Go to downloads Questions?