Skip to content

feat: settings page and enhancements#25

Merged
FjamZoo merged 13 commits into
mainfrom
feat/settings-page
Jun 30, 2026
Merged

feat: settings page and enhancements#25
FjamZoo merged 13 commits into
mainfrom
feat/settings-page

Conversation

@andreutu

Copy link
Copy Markdown
Collaborator

Description

Implements a settings page that can be used to configure various aspects of fxManager. As of now, the amount of customizable options is limited, but its structure and modularity will allow for easy expansions as features are progressively added.

Related managers, routes and parts of the codebase have been refactored to account for using settings instead of hardcoded or environment values. Moreover, a redo of how settings are structured has been implemented which now separates settings by categories (scopes), and invalid values (scopes and keys) are now restricted.

Tests

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

Additional Notes

N/A

@Maximus7474 Maximus7474 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall, a couple little adjustments on the contents.
Also noticed that there was no field for inputting discord bot token, are we keeping that as an env variable ?

Comment thread apps/core/src/routes/api/settings/index.ts Outdated
Comment thread apps/webpanel/src/pages/settings/tabs/whitelist.tsx Outdated
Comment thread apps/webpanel/src/pages/settings/index.tsx Outdated
@andreutu

Copy link
Copy Markdown
Collaborator Author

Also noticed that there was no field for inputting discord bot token, are we keeping that as an env variable ?

I'm thinking it would be better this way and more secure, but on second thought I think it should be a good addition. Should I add it?

@Maximus7474

Copy link
Copy Markdown
Collaborator

Well, I think it would be best. Might develop the settings to adapt what can be accessed/changed so it's not just one permission.

@FjamZoo

FjamZoo commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

Also noticed that there was no field for inputting discord bot token, are we keeping that as an env variable ?

I'm thinking it would be better this way and more secure, but on second thought I think it should be a good addition. Should I add it?

I think anything that is currently a env unless it touches ports etc. (that might break our shit) it should just be configureable on the webpanel for end users.

Most people in fivem will NOT know how to edit a .env

@andreutu

Copy link
Copy Markdown
Collaborator Author

Most people in fivem will NOT know how to edit a .env

Highly doubt 90% of people will even be able to run fxManager, but yeah I'll add that.

@Maximus7474

Copy link
Copy Markdown
Collaborator

Highly doubt 90% of people will even be able to run fxManager, but yeah I'll add that.

Well the entire community running dodgy game panels won't be able to, unless companies decide to implement it.

@andreutu

Copy link
Copy Markdown
Collaborator Author

Discord bot token is now configurable, should be good to merge.

@FjamZoo FjamZoo merged commit a716330 into main Jun 30, 2026
5 checks passed
@FjamZoo FjamZoo deleted the feat/settings-page branch July 4, 2026 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants