nx_ini folder is user specific, why not share it with static location conf files?
Answered
Conf config is stored in /opt/${COMPANY}/mediaserver/etc, and INI config is stored in /root/.config/nx_ini for root and /home/${COMPANY}/.config/nx_ini for non-root.
This makes it rather non-deterministic, at least for docker, can the INI files please be shared with the default static config in /etc, i.e. I see no value in a server app having config that is in a user directory?
-
Thank you very much for taking the time to offer your suggestions. We truly appreciate your input.
Regarding the placement of the ini folder, it is intended for users to configure certain hidden or advanced settings for both the server and/or the client. Placing these files in the mediaserver folder could potentially cause inconvenience for users who do not install the server on a workstation, as they may not have access to the necessary ini files for their client applications.
We understand the importance of having configuration files stored in a common location that is independent of the existence of the server or application. Our nx_ini folder serves this purpose for configuration files across various modules, catering not only to server applications but also to client applications and other modules. Additionally, it is common for different users, each with administrator privileges on the OS side, to troubleshoot various components such as the server application, client application for different modules. Storing configuration files in user folders for different technicians is a scenario we encounter and would like to accommodate.
While we greatly value your suggestions and feedback, we would like to explain that there are specific reasons and use cases behind our current design decisions. At this time, we do not have plans to alter this structure. It is worth noting that configuration files are not frequently modified and we may suggest you to keep the path in mind in terms of different paths of the proper configuration files.
Thank you once again for your understanding and great feedbacks.
0 -
Server and clients are not installed on the same systems, at least not in production, thus sharing in the same folder is a mute point.
On servers the location of configuration files must be deterministic, and other server config conf files are already in a well known static etc location, mixing configuration locations makes life difficult.
For the server I see no reason to not locate ini files with conf files, the argument of different technicians and client install sharing does not apply to a server scenario.
0 -
Hi Pieter Viljoen,
Thanks for the follow-up. We do have some users who installed the server and client (bundled) on the same machine for the system in middle-small scale. So at the moment, the ini files would be remained as it is for some time. However, we do appreciate the suggestions and it is in the backlog for further discussion in the future release.
Thanks again and please keep raise and/or provide the feedback to the product.
0 -
The decision to keep the `nx_ini` folder user-specific rather than sharing it with static location configuration files depends on several factors and considerations related to software design, user experience, security, and system architecture. Here are some reasons why software developers might choose to keep the `nx_ini` folder user-specific:
1. User Preferences: The `nx_ini` folder often contains user-specific settings, preferences, and configurations for a particular software application. Sharing this folder across all users could lead to conflicts and inconsistencies in settings, potentially causing confusion and usability issues.
2. Security and Privacy: User-specific folders help maintain data privacy and security by isolating each user's settings and configurations. Sharing sensitive configuration files across users could pose security risks, especially if the files contain personal or confidential information. Valero Credit Card
3. Customization and Flexibility: Keeping the `nx_ini` folder user-specific allows each user to customize their settings and configurations according to their preferences and requirements. Users may have different needs and workflows, and providing individual configuration folders enhances flexibility and customization options.
4. Ease of Management: Managing user-specific configuration folders simplifies troubleshooting and support processes. It allows administrators and support personnel to address user-specific issues more effectively without impacting other users' configurations.
5. Compatibility and Portability: User-specific configuration folders facilitate application portability and compatibility across different systems and environments. Users can easily transfer their settings and configurations to other devices or user accounts without affecting system-wide configurations.
However, there may be situations where sharing configuration files across users is necessary or beneficial. In such cases, software developers may implement alternative approaches such as system-wide configuration files with appropriate access controls and permissions to ensure security and maintainability.
Ultimately, the decision to keep the `nx_ini` folder user-specific or share it with static location configuration files depends on the specific requirements, design considerations, and trade-offs of the software application and its target user base.
0
Please sign in to leave a comment.
Comments
4 comments