Internal.io can be deployed as a Docker container running on your own cloud instance.
To ensure that your data is persisted between deployments, Internal makes use of Docker volumes. Internal uses one storage volume mounted to the data filesystem path (/srv/internalio/data).
The on premise deployment of Internal requires several environment variables to be configured prior to running. These can be saved to an env file to be used by Docker directly or passed through as individual environment variables. In the examples below, we'll assume the use of an env file.
Be sure to securely store and backup the INTERNALIO_SECRET_KEY and INTERNALIO_CONNECTOR_SECRET_KEY environment variables. Losing either one of these keys will result in inaccessible audit log data or data sources.
The on premise version of Internal can be deployed using Docker:
Ensure that the INTERNALIO_API_DATABASE_URI ****and ****INTERNALIO_CONNECTOR_DATABASE_URI environment variables are set with valid PostgreSQL connection URIs. Once these values are set, you may omit the data volume from the above example to run Internal:
Double check that you are running the latest version of the OnPrem deployment. As seen in the command above, internalio/onprem:2.34.0 is the latest version as of 06/21/2022.
After a few moments, the container should be running with the host port 7080 mapped to the container. You can verify this by running:
You may now navigate to the hostname or IP address on port 7080 (e.g. http://127.0.0.1:7080). Create an account, then you'll be guided through connecting your first datasources.
SSL configuration with custom certificates can be accomplished using docker compose to run a reverse proxy container that communicates with the on internalio/onprem container. Here is an example configuration that uses nginx as the reverse proxy (other proxy services such as HAProxy will also work).
First create your docker-compose.yml file:
Copy your certificate and key into in the ./certs directory:
Create an nginx config in your ./nginx directory (let's call it nginx.conf ).
Run docker compose:
To update Internal, simply pull the latest docker image and re-deploy using the existing environment file and config/data volumes.
Run the container with the following flag to allow Localhost proxies to communicate with external addresses from inside of a container which is running Internal.
One can export the Postgres DB that Internal uses for its application for sharing, deployment, or backups by issuing the following commands from CLI via a logged-in user on the server on which OnPrem Internal is running:
Special consideration must be paid to installing our on-prem solution to Windows Machines, in particular Windows Server. Below, you'll find the needed steps to get your solution installed and running.
NOTE: If you are using Azure virtual machines, you will need to select a virtual machine that supports running nested virtualization (Dv3 and Ev3 sizes). Additionally, the server must be able to run Hyper-V.
NOTE: Make sure you do linuxkit/lcow part or else you will get an error indicating that
"C:\Program Files\Linux Containers\kernel.exe" is missing.
Internal offers custom OAuth via Okta, Google, and Auth0, and is compatible with any other identity provider which uses OAuth and OAuth2. The following are those authorization tools for which we have documentation: