Fix remote api key schema (#83)

* fix: add remote_api_key column to initial database schema

* chore: bump version to 1.3.1 - fix database schema bug

Author: mostafa-wahied

.gitignore

@@ -8,9 +8,7 @@ build/
 misc/
 
 # Ignore specific backend files
-backend/data/*.db
-backend/data/*.json
-backend/data/*.md
+backend/data/*
 
 # Test results and API testing artifacts
 backend/api-tests/

CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to portracker will be documented in this file.
 
+## [1.3.1] - 2026-02-03
+
+### Fixed
+
+- **Database Schema**: Fixed missing `remote_api_key` column in initial database creation that caused "no such column" errors for fresh installations (resolves #82)
+
 ## [1.3.0] - 2026-02-02
 
 **Highlights**

backend/db.js

@@ -36,6 +36,7 @@ if (!tableExists) {
       unreachable INTEGER DEFAULT 0,
       api_key TEXT,
       api_key_created_at TEXT,
+      remote_api_key TEXT,
       FOREIGN KEY (parentId) REFERENCES servers(id)
     );
     

backend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "backend",
-  "version": "1.2.0",
+  "version": "1.3.1",
   "description": "",
   "main": "index.js",
   "scripts": {

package.json

@@ -1,6 +1,6 @@
 {
   "name": "portracker",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "A multi-platform port-tracking dashboard",
   "main": "backend/index.js",
   "scripts": {