Skip to content

Feat: shut server down if it can't find fxManager resource#61

Merged
FjamZoo merged 2 commits into
mainfrom
chore/crash-server-on-missing-ressource
Jul 12, 2026
Merged

Feat: shut server down if it can't find fxManager resource#61
FjamZoo merged 2 commits into
mainfrom
chore/crash-server-on-missing-ressource

Conversation

@Maximus7474

Copy link
Copy Markdown
Member

Description

Even if the project can run without the fxserver resource, pretty much everything else becomes pointless, it's just a glorified web hosted console.


Tests

  • Tested in development mode
  • Passes typecheck
  • Builds & runs on Windows
  • Builds & runs on Linux

Additional Notes

@Maximus7474 Maximus7474 requested a review from FjamZoo July 7, 2026 18:27
@Maximus7474 Maximus7474 self-assigned this Jul 7, 2026
@Maximus7474 Maximus7474 added the enhancement New feature or request label Jul 7, 2026
@Maximus7474 Maximus7474 mentioned this pull request Jul 11, 2026
4 tasks
@FjamZoo FjamZoo merged commit 4a2ac11 into main Jul 12, 2026
6 checks passed
Maximus7474 added a commit that referenced this pull request Jul 12, 2026
setFxServerReady instead of detecting nucleus auth
@Maximus7474 Maximus7474 deleted the chore/crash-server-on-missing-ressource branch July 12, 2026 21:31
andreutu pushed a commit that referenced this pull request Jul 13, 2026
* fix(core/process): nucleus deprecation makes validating the startup
impossible
-> wait for an http request from fxManager resource to say the server is
ready
-> with the current setup, fxManager starts last so on first tick for it
server should be running

* fix(core/modules/process): updated test added in #61 to use
setFxServerReady instead of detecting nucleus auth
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: core enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants