Using NenjimHub, it is currently not possible to start any plugins (applications or services), as we do not even have an active interface for doing so.
NenjimHub will need a very basic way to start those on its own startup.
We already have a standalone (not needing anything from Nenjim) application called JupiterPerpsAlarm that we can use to implement this auto start feature.
The code for the Jupiter Alarm is in implementation package: com.r35157.jupiterperpsalarm.impl.ref
What NOT to do:
We should change the code for the Jupiter Alarm as little as possible - preferably not at all.
We should NOT do correct Nenjim process management
We should NOT do unittests
We should NOT make this flexible to start other plugins for now.
What we SHOULD do:
When NenjimHub is started using the 'run.sh' or 'debug.sh' script, Nenjim should also start the Jupiter Alarm.
Because we do not have any real process management yet, NenjimHub should just start a new thread and make it run the Jupiter Alarm.
NenjimHub should never exit even though the Jupiter Alarm fails or completes, as the NenjimHub is lige the operating system. It is ok that we cannot restart anything. We will have to CRTL+C and restart NenjinHub to start our only plugin - the Jupiter Alarm.
### Generel
Using NenjimHub, it is currently not possible to start any plugins (applications or services), as we do not even have an active interface for doing so.
NenjimHub will need a very basic way to start those on its own startup.
We already have a standalone (not needing anything from Nenjim) application called JupiterPerpsAlarm that we can use to implement this auto start feature.
The code for the Jupiter Alarm is in implementation package: com.r35157.jupiterperpsalarm.impl.ref
### What NOT to do:
- We should change the code for the Jupiter Alarm as little as possible - preferably not at all.
- We should NOT do correct Nenjim process management
- We should NOT do unittests
- We should NOT make this flexible to start other plugins for now.
### What we SHOULD do:
- When NenjimHub is started using the 'run.sh' or 'debug.sh' script, Nenjim should also start the Jupiter Alarm.
- Because we do not have any real process management yet, NenjimHub should just start a new thread and make it run the Jupiter Alarm.
- NenjimHub should never exit even though the Jupiter Alarm fails or completes, as the NenjimHub is lige the operating system. It is ok that we cannot restart anything. We will have to CRTL+C and restart NenjinHub to start our only plugin - the Jupiter Alarm.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Generel
Using NenjimHub, it is currently not possible to start any plugins (applications or services), as we do not even have an active interface for doing so.
NenjimHub will need a very basic way to start those on its own startup.
We already have a standalone (not needing anything from Nenjim) application called JupiterPerpsAlarm that we can use to implement this auto start feature.
The code for the Jupiter Alarm is in implementation package: com.r35157.jupiterperpsalarm.impl.ref
What NOT to do:
What we SHOULD do: