* Add rate limits for device authed endpoints
* Fix lint
* Add missing test
* Fix test
* Increase the quota for desktop endpoints
* Add comment about quota
Related to #6364 and #6363, this:
- Adds a new Docker image, `fleetdm/fleetctl` equipped with all necessary dependencies to build Fleet-osquery binaries for all platforms
- Modifies the package generation logic to special case this scenario via an environment variable `FLEETCTL_NATIVE_TOOLING`
- Adds a new GitHub workflow to test this
There are more details in the README, but part of the special-casing logic is in place to output the binaries to a folder named `build` when they are run with `FLEETCTL_NATIVE_TOOLING`, this is so we can persist the binary generated by the docker container via a bind mount:
```bash
docker run -v "$(pwd):/build" fleetdm/fleetctl package --type=msi
```
To test this changeset, I have generated packages for all platforms, both via the new Docker image and via the classic `fleetctl package`.
* state of device management blog post
- Article to help promote the report
- Needed before merge: "Reports" article category
* add report category and update routes
* Update state-of-device-management.md
I reworded part of this to make it easier to read. Let me know if I can be of any more help. :)
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
Co-authored-by: Tim Kern <tim@fleetdm.com>
* Edits to Hetzner deployment guide
Main nav:
- I added a link to the article from the main nav
Edits to the article:
- Changed up some of the language to make it consistent with our existing deployment guides.
- Re-arranged the intro section for clarity
- Changed the thumbnail image
Style fixes:
- reduced margin top and bottom for articles H3
* Update deploy-fleet-on-hetzner-cloud.md
- To reduce duplicated content and make this easier to maintain, I suggest removing Fleet setup instructions, and linked to the relevant sections of the docs instead.
* Update deploy-fleet-on-hetzner-cloud.md
Word changes
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update articles/deploy-fleet-on-hetzner-cloud.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update deploy-fleet-on-hetzner-cloud.md
Update script to latest version of Fleet.
* small edit
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
Co-authored-by: Eric <eashaw@sailsjs.com>
* Add server support for Fleet Sandbox demo login
This adds an endpoint `/api/latest/fleet/demologin` that provides a
redirect for the fleetdm.com portion of Fleet Sandbox to automatically
log in a user. The username and password must be provided as form
values. The endpoint is only enabled if `FLEET_DEMO=1` is set in the
server environment.
This was tested locally with the following HTML served by `python3 -m
http.server`, and the Fleet server running with `FLEET_DEMO=1
./build/fleet serve --dev`:
```
<!DOCTYPE html>
<body>
<form
method="post"
action="https://localhost:8080/api/latest/fleet/demologin"
id="demologin"
>
<input type="hidden" name="email" value="admin@example.com" />
<input type="hidden" name="password" value="admin123123#" />
<input type="submit"/>
</form>
<script type="text/javascript">
document.forms["demologin"].submit();
</script>
</body>
</html>
```
For Fleet sandbox purposes, the `action` should be set to the correct
hostname for the sandbox instance, while the `email` and `password`
should be set to the same credentials that were provided when creating
the instance.
* lucas comments
* Add integration tests
* Fix status codes and add comments
Co-authored-by: Martin Angers <martin.n.angers@gmail.com>
Tomas Touceda