MintCHM

MintHCM

Is an open-source software, which means it is freely available for download and installation on your own server.

Human Capital Management

It encompasses a comprehensive set of practices for the recruitment, management, and administrative aspects of human resources processes, often also referred to as Human Resources Management (HRM).

Purpose

The purpose of this wiki entry is to provide an example on integrating NGINX with MintHCM, ensuring a seamless and efficient setup.

This article assumes the following:

• NGINX has been installed
• Your NGINX Default site is configured.
• MintHCM has already been installed and configured in your web directory on the server.

Additional Notes

• This setup is compatible with both Peppermint (based on Debian or Devuan) and can be applied to Debian or Devuan directly, with the only variation being the init systems used by each distribution. The steps outlined here are universally applicable, making it a versatile solution for all these platforms.

• By default, MintHCM is documented to use Apache, primarily due to its reliance on the .htaccess feature. The '.htaccess file is a configuration file used by Apache-based web servers to manage and customize the behavior of the server at a directory level.

• NGINX does not have a direct equivalent to Apache's .htaccess files. To achieve similar functionality, you need to set the NGINX configuration directives. This involves placing them within the server or location blocks of the NGINX configuration file.

Configure NGINX

On Peppermint, which is based on Debian or Devuan, the NGINX configuration files are typically located in the following directories:

• Main Configuration File: Usually found at /etc/nginx/nginx.conf
• Site Configuration Files: Often located in /etc/nginx/sites-available/ and symlinked to /etc/nginx/sites-enabled/
• Other Configuration Files: Additional configuration files might be found in /etc/nginx/conf.d/

For these steps you only need to work with the sites-available In many NGINX installations, a default configuration file is provided in the sites-available directory, often named default. This file serves as a template or example configuration.

A common best practice is to define your standard server block settings in the default configuration file and then include separate .conf files for specific locations or sites. This approach keeps your configuration organized and allows you to reuse common settings across multiple server blocks.