2021-10-10 21:31:21 +00:00
|
|
|
# diyhosting.bhh.sh ([https://diyhosting.bhh.sh](https://diyhosting.bhh.sh))
|
2021-06-29 12:30:52 +00:00
|
|
|
|
2021-10-10 21:31:21 +00:00
|
|
|
A site dedicated to share self-hosting knowledge
|
2021-06-29 12:30:52 +00:00
|
|
|
|
|
|
|
Simple step-by-step text and image-based tutorials for creating websites, email servers, chat servers, server administration and everything else.
|
|
|
|
|
|
|
|
Suggestions welcome.
|
2021-06-30 20:43:18 +00:00
|
|
|
|
2021-07-01 12:45:52 +00:00
|
|
|
## Submission guidelines
|
2021-06-30 20:43:18 +00:00
|
|
|
|
|
|
|
- follow the general style of pre-existing articles
|
2021-07-01 12:45:52 +00:00
|
|
|
- use the root user (i.e. no `sudo`) unless there is a specific need.
|
|
|
|
- do not preface commands with `$` or `#` or anything.
|
2021-06-30 20:43:18 +00:00
|
|
|
- use `.svg` files for icons/logos and for illustrative images, keep filesize low
|
2021-07-01 12:45:52 +00:00
|
|
|
- Use `example.org`
|
|
|
|
- custom command/file info should be highlighted with `<strong>` tags
|
|
|
|
|
|
|
|
### On `<pre>` tags
|
|
|
|
|
|
|
|
|
|
|
|
In-line code should be in `<code>` tags, while codeblocks should be in a `<code>` tag *inside* of a `<pre>` tag.
|
|
|
|
`<pre>` allows formatting preserving whitespace.
|
|
|
|
That said, do *not* format `<pre>` tags as following:
|
|
|
|
|
|
|
|
```
|
|
|
|
<pre><code>
|
|
|
|
echo "Here is a command."
|
|
|
|
echo "Here is another."
|
|
|
|
</code></pre>
|
|
|
|
```
|
|
|
|
|
|
|
|
but do it like this:
|
|
|
|
|
|
|
|
```
|
|
|
|
<pre><code>echo "Here is a command."
|
|
|
|
echo "Here is another."</code></pre>
|
|
|
|
```
|
|
|
|
|
|
|
|
**All** whitespace, including tabbing in and initial and final newlines are displayed by `<pre>`.
|
|
|
|
To maintain consistency and avoid goofy-looking extra lines, add no extra whitespace.
|