Local RMS Software Implementation Guide

While our cloud-based solutions are widely favored, we recognize that some clients, particularly those with robust IT resources, in data-sensitive industries, or with a strong desire to seamlessly integrate our technology into their onsite infrastructure, may prefer the flexibility of an on-premises installation. This guide is designed to empower you to make this choice confidently and navigate the process efficiently.

Register for Our Portal

Our RMS Portal is a vital communication channel for sharing crucial information and updates. If you’re currently involved in an active implementation, visiting the portal and registering to receive a unique company code is essential. This code is your key to managing your project’s label designs and software updates, ensuring you feel valued and in control of your project.

Understand Our Process

Our software runs on PHP8, PostgreSQL, and IIS on Windows or Apache on Linux. If you need a VM image, we will develop your implementation on Microsoft Azure and make it available for User Acceptance Testing (UAT). Once your configuration is complete, we will distribute your image.

The implementation process involves gathering requirements for your workflow and defining any necessary integrations. You will receive RDP access to the Azure VM to test the implementation.

If you are running a Linux environment, we will test your implementation on our cloud environment and provide you with a Docker container upon acceptance.

Updates and Upgrades

From time to time, we will update your portal with updated plugins, core updates, database scripts, labels, training, and more. We will inform your company code user via email to keep you up to date on new developments. The portal serves as the central hub for all updates and communications.

SSL Certificates

If you want to use SSL on your LAN, here is an example of how to do so with a Certificate Authority (CA). You must perform these steps yourself and provide the certificate for us to install on the VM (or install it later yourself).

  1. Get a Domain Name: You need a public domain or subdomain, even though your app will only be accessible on your local network.
  2. Obtain an SSL Certificate: You can get an SSL certificate for your domain or subdomain. Services like Let’s Encrypt can provide this for free.
  3. Install the Certificate on Your Local Server: You’ll install this certificate on the server within your LAN hosting the app, which will require some technical steps.
  4. Access Your App Using the Domain Name: Inside your network, you can access your app using the domain or subdomain. Even though it’s a public domain, you won’t make the app accessible from outside; it’s just for SSL purposes.
  5. Configure Local DNS (Optional): You can set up your local network’s DNS to recognize the domain or subdomain and direct it to your local app so it doesn’t go out to the internet.

This way, your app stays within your LAN, but you still get the benefits of SSL encryption for users accessing it locally.

Related Posts

Customize Consent Preferences
We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site.
We also use third-party cookies that help us analyze how you use this website, store your preferences, and provide the content and advertisements that are relevant to you. These cookies will only be stored in your browser with your prior consent.
You can choose to enable or disable some or all of these cookies but disabling some of them may affect your browsing experience.
Always Active
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.