mirror of https://github.com/fleetdm/fleet synced 2026-04-21 21:47:20 +00:00

Enroll hosts docs improvements (#14862 )

Summary:
- Enroll hosts page refinement
- Since page was too long and had a lot of content I did following:
    - Moved most important sections to the top
- Did some changes to make things more consistent, when possible having
UI and CLI sections with steps (ordered list)
- Moved `Add hosts with plain osquery` to contributor docs, since I
learned this approach is used just by couple of Fleet customers, and we
don't advise this as best practice anymore
- Added overview (table of contents) on the top to make easier to
navigate through the page
- Moved some technical (advanced) topics into separate section on the
bottom of the page

---------

Co-authored-by: Noah Talerman <noahtal@umich.edu>
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Co-authored-by: Rachael Shaw <r@rachael.wtf>

2023-11-20 19:39:41 +01:00

2.6 KiB

Raw Blame History

Deploying ChromeOS test extensions to enrolled Chromebooks

As part of validating any ChromeOS extension, run this process to force-install the extension on Chromebooks for debugging.

Build the extension

Bump the extension version

Modify the version field at the top of the package.json file in ee/fleetd-chrome

Update the version in updates.xml to match the package.json version.

Build the distribution folder

cd ee/fleetd-chrome
yarn run build

Pack the extension

Navigate to chrome://extensions in your Chrome web browser.

In developer mode, select "Pack extension"
Set "Extension root directory" to the newly-created ee/fleetd-chrome/dist folder
Press "Pack extension" (key name will auto-generate)

Load the new extension to the Chrome web browser

Open the finder app
Drag and drop the ee/fleetd-chrome/dist.crx binary file on top of a Chrome web browser window
Press "Add Extension"
Verify that the extension works
Copy the appid for later use

Run a local server to make the new extension available

Edit update.xml

Open ee/fleetd-chrome/update.xml in your text editor and modify:

The version.
The appid (copied previously). This will only be done for debug versions. For production, we will keep the original ID we have.

Create the server

cd ee/fleetd-chrome
python3 -m http.server

Verify that it works by going to http://localhost:8000 to see the files.

cd ee/fleetd-chrome
npm install -g localtunnel
lt --port 8000 --subdomain test-new-tables

In your web browser go to: http://test-new-tables.loca.lt
Click the hazard link on item number 1 (below the big button "Click To Submit"). From the new page, copy the IP and paste it into the previous page in the window.
Open ee/fleetd-chrome/update.xml in your text editor and modify the codebase to use the newly created URL (in this example: http://test-new-tables.loca.lt/dist.crx).

Deploy the extension using Google Admin

Follow the instructions here for installing the fleetd Chrome extension, with the following modifications:

Select the "ChromeOSTesting" group.

For "Extension ID", use the ID previously copied.

For "Installation URL", use http://test-new-tables.loca.lt/updates.xml.

Remove the filters (the filters with our appid).

For "Policy for extensions", copy over the JSON from the original extension.

2.6 KiB Raw Blame History