| 168 | = Stand-alone running |
| 169 | Stand-alone running works similar as in java. |
| 170 | * Ensure you pip-installed the geniuswebcore (2.0.1 or higher) |
| 171 | * The parties you want to run must be python-based (using GeniusWebPython, not GeniusWeb) and in your pythonpath. Typically by adding them to your PYTHONPATH environment variable. |
| 172 | * The profiles you want to provide to the parties (alternatively you can refer to a profile on a running profile server) |
| 173 | * A settings.json file containing the [source:geniuswebcore/geniusweb/protocol/session SessionSettings] eg SAOP Settings. [source:geniuswebcore/test/resources/settings.json view example file]. |
| 174 | |
| 175 | == Limitations |
| 176 | SimpleRunner has a number of restrictions, compared to a run using a runserver and partyserver |
| 177 | |
| 178 | * With stand-alone runner, your parties are run together in a single python interpreter. The main implication is that there may arise version conflicts between parties. |
| 179 | * You can only use GeniusWebPython-based parties, not GeniusWeb-based parties |
| 180 | |
| 181 | |
| 182 | |
| 183 | |
| 184 | |