r35157/com_r35157_nenjim-hubd-impl_ref
SHA256
0
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Enable support for autostart of JupiterPerpsAlarmImpl #2

New Issue
Closed
opened 2026-06-19 09:11:46 +02:00 by minimons · 0 comments
minimons commented 2026-06-19 09:11:46 +02:00
Owner
Copy Link
Copy Source

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.
### 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.
minimons added the enhancement label 2026-06-19 09:11:46 +02:00
minimons self-assigned this 2026-06-19 09:11:46 +02:00
minimons added this to the Nenjim project 2026-06-19 09:11:46 +02:00
minimons moved this to Done in Nenjim on 2026-06-23 09:46:21 +02:00
Sign in to join this conversation.
0.1-dev
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project Nenjim
Assignees
Clear assignees
builder (CICD User) minimons (Morten Green Hermansen)
No Assignees minimons
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: r35157/com_r35157_nenjim-hubd-impl_ref#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?