# Novarix Networks Website

Static marketing site for `Novarix Networks`, prepared for this deployment model:

- `Gitea` as the source of truth for the code
- `Ubuntu 24.04` VM running `Nginx` as the private web server
- `Nginx Proxy Manager` exposing the site publicly and handling SSL

## Project Structure

- `public/` static files that should be deployed to the web root
- `public/assets/logo/` brand assets used by the site
- `public/assets/favicon/` favicon files
- `ops/nginx/novarixnet.com.conf.example` example Nginx server block

## Current Recommended Architecture

1. Keep this project in your internal `Gitea` repo.
2. Use the `Ubuntu 24.04` VM as the dedicated private web server.
3. Install `nginx` on that VM.
4. Deploy the contents of `public/` to something like `/var/www/novarixnet.com`.
5. Use `Nginx Proxy Manager` to proxy the public domain to the VM's private IP and Nginx port.
6. Let `Nginx Proxy Manager` handle the public certificate and HTTPS redirect.

## Recommended Workflow

This is the cleanest way to handle changes:

1. Edit the site locally.
2. Commit and push to `Gitea`.
3. On the `Ubuntu 24.04` web VM, pull the latest repo changes.
4. Sync the contents of `public/` into `/var/www/novarixnet.com`.
5. Reload `nginx` if needed.

This keeps:

- your repo as the source of truth
- the web VM as a deployment target
- live web files separate from the Git working tree

## Important Deployment Note

Do not point `nginx` directly at the Git repository directory if you can avoid it.

Better approach:

- keep the repo in a path such as `/opt/novarix-website`
- serve the live site from `/var/www/novarixnet.com`
- copy or sync `public/` into `/var/www/novarixnet.com` during deployment

That gives you a cleaner separation between:

- source code
- deployment files
- web server content

## Example Web VM Layout

- Repo checkout: `/opt/novarix-website`
- Live site root: `/var/www/novarixnet.com`
- Nginx site config: `/etc/nginx/sites-available/novarixnet.com`

## Example Deployment Flow On The Web VM

Clone the repo once:

```bash
git clone <your-gitea-repo-url> /opt/novarix-website
```

Deploy updated files:

```bash
sudo mkdir -p /var/www/novarixnet.com
sudo rsync -av --delete /opt/novarix-website/public/ /var/www/novarixnet.com/
```

Reload Nginx:

```bash
sudo systemctl reload nginx
```

## Nginx Proxy Manager Flow

- Public DNS record points to your public IP
- Router forwards `80` and `443` to the host running `Nginx Proxy Manager`
- `Nginx Proxy Manager` receives the public request
- `Nginx Proxy Manager` proxies traffic to the private `Ubuntu 24.04` web VM
- Private `nginx` serves the static files

## Canonical Domain Suggestion

Your strongest current options are:

- `novarixnet.com` for broad and international branding
- `novarix.co.uk` for a stronger UK-local trust signal

Pick one as the canonical domain and redirect the others to it.

## Notes For This Site

- Replace the placeholder `contact@novarixnet.com` link in `public/index.html`
- Add real company contact details before launch
- Add legal pages such as privacy and terms
- Add deeper service pages once the ISP, MSP, and transit offers are finalized
- Add a contact form or CRM integration later if needed

## Included Nginx Example

Use the example config here as a starting point:

- `ops/nginx/novarixnet.com.conf.example`

Review the domain names, root path, and cache rules before using it in production.