TechDeployment

Deploying Omni on Ubuntu Server

A practical deployment case study showing how Omni was moved from a local VirtualBox development environment to a private Ubuntu server using Next.js, PostgreSQL, Nginx, PM2, Git, and separate dev/staging environments.

Challenge

What needed to be solved

This project documents the process of deploying the Omni portfolio and knowledge platform on an Ubuntu 24.04 work server. The goal was to move away from a local VirtualBox-only workflow and create a cleaner server-based development and staging setup with Nginx, PM2, PostgreSQL, Git-based deployment, and safer separation between dev and staging.

The server only had a private IP, so external access required careful planning.
Development and staging initially shared some configuration, which risked affecting both environments.
Direct port 3000 access depended on firewall and workstation subnet rules.
Some staging edits were made manually, which caused Git pull conflicts.
Responsive layout required testing across large screens and laptop widths.

Delivery

What Omni delivered

Prepared the Ubuntu work server for hosting the Omni application.
Created a dedicated application user and organized the app under /srv.
Moved the Omni codebase from the local VirtualBox workflow to the work server.
Configured separate development and staging application folders.
Configured separate PostgreSQL databases for dev and staging.
Used PM2 to run the staging Next.js application process.
Configured Nginx to expose the staging application through the server IP.
Tested contact form behavior, admin pages, Learn pages, and project detail pages.
Used Git to promote committed changes from dev to staging.

Evidence

Selected implementation evidence

Read supporting project notes

Project context

Omni started as a local development project running inside a VirtualBox Ubuntu environment. As the project became more serious, the next step was to move it to a stronger work server where development and staging could run more reliably.

Goal

The goal was to create a server-based workflow where development can continue on the work server, while staging remains available through Nginx for browser testing and internal review.

Implementation approach

The server was prepared with a dedicated application structure under /srv. The development application runs separately from the staging application, and each environment uses its own database so changes in development do not accidentally affect staging data.

Operational design

Nginx exposes the staging site through port 80, while the development server can be accessed directly on port 3000 when needed. PM2 is used to keep the staging process running, and Git is used to move committed changes from development to staging.

Result

The result is a cleaner, safer, and more professional deployment workflow for Omni. The project can now be developed on the server, tested in staging, committed through Git, and later prepared for public hosting when a domain and public access are ready.

Outcome

Operational value

Omni was successfully deployed on the Ubuntu work server with separate development and staging application folders, separate PostgreSQL databases, Nginx access for staging, PM2 process management, Git-based promotion from dev to staging, and tested Learn/project pages.

Environment

Technology and environment

Ubuntu 24.04
Next.js
TypeScript
PostgreSQL
Prisma
Nginx
PM2
Git
UFW
MobaXterm

Related knowledge

Collaboration

Have a system or environment to build or improve?

Share what needs to be built, improved, prepared, or supported. Omni can help turn the requirement into dependable delivery.

Discuss your project