61 lines
3.1 KiB
Markdown
61 lines
3.1 KiB
Markdown
|
|
|
|
**Horde** is a set of services supporting workflows Epic uses to develop Fortnite,
|
|
Unreal Engine, and other titles.
|
|
|
|
It is provided with full source code to Unreal Engine licensees, and is meant for licensees to host and configure
|
|
themselves. We provide pre-built Docker images for deployment on Linux, and an MSI installer for Windows.
|
|
|
|
Horde offers the following functionality, most of which may be enabled or disabled independently:
|
|
|
|
* **[Remote Execution](Docs/Tutorials/RemoteCompilation.md)**: Functionality to offload compute work to other machines,
|
|
including C++ compilation with **Unreal Build Accelerator**.
|
|
* **[Build Automation (CI/CD)](Docs/Tutorials/BuildAutomation.md)**: A build automation system designed for teams working
|
|
with large Perforce repositories.
|
|
* **[Test Automation](Docs/Config/AutomationHub.md)**: A frontend for querying automation results across streams and
|
|
projects, integrated with AutomationTool and Gauntlet.
|
|
* **[Studio Analytics](Docs/Tutorials/Analytics.md)**: Receives telemetry from Unreal Editor, and shows charts for
|
|
key workflow metrics.
|
|
* **[UnrealGameSync Metadata Server](Docs/Config/UgsMetadataServer.md)**: Various features for teams using
|
|
UnrealGameSync, including build status reporting, comment aggregation, and crowdsourced build health functionality.
|
|
* **[Mobile/Console Device Management](Docs/Tutorials/DeviceManager.md)**: Tools for managing a farm of development kits and
|
|
mobile devices.
|
|
|
|
Read more about our [goals and philosophy](Docs/Goals.md), or check out the [FAQ](Docs/Faq.md).
|
|
|
|
## Status
|
|
|
|
Horde is considered production ready for Unreal Engine licensees.
|
|
|
|
See also: [Feature Status](Docs/Features.md)
|
|
|
|
## Getting Started
|
|
|
|
* **[Install the Horde agent](Docs/Tutorials/InstallHorde.md)**
|
|
* **[Enable remote C++ compilation](Docs/Tutorials/RemoteCompilation.md)**
|
|
* **[Enable remote shader compilation](Docs/Tutorials/RemoteShaderCompilation.md)**
|
|
* **[Set up build automation](Docs/Tutorials/BuildAutomation.md)**
|
|
* **[Enable test automation with Gauntlet](Docs/Tutorials/TestAutomation.md)**
|
|
* **[Get telemetry and analytics for your team](Docs/Tutorials/Analytics.md)**
|
|
* **[Work with mobile and console devices](Docs/Tutorials/DeviceManager.md)**
|
|
* **[Install UnrealGameSync and distribute Unreal Editor to your team](Docs/Tutorials/UnrealGameSync.md)**
|
|
* **[Enable authentication](Docs/Tutorials/Authentication.md)**
|
|
|
|
## Reference
|
|
|
|
Horde's reference documentation is divided into sections by target audience:
|
|
|
|
* [**Deploying Horde**](Docs/Deployment.md)
|
|
* Information on the architecture and components making up Horde, and best practices for deploying them.<br>
|
|
**Audience:** IT, sysadmins, coders intending to modify Horde.
|
|
* [**Configuring and Operating Horde**](Docs/Config.md)
|
|
* Describes how to set up and administer Horde.<br>
|
|
**Audience:** Build/dev ops teams, admins.
|
|
* [**Horde Internals**](Docs/Internals.md)
|
|
* Describes how to build and modify Horde and its architecture.<br>
|
|
**Audience:** Developers wishing to extend Horde.
|
|
|
|
## Further Reading
|
|
|
|
* [Glossary](Docs/Glossary.md)
|