Fork me on GitHub
#mount
<
2020-07-09
>
roklenarcic07:07:16

if I’ve got states A and B, A uses B in its start, when I start state A, state B doesn’t get started… what is the reason for that?

tolitius15:07:33

@roklenarcic you can start all with (mount/start) or you can do (mount/start #'foo/a #'foo/b) when you start a state individually (mount/start #'foo/a) it only focuses on a state specified and does not affect other states

roklenarcic15:07:37

so if I want to start the web server, but not scheduled jobs for instance, I have to manually list all the dependencies?

tolitius15:07:44

you can start all except a "scheduler" state: https://github.com/tolitius/mount#composing-states

roklenarcic15:07:42

right, so I need to list scheduler and dependencies that it uses but web server doesn’t use in except

roklenarcic15:07:29

I assume same principle applies, putting just scheduler in except will only skip that one, not it’s dependencies

tolitius15:07:04

correct. how many states do you need to exclude?

tolitius15:07:40

usually it's from one to just a few, otherwise it might be an indicator to remove number of stateful things

tolitius15:07:40

this depends of course, but if states are kept low level (connections, tread pools, listeners, servers, etc..) there are just not as many of them in a given application