added toc
This commit is contained in:
parent
a07e14676f
commit
e0965dbf1c
@ -11,7 +11,7 @@ slug: 002
|
||||
|
||||
## Introduction
|
||||
|
||||
You wan't to get started with self-hosting. This means you will need a computer that will be your server. But what makes a good server?
|
||||
You want to get started with self-hosting. This means you will need a computer that will be your server. But what makes a good server?
|
||||
|
||||
First, while dedicated server equipment does exist, in the case of the homebrew server it is more helpful to think of a 'server' as a function rather than as a special machine.
|
||||
|
||||
|
@ -9,10 +9,3 @@ Category: fundamentals
|
||||
slug: 001
|
||||
|
||||
This series is a starting point for people looking to host their own on-line services from home. A good place to start is by reading the [homebrewserver.club principles]({filename}manifesto.md) on to understand why we make the choices we do. Then have a look at the [hardware guide](hwguide) or [setting up a server behind your home router.]({filename}portforwarding.md)
|
||||
|
||||
The Homebrewserver.club principles
|
||||
What makes a good homebrew server (hardware guide)
|
||||
Setting up a server behind a home router
|
||||
Setting up a webserver
|
||||
Using SSH to connect to your home brew server
|
||||
Basic security considerations
|
||||
|
@ -7,6 +7,8 @@ Status: published
|
||||
Category: fundamentals
|
||||
slug: 006
|
||||
|
||||
[TOC]
|
||||
|
||||
## Promote approaches, not apps
|
||||
We privilege general approaches over particular software applications. We try to contextualize our technical choices socially, politically and economically to provide in-depth understanding and prevent The Best Way™ solutionism. For these reasons we like free and open source software as a starting point and try to provide documentation for others to learn as well.
|
||||
|
||||
|
@ -7,6 +7,8 @@ Summary: How to set up a spare olimex board as a networked backup disk
|
||||
Category: fundamentals
|
||||
slug: 007
|
||||
|
||||
[TOC]
|
||||
|
||||
#Introduction
|
||||
|
||||
The idea behind this setup is to make a so-called NAS (networked attached storage) which can be used as a remote back-up drive for your data. The setup is really meant as a low power, 'set and forget' solution. It connects to a public server via a VPN so it isn't publically accessible and doesn't need any open ports in a home router.
|
||||
|
@ -9,6 +9,8 @@ Image: images/port_forwarding.svg
|
||||
Status: published
|
||||
slug: 005
|
||||
|
||||
[TOC]
|
||||
|
||||
# UNDER CONSTRUCTION
|
||||
|
||||
##Introduction
|
||||
|
@ -10,6 +10,8 @@ Status: published
|
||||
Category: fundamentals
|
||||
slug: 003
|
||||
|
||||
[TOC]
|
||||
|
||||
## Introduction
|
||||
|
||||
Some of the essential things that separate a server from other computers is that first they are usually not where you are and second that often come without screen and keyboard. With homebrewservers this is particularly the case when using Single Board Computers (SBC).
|
||||
|
Loading…
Reference in New Issue
Block a user