mount

roklenarcic 2020-07-09T07:25:16.075500Z

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?

tolitius 2020-07-09T15:13:33.075900Z

@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

roklenarcic 2020-07-09T15:14:37.076500Z

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

tolitius 2020-07-09T15:15:44.077Z

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

tolitius 2020-07-09T15:16:19.077900Z

or if you don't need to compose them: https://github.com/tolitius/mount#start-an-application-without-certain-states

roklenarcic 2020-07-09T15:17:42.079400Z

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

roklenarcic 2020-07-09T15:18:29.080200Z

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

tolitius 2020-07-09T15:19:04.080800Z

correct. how many states do you need to exclude?

tolitius 2020-07-09T15:19:40.081900Z

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

tolitius 2020-07-09T15:20:40.083Z

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