blob: a6538aa207f13ddc02957968b4c96b701ff47b81 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
<!DOCTYPE html>
<head>
<title>Moving This Site</title>
<meta charset="utf-8"/>
<link rel="stylesheet" href="https://hairydiode.xyz/style.css"/>
<link rel="icon" type="image/png" href="https://hairydiode.xyz/img/fav/logo.png"/>
</head>
<body>
<div class="content">
<pre>
<!--
123456789-223456789-323456789-423456789-523456789-623456789-723456789-8234567890
一二三四
-->--------------------------------------------------------------------------------
<a href="https://hairydiode.xyz">>HairyDiode</a>
--------------------------------------------------------------------------------
<!--
123456789-223456789-323456789-423456789-523456789-623456789-723456789-8234567890
一二三四-->Moving This Site 6-26-2018
--------------------------------------------------------------------------------
So I've recently just moved this site away from github to my own VPS, as well as
all my git repos.
For those of you that are new, you'll notice that this site is entirely static
and all the pages are basically glorified text files. THat's the point, Text is
main content of this site and I don't want to serve bloated multi-megabyte files
just to deliver that. The fanciest thing I have on this site is a custom font
for <a href="https://hairydiode.xyz/iokalant">Iokalant</a>.
If you want to put a name to this style, call it web brutalist.
The way the site works now is this:
-I setup a bare git repo on my VPS containing the <a href="https://hairydiode.xyz/cgit/hairydiode">hairydiode git repo</a>
-In the post-receive hook of the repo it checks out the repository to
/var/www/html
-Apache2 is setup to serve those files
-The 'rewrite' module allowing me to remove the .html extensions from files, cgit
allows me to show my git repos in a web interface and I get my ssl certificates
from Let's Encrypt, whose <a href="https://certbot.eff.org/">certbot</a> takes care of setting up https on the apache
server.
It's a standard setup and if you want to read about it else where see the guide
from Digital Ocean on <a
href="https://www.digitalocean.com/community/tutorials/how-to-set-up-automatic-deployment-with-git-with-a-vps">Git Deployment</a>, and <a href="https://www.digitalocean.com/community/tutorials/how-to-configure-the-apache-web-server-on-an-ubuntu-or-debian-vps">Setting Up Apache</a>. Also <a href="https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server">This Guide</a>
for setting up a git server.
Some Caveats:
-If you're cloning a repository from somewhere else make sure:
--That the repository is chowned to the user 'git'
--Make sure the repository is bare. To do this, simply replace the folder
containing the repo with the .git folder beneath it, then type:
$ git config --bool core.bare true
to tell git that the repo is now bare.
-Make sure that the 'git' user has permisions to the deploy repository
-When enabling cgit, make sure to enable cgi with:
$ a2enmod cgi
-When making any change to apache2, make sure to restart it with:
$ systemctl restart apache2
</pre>
</div>
<br>
<br>
</body>
<!--
if you're digging in the src you might be interested in how this site works
here: https://hairydiode.xyz/meta2
-->
|
