but then how do you kill off all of the actors deployed using the old stuff?
yeah, I think maybe it's something that's a lot easier to do in F# :smile:
but that is the nasty edge case though
@smalldave newbie Topshelf question for you - is there any specific convention I need to follow when setting up commandline arguments?
like
/mycommand {commandvalue}
basically someone can pass in the IP, port number, and a debug flag that the service will use when it runs
because the way this stuff really gets set is via .config
using the usual HOCON configuration stuff
should have read that properly. apparently doesn't work
they're all optional anyway
<?xml version="1.0" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<targets>
<!--<target name="eventlog" xsi:type="EventLog" layout="${logger}: ${message}" source="Lighthouse" log="Application" />-->
<target name="console" xsi:type="ColoredConsole" layout="${date:format=HH\:MM\:ss} ${logger} ${message}"></target>
</targets>
<rules>
<!--<logger name="*" minlevel="Warn" writeTo="eventlog" />-->
<logger name="*" minlevel="Info" writeTo="console" />
</rules>
</nlog>
commented out the eventlog stuff, but not seeing anything appear on the console
cc @mmisztal1980
write away @Horusiath !
It's definitely something that would be worth it.. Here is some inspiration from the JVM side https://vaughnvernon.co/?p=986 using Postgres.
@Aaronontheweb Is there some simple documentation say a diagram showing the basic hierarchy of the Akka internals and how they play together. I am still trying to find a good place within the code base for that IOC release strategy and getting hung up on the life cycle and the other responsibilities of the system.
@Aaronontheweb I was just looking over on the JVM side and found this Stop Hook
After stopping an actor, its postStop hook is called, which may be used e.g. for deregistering this actor from other services. This hook is guaranteed to run after message queuing has been disabled for this actor, i.e. messages sent to a stopped actor will be redirected to the deadLetters of the ActorSystem.
After stopping an actor, its postStop hook is called, which may be used e.g. for deregistering this actor from other services. This hook is guaranteed to run after message queuing has been disabled for this actor, i.e. messages sent to a stopped actor will be redirected to the deadLetters of the ActorSystem.