From 0d5cb25ad2c2b4dae052b9e065a1517d5b05b160 Mon Sep 17 00:00:00 2001 From: Zef Hemel Date: Wed, 31 Jul 2024 12:49:16 +0200 Subject: [PATCH] Move Deno Deploy to network and internet deployment in docs --- website/Install.md | 1 - website/Install/Network and Internet.md | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/website/Install.md b/website/Install.md index 4a53919c..f353f887 100644 --- a/website/Install.md +++ b/website/Install.md @@ -11,7 +11,6 @@ You have a few options here: 1. Installation via [[Install/Docker]] (the awesome container runtime): recommended if you already have Docker installed 2. Installation via [[Install/Deno]] (the awesome JavaScript runtime): recommended if you intend to hack on SilverBullet itself later on -3. More advanced: deploy directly to the cloud via [[Install/Deno Deploy]] # Non-local access Once you got a comfortable set running locally, you may want to look at options to expose your setup to your [[Install/Network and Internet]]. diff --git a/website/Install/Network and Internet.md b/website/Install/Network and Internet.md index d52001f6..46bc8000 100644 --- a/website/Install/Network and Internet.md +++ b/website/Install/Network and Internet.md @@ -14,3 +14,4 @@ People have found various simple to more complex ways of achieving this. * Using [[Deployments/ngrok]] is likely the easiest solution to exposing your _locally running_ SilverBullet to the Internet. Note that “locally running” can mean your own local machine, but can still refer to running it on a server in your network (like a Raspberry Pi). * [[Deployments/Caddy]]: the easiest solution to expose SilverBullet running on a publicly accessible server to the Internet (but local network as well using Tailscale) * [[Authelia]] setup hints +* Deploy directly to the cloud via [[Install/Deno Deploy]]