No description on how to run with Cargo on Linux development machines

https://documentation.bloomreach.com/14/library/development/run-and-develop-with-cargo.html

We ran into this issue when trying to run a HippCMS / brXM project which uses Apache Cargo to deploy several .war files to a managed instance of Tomcat 8. It turns out that the order in which the .war files are deployed can be inconsistent between systems and mainly relies on the order within the filesystem. On Linux systems that are using the ext4 filesystem for example order files in a order dependent on the file hash instead of alphabetical order like how Windows would do this. The result is that the `cargocpc.war` file, which apparently should load first for Hippo/Cargo, loads later in the process which causes the startup to fail.

The `ext4` file systems use hashed b-trees to organize files and directories, to disable this the user can run the following as a work around where `/dev/xyz` is the primary partition:

```
tune2fs -O^dir_index /dev/xyz
```

To re-enable the file system’s hashed b-trees:

```
tune2fs -O+dir_index /dev/xyz
```

There consequences to using the above workaround so having a better solution, hopefully included out of the box with brXM, to allow loading the tomcat applications in Cargo in a consistent manner independent of underlying OS and filesystem would be useful. Having some mention of this with perhaps this and other better workarounds in the documentation would be a great start.

Start with the linked Cargo development page and review its instructions for running HippCMS/brXM projects on Linux. Document the deployment-order problem and relevant workaround guidance, or clarify the better solution if the project provides one; done means the page explains the Linux-specific behavior and how to avoid startup failure.

Written by the indexing model from the issue text.