| … | |
… | |
| 1015 | AnyEvent::MP::Global), then you can configure this service statically: |
1015 | AnyEvent::MP::Global), then you can configure this service statically: |
| 1016 | |
1016 | |
| 1017 | aemp profile mysrvnode services mymod::service:: |
1017 | aemp profile mysrvnode services mymod::service:: |
| 1018 | aemp run profile mysrvnode |
1018 | aemp run profile mysrvnode |
| 1019 | |
1019 | |
| 1020 | And the module will automatically be started in the node. |
1020 | And the module will automatically be started in the node, as specifying a |
|
|
1021 | module name (with C<::>-suffix) will simply load the module, which is then |
|
|
1022 | free to do whatever it wants. |
| 1021 | |
1023 | |
| 1022 | Of course, you can also do it in the much more standard way by writing |
1024 | Of course, you can also do it in the much more standard way by writing |
| 1023 | a module (e.g. C<BK::Backend::IRC>), installing it as part of a module |
1025 | a module (e.g. C<BK::Backend::IRC>), installing it as part of a module |
| 1024 | distribution and then configure nodes, for example, if I want to run the |
1026 | distribution and then configure nodes, for example, if I want to run the |
| 1025 | Bummskraut IRC backend on a machine named "ruth", I could do this: |
1027 | Bummskraut IRC backend on a machine named "ruth", I could do this: |
