Wreckroom - User contributions [en]

Web Server

2026-04-28T00:54:36Z

66.108.234.75:

= Synology Site Management =

Both sites are hosted on '''mainsqueeze''' (Synology) behind NGINX Reverse Proxy, served over 443.

{| class="wikitable"
! Site !! Local Port !! Directory
|-
| [https://wreckroom.nyc wreckroom.nyc] || <code>localhost:3000</code> || <code>/volume2/wreckroom.nyc/wreckroom.nyc</code>
|-
| [https://justinbjur.com justinbjur.com] || <code>localhost:3001</code> || <code>/volume2/justinbjur.com/justinbjur.com</code>
|}

== Updating Site Content ==
# Make changes locally and commit to GitHub
# SSH into mainsqueeze: <code>ssh guernica@mainsqueeze</code>
# Navigate to the site and pull:
## <code>cd /volume2/wreckroom.nyc/wreckroom.nyc</code> (or justinbjur.com)
## <code>git pull</code>
# Restart pm2: <code>sudo pm2 restart wreckroom.nyc</code> (or justinbjur.com)

== PM2 ==
'''PM2''' is a process manager that keeps both Next.js apps alive on mainsqueeze.

=== Current Processes ===
{| class="wikitable"
! Name !! Command
|-
| <code>wreckroom.nyc</code> || <code>npm run start</code>
|-
| <code>justinbjur.com</code> || <code>npm run start</code>
|}

=== After a Synology Reboot ===
PM2 should auto-resume if <code>pm2 save</code> was run. If not, restart manually:
# <code>cd /volume2/wreckroom.nyc/wreckroom.nyc</code>
# <code>sudo pm2 start npm --name "wreckroom.nyc" -- run start</code>
# <code>cd /volume2/justinbjur.com/justinbjur.com</code>
# <code>sudo pm2 start npm --name "justinbjur.com" -- run start</code>
# <code>sudo pm2 save</code>

=== Troubleshooting ===
If a site is down and pm2 shows an error, delete and restart that process:
# <code>sudo pm2 delete wreckroom.nyc</code>
# <code>sudo pm2 start npm --name "wreckroom.nyc" -- run start</code>
# <code>sudo pm2 save</code>

== Certificates ==
If you modify a certificate's FQDN, you '''must''' also update the reverse proxy entry.

'''Control Panel → Login Portal → Advanced → Reverse Proxy'''

Update the hostname there — without this step the site will not resolve correctly even after migrating the cert. This has cost half a day before, don't skip it.

Web Server

2026-04-28T00:12:25Z

66.108.234.75:

= Synology Site Management =

Both sites are hosted on '''mainsqueeze''' (Synology) behind NGINX Reverse Proxy, served over 443.

{| class="wikitable"
! Site !! Local Port !! Directory
|-
| [https://wreckroom.nyc wreckroom.nyc] || <code>localhost:3000</code> || <code>/volume2/wreckroom.nyc/wreckroom.nyc</code>
|-
| [https://justinbjur.com justinbjur.com] || <code>localhost:3001</code> || <code>/volume2/justinbjur.com/justinbjur.com</code>
|}

== Updating Site Content ==
# Make changes locally and commit to GitHub
# SSH into mainsqueeze: <code>ssh guernica@mainsqueeze</code>
# Navigate to the site and pull:
## <code>cd /volume2/wreckroom.nyc/wreckroom.nyc</code> (or justinbjur.com)
## <code>git pull</code>
# Restart pm2: <code>sudo pm2 restart wreckroom.nyc</code> (or justinbjur.com)

== PM2 ==
'''PM2''' is a process manager that keeps both Next.js apps alive on mainsqueeze.

=== Current Processes ===
{| class="wikitable"
! Name !! Command
|-
| <code>wreckroom.nyc</code> || <code>npm run dev</code>
|-
| <code>justinbjur.com</code> || <code>npm run dev</code>
|}

=== After a Synology Reboot ===
PM2 should auto-resume if <code>pm2 save</code> was run. If not, restart manually:
# <code>cd /volume2/wreckroom.nyc/wreckroom.nyc</code>
# <code>sudo pm2 start npm --name "wreckroom.nyc" -- run dev</code>
# <code>cd /volume2/justinbjur.com/justinbjur.com</code>
# <code>sudo pm2 start npm --name "justinbjur.com" -- run dev</code>
# <code>sudo pm2 save</code>

=== Troubleshooting ===
If a site is down and pm2 shows an error, delete and restart that process:
# <code>sudo pm2 delete wreckroom.nyc</code>
# <code>sudo pm2 start npm --name "wreckroom.nyc" -- run dev</code>
# <code>sudo pm2 save</code>

== Certificates ==
If you modify a certificate's FQDN, you '''must''' also update the reverse proxy entry.

'''Control Panel → Login Portal → Advanced → Reverse Proxy'''

Update the hostname there — without this step the site will not resolve correctly even after migrating the cert. This has cost half a day before, don't skip it.

Wreckroom

2026-01-19T16:39:36Z

66.108.234.75: /* UniFi */

[[Wreckroom]] is an Independent Record Label focused on innovative and groundbreaking music.

=Strategy=
===[[Executive Summary]]===
===[[Road Map Q1-Q2 2024]]===

=Media Verticals=
Media Verticals are the different broad categories of content we focus on.

===[[Performance Series]]===
A Safe and Sound Showcase, Daylight Sessions all fall under these categories. Usually a performance video piece that lives on YouTube.

===[[Interviews]]===
Short form content pieces that either feed into the performance series or create a short form entertainment piece from artists we’ve worked with.

===[[WRNY]]===

WRNY a 24 hour Youtube Radio Station, featuring all the artists that we have hand selected to perform at [[Safe & Sound Studios]].

=Access=
You can access Wreckroom remotely via [[VPN]] or onsite. You will need to mount the [[Media Server]] to access the media and [[DaVinci Resolve Project Server]] for video editing.
==Remote Access==
===[[VPN]]===

If you are working from home, connect to the [[VPN]] to access Wreckroom media files and storage ''remotely''.

==Media Access==
Regardless of if you are at home or in the studio, you can access the Wreckroom servers:

===[[Media Server]]===
Connect to [[Wreckroom]]'s vast media library.

====[[File Naming Conventions]]====
Learn about how files on the server are to be named! TL;DR ALL CAPS

== Project Access ==

===[[DaVinci Resolve Project Server]]===
A Network Server to edit files remotely in resolve

====[[Creating Proxies in Resolve Server]]====
Learn how creating proxy media on the [[Media Server]] helps speed up performance over the [[DaVinci Resolve Project Server]]!

====[[Transferring Local Database to Davinci Resolve Project Server]]====
If you have a project that has been edited locally and needs to be transferred to the Resolve server!

====[[Ensuring Media Accessibility]]====
Steps to create media accessible remotely as well as relink media in projects!

=Help=

===[https://www.mediawiki.org/wiki/Cheatsheet Wiki Syntax Cheatsheet]===

= Network Administration =

===[[Synology]]===
The Synology is a Network Attached Storage (NAS) and Linux Server that runs many different processes that are essential to [[Wreckroom]].

===[[MacPro]]===
The MacPro runs the [[DaVinci Resolve Server]] and hosts [[OBS]] for [[WRNY]].

===[[UniFi]]===
We have a 10G network...LFG!

Navidrome

2025-09-25T03:28:17Z

66.108.234.75:

[[Navidrome]] is a self-hosted music streaming server that lets you stream your personal music collection over the web. Think of it as your personal music cloud - you can listen to your music collection from anywhere, just like Spotify, but it's your own music hosted on your own server.

=Configuration=

The configuration file is located at: <code>/volume2/docker/navidrome/navidrome.toml</code>

===Docker===

Navidrome is managed inside a Docker container. To restart use: <code>sudo docker restart navidrome</code>

=== Certs ===

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

Since docker goes through the GUI <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs need to happen manually to propagate on update.

<syntaxhighlight lang="bash">
sudo cp /usr/syno/etc/certificate/system/default/RSA-cert.pem /volume2/docker/navidrome/ssl/certificate.crt
sudo cp /usr/syno/etc/certificate/system/default/RSA-privkey.pem /volume2/docker/navidrome/ssl/private.key
sudo chmod 644 /volume2/docker/navidrome/ssl/certificate.crt
sudo chmod 600 /volume2/docker/navidrome/ssl/private.key
sudo docker restart navidrome
</syntaxhighlight>

Navidrome

2025-07-20T18:41:42Z

66.108.234.75: /* Configuration */

[[Navidrome]] is a self-hosted music streaming server that lets you stream your personal music collection over the web. Think of it as your personal music cloud - you can listen to your music collection from anywhere, just like Spotify, but it's your own music hosted on your own server.

=Configuration=

The configuration file is located at: <code>/volume2/docker/navidrome/config.toml</code>

===Docker===

Navidrome is managed inside a Docker container. To restart use: <code>sudo docker restart navidrome</code>

=== Certs ===

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

Since docker goes through the GUI <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs need to happen manually to propagate on update.

<syntaxhighlight lang="bash">
sudo cp /usr/syno/etc/certificate/system/default/RSA-cert.pem /volume2/docker/navidrome/ssl/certificate.crt
sudo cp /usr/syno/etc/certificate/system/default/RSA-privkey.pem /volume2/docker/navidrome/ssl/private.key
sudo chmod 644 /volume2/docker/navidrome/ssl/certificate.crt
sudo chmod 600 /volume2/docker/navidrome/ssl/private.key
sudo docker restart navidrome
</syntaxhighlight>

Navidrome

2025-07-18T20:15:08Z

66.108.234.75:

[[Navidrome]] is a self-hosted music streaming server that lets you stream your personal music collection over the web. Think of it as your personal music cloud - you can listen to your music collection from anywhere, just like Spotify, but it's your own music hosted on your own server.

=Configuration=

The configuration file is located at: <code>/volume2/docker/navidrome/config.toml</code>

===Docker===

Navidrome is managed inside a Docker container. To restart use: <code>sudo docker restart navidrome</code>

=== Certs ===

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

Since docker goes through the GUI <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs need to happen manually to propagate on update.

<syntaxhighlight>
sudo cp /usr/syno/etc/certificate/system/default/RSA-cert.pem /volume2/docker/navidrome/ssl/certificate.crt
sudo cp /usr/syno/etc/certificate/system/default/RSA-privkey.pem /volume2/docker/navidrome/ssl/private.key
sudo chmod 644 /volume2/docker/navidrome/ssl/certificate.crt
sudo chmod 600 /volume2/docker/navidrome/ssl/private.key
sudo docker restart navidrome
</syntaxhighlight>

Navidrome

2025-07-18T20:02:24Z

66.108.234.75: /* Configuration */

[[Navidrome]] is a self-hosted music streaming server that lets you stream your personal music collection over the web. Think of it as your personal music cloud - you can listen to your music collection from anywhere, just like Spotify, but it's your own music hosted on your own server.

=Configuration=

The configuration file is located at: <code>/volume2/docker/navidrome/config.toml</code>

===Docker===

Navidrome is managed inside a Docker container. To restart use: <code>sudo docker restart navidrome</code>

=== Certs ===

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

Since docker goes through the GUI <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs need to happen manually to propagate on update.

<syntaxhighlight>
cp /usr/syno/etc/certificate/system/default/RSA-cert.pem /volume2/docker/navidrome/ssl/certificate.crt
cp /usr/syno/etc/certificate/system/default/RSA-privkey.pem /volume2/docker/navidrome/ssl/private.key
chmod 644 /volume2/docker/navidrome/ssl/certificate.crt
chmod 600 /volume2/docker/navidrome/ssl/private.key
docker restart navidrome
</syntaxhighlight>

Navidrome

2025-07-18T19:42:05Z

66.108.234.75: /* Configuration */

[[Navidrome]] is a self-hosted music streaming server that lets you stream your personal music collection over the web. Think of it as your personal music cloud - you can listen to your music collection from anywhere, just like Spotify, but it's your own music hosted on your own server.

=Configuration=

The configuration file is located at: <code>/volume2/docker/navidrome/config.toml</code>

===Docker===

Navidrome is managed inside a Docker container. To restart use: <code>sudo docker restart navidrome</code>

=== Certs ===

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

I've set up symlinks to auto update the <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs propagate on update.

<syntaxhighlight>
# First, navigate to the directory
cd /volume2/docker/navidrome/ssl

# THEN create the symlinks
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-cert.pem certificate.crt
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-privkey.pem private.key
</syntaxhighlight>

Navidrome

2025-07-18T19:41:05Z

66.108.234.75: /* Configuration */

[[Navidrome]] is a self-hosted music streaming server that lets you stream your personal music collection over the web. Think of it as your personal music cloud - you can listen to your music collection from anywhere, just like Spotify, but it's your own music hosted on your own server.

=Configuration=

===Docker===

Navidrome is managed inside a Docker container. To restart use: <code>sudo docker restart navidrome</code>

==== <code>config.toml</code>====

=== Certs ===

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

I've set up symlinks to auto update the <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs propagate on update.

<syntaxhighlight>
# First, navigate to the directory
cd /volume2/docker/navidrome/ssl

# THEN create the symlinks
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-cert.pem certificate.crt
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-privkey.pem private.key
</syntaxhighlight>

Navidrome

2025-07-18T19:38:48Z

66.108.234.75: /* Configuration */

[[Navidrome]] is a self-hosted music streaming server that lets you stream your personal music collection over the web. Think of it as your personal music cloud - you can listen to your music collection from anywhere, just like Spotify, but it's your own music hosted on your own server.

=Configuration=

=== <code>config.toml</code>===

=== Certs ===

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

I've set up symlinks to auto update the <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs propagate on update.

<syntaxhighlight>
# First, navigate to the directory
cd /volume2/docker/navidrome/ssl

# THEN create the symlinks
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-cert.pem certificate.crt
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-privkey.pem private.key
</syntaxhighlight>

Navidrome

2025-07-18T19:38:10Z

66.108.234.75:

Navidrome

2025-07-18T19:36:18Z

66.108.234.75: /* Configuration */

[[Navidrome]] is

=Configuration=

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

I've set up symlinks to auto update the <code>config.toml</code> for [[Navidrome]] so updates to the default SSL certs propagate on update.

<syntaxhighlight>
# First, navigate to the directory
cd /volume2/docker/navidrome/ssl

# THEN create the symlinks
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-cert.pem certificate.crt
sudo ln -s /usr/syno/etc/certificate/system/default/RSA-privkey.pem private.key
</syntaxhighlight>

Navidrome

2025-07-18T19:34:14Z

66.108.234.75:

Navidrome

2025-07-18T19:32:33Z

66.108.234.75: /* Configuration */

=Configuration=

The default '''wreckroom.nyc''' certs are located here: <code>/usr/syno/etc/certificate/system/default</code>

I've set up symlinks to auto update the <code>config.toml</code> for [[Navidrome]]

<syntaxhighlight>

</syntaxhighlight>

Navidrome

2025-07-18T19:31:26Z

66.108.234.75: /* Configuration */

=Configuration=

The default '''wreckroom.nyc''' certs are located here:<code>/usr/syno/etc/certificate/system/default</code>

Navidrome

2025-07-18T19:31:05Z

66.108.234.75: /* Configuration */

=Configuration=

Wreckroom certs are located here:<code>/usr/syno/etc/certificate/system/default</code>

Navidrome

2025-07-18T19:30:54Z

66.108.234.75: /* Configuration */

=Configuration=

Wreckroom certs are located here:<code>
/usr/syno/etc/certificate/system/default
</code>

Navidrome

2025-07-18T19:30:43Z

66.108.234.75:

=Configuration=

Wreckroom certs are located here:

<syntaxhighlight>
/usr/syno/etc/certificate/system/default
</syntaxhighlight>

Navidrome

2025-07-18T19:29:43Z

66.108.234.75: Created page with "<syntaxhighlight> /usr/syno/etc/certificate/system/default </syntaxhightlight>"

<syntaxhighlight>
/usr/syno/etc/certificate/system/default
</syntaxhightlight>

Synology

2025-07-18T19:25:55Z

66.108.234.75: /* Public */

The Synology is a Network Attached Storage (NAS) and Linux Server that runs many different processes that are essential to [[Wreckroom]].

=Public=

===[[MediaWiki]]===
Uses MariaDB 10 and MediaWiki applications.

===[[Web Server]]===
NGINX reverse proxy runs wreckroom.nyc over 443/3000.

==Private==
===[[Media Server]]===
Serves files behind the [[VPN]].

===[[Navidrome]]===
Serves FLAC library

MediaWiki

2025-06-04T01:52:00Z

66.108.234.75:

WikiMedia Extensions
Pygments
clone into <code>extensions/</code>

<syntaxhighlight>
cd /volume2/web_packages/mediawiki/extensions
git clone https://github.com/wikimedia/mediawiki-extensions-SyntaxHighlight_GeSHi.git
</syntaxhighlight>

configure LocalSettings.php

<code>
vim /volume2/web_packages/mediawiki/LocalSettings.php
</code>

Add the following line:

<code>
wfLoadExtension( 'SyntaxHighlight_GeSHi' );
</code>

Run this line in terminal

<code>
php maintenance/update.php --quick
</code>

MediaWiki

2025-06-04T01:51:46Z

66.108.234.75:

WikiMedia Extensions
Pygments
clone into <code>extensions/</code>

<syntaxhighlight>
cd /volume2/web_packages/mediawiki/extensions
git clone https://github.com/wikimedia/mediawiki-extensions-SyntaxHighlight_GeSHi.git
</syntaxhighlight>

configure LocalSettings.php

<code>
vim /volume1/web_packages/mediawiki/LocalSettings.php
</code>

Add the following line:

<code>
wfLoadExtension( 'SyntaxHighlight_GeSHi' );
</code>

Run this line in terminal

<code>
php maintenance/update.php --quick
</code>

Web Server

2024-05-06T01:46:57Z

66.108.234.75:

The Synology hosts [https://wreckroom.nyc https://wreckroom.nyc] over 443 using a NGINX Reverse Proxy via <code>localhost:3000</code>.

=Updating Copy to Website=
# Commit changes on GitHub
## app/page.js (replace text in the <code><Card /></code> components
## app/components/layout/Mission.js
# in terminal, execute
## <code>ssh userName@wreckroom.nyc</code>
## <code>cd /volume2/wreckroom.nyc/wreckroom.nyc</code>
## <code>git pull</code>
## <code>sudo pm2 delete all</code>
## <code>sudo pm2 start "npm run dev" -- start</code>

==PM2==

'''PM2''' is a process manager that serves the [https://en.wikipedia.org/wiki/Npm npm] NextJS App [https://wreckroom.nyc https://wreckroom.nyc]

Upon restarting the Synology, you will to restart PM2 in <code>cd /volume1/wreckroom.nyc/wreckroom.nyc</code> by following these steps:

#End all processes: <code>sudo pm2 delete all</code>.
#Start the [https://en.wikipedia.org/wiki/Npm npm] process using '''PM2''': <code>sudo pm2 start npm -- start</code>.

If you are having issues with '''PM2''' process manager serving the NextJS app (when <code>sudo npm run start</code> works fine), use the above steps as well.

If having trouble running npm run start due to fonts or other issues try
<code>sudo pm2 start "npm run dev" -- start</code>

==Certificates==
If you make changes to a Certificate's FQDN, in addition to migrating the certificate, you ''must'' go to Control Panel / Login Portal / Advanced / Reverse Proxy. The hostname must be changed there for everything to work properly! This took half a day to figure out last time, hope it saves you some time in the future :)