diff --git a/deploy.sh b/deploy.sh new file mode 100755 index 0000000..0cde4bc --- /dev/null +++ b/deploy.sh @@ -0,0 +1,20 @@ +#!/bin/bash +set -e + +REMOTE_PATH="/home/admin/www/jasonhilder.dev/" + +echo "Deploying to server..." + +# Sync local project to server over SSH, only transferring changed files. +# -a = archive mode (preserves permissions, timestamps etc) +# -v = verbose output +# -z = compress data during transfer +# --delete = remove files on server that no longer exist locally +# --exclude = skip these files/dirs, they don't belong on the server +rsync -avz --delete \ + --exclude='.git' \ + --exclude='README.md' \ + --exclude='deploy.sh' \ + ./ "server:$REMOTE_PATH" + +echo "Deploy complete." diff --git a/index.php b/index.php new file mode 100644 index 0000000..c550b4c --- /dev/null +++ b/index.php @@ -0,0 +1,3 @@ + 'web/pages/home.php', + '/about' => 'web/pages/about.php', +]; + +$base = realpath(ROOT . '/web/pages'); + +if ($base === false) { + http_response_code(500); + exit; +} + +if (array_key_exists($uri, $routes)) { + $real = realpath(ROOT . '/' . $routes[$uri]); + + if ($real !== false && str_starts_with($real, $base . DIRECTORY_SEPARATOR)) { + require $real; + } else { + http_response_code(403); + exit; + } +} else { + http_response_code(404); + require ROOT . '/web/pages/404.php'; +} diff --git a/static/css/app.css b/static/css/app.css deleted file mode 100644 index 136769c..0000000 --- a/static/css/app.css +++ /dev/null @@ -1,4 +0,0 @@ -body { - background-color: #191919; - color: #ffffff; -} diff --git a/web/pages/404.php b/web/pages/404.php new file mode 100644 index 0000000..00fceff --- /dev/null +++ b/web/pages/404.php @@ -0,0 +1,6 @@ + + +
Seems this is not what you are looking for...
+ + diff --git a/web/pages/home.php b/web/pages/home.php new file mode 100644 index 0000000..f16fb12 --- /dev/null +++ b/web/pages/home.php @@ -0,0 +1,33 @@ + + ++ I build backend systems, data pipelines, and internal tooling. I have a bias toward simplicity and the shortest path + to something solid — built to last, not just to ship. I'd rather understand a system deeply than paper over it with abstractions. +
++ When I'm not working, I'm either in the water surfing, spending time with my girlfriend, playing games, or digging into systems programming + — CPU simulators, indie game experiments, and the custom tooling that tends to grow around them. I run Linux, daily-drive a + Happy Hacking Keyboard, and have strong opinions about my desktop setup — some might call it a problem, I call it a hobby. +
+Values I hold in work and life
----------------------------------------------
+ +