Move extension download from Settings to Terminals page
Makes more sense there — creating a terminal key and installing the extension are the same setup workflow, not two unrelated things on separate pages. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
fbd1443e35
commit
67def8ac19
2 changed files with 17 additions and 18 deletions
|
|
@ -1,6 +1,6 @@
|
|||
import { useEffect, useState } from 'react'
|
||||
import { RefreshCw, KeyRound, Ban, Trash2, Copy } from 'lucide-react'
|
||||
import { fetchTerminals, createTerminal, revokeTerminal, deleteTerminal } from '../api'
|
||||
import { RefreshCw, KeyRound, Ban, Trash2, Copy, Download } from 'lucide-react'
|
||||
import { fetchTerminals, createTerminal, revokeTerminal, deleteTerminal, extensionDownloadUrl } from '../api'
|
||||
import type { Terminal } from '../types'
|
||||
|
||||
export default function Terminals() {
|
||||
|
|
@ -69,6 +69,19 @@ export default function Terminals() {
|
|||
(hotel-owned hardware gets a device credential, same trust tier as the tablets themselves).
|
||||
</p>
|
||||
|
||||
<div className="card" style={{ marginBottom: 20 }}>
|
||||
<div style={{ fontWeight: 600, marginBottom: 6 }}>Chrome Extension</div>
|
||||
<p className="field-hint" style={{ marginBottom: 10 }}>
|
||||
Not published anywhere yet, so it needs installing manually on each reception PC: download,
|
||||
unzip, then <code>chrome://extensions</code> → enable Developer mode → Load unpacked →
|
||||
select the unzipped folder. It'll need a terminal key from below to actually authorize
|
||||
pushes — create one first if you haven't already.
|
||||
</p>
|
||||
<a className="btn" href={extensionDownloadUrl()} style={{ display: 'inline-flex', alignItems: 'center', gap: 6, textDecoration: 'none' }}>
|
||||
<Download size={16} strokeWidth={1.75} /> Download Extension (.zip)
|
||||
</a>
|
||||
</div>
|
||||
|
||||
{error && <div className="error-banner">{error}</div>}
|
||||
|
||||
{revealedKey && (
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue