 |
t001-new-homepage.html - adamsgaard.dk - my academic webpage |
 |
git clone git://src.adamsgaard.dk/adamsgaard.dk |
 |
Log |
|
Files |
|
Refs |
|
README |
|
LICENSE |
|
--- |
|
t001-new-homepage.html (3206B) |
|
--- |
|
1 <p>I have had my own webpage since 2002 |
|
2 (<a href="https://web.archive.org/web/20020203191552/http://www.a-d-c.dk… |
|
3 <a href="https://web.archive.org/web/2018*/cs.au.dk/~adc">cs.au.dk/~adc<… |
|
4 <a href="https://web.archive.org/web/20160904034204/https://adamsgaard.d… |
|
5 I use a webpage as a place to keep my contact information, |
|
6 software, notes, and research. The previous iteration (Fig. 1) |
|
7 was inspired by the 2015 April 1st retro-version of of <a |
|
8 href="https://gentoo.org">gentoo.org</a>, bringing back memories of the |
|
9 computing of yesteryear.</p> |
|
10 |
|
11 <figure class="pagefigure"> |
|
12 <img src="img/adamsgaard.dk-old.png" |
|
13 alt="Old apperance of adamsgaard.dk" |
|
14 class="pageimg"/> |
|
15 <figcaption> |
|
16 Fig. 1: Appearance of adamsgaard.dk until fall 2019 |
|
17 </figcaption> |
|
18 </figure> |
|
19 |
|
20 <p>The previous backend was a <a href="https://www.debian.org">Debian |
|
21 GNU/Linux</a> virtual machine, first running at home |
|
22 and then in the cloud. It dynamically served the pages |
|
23 with <a href="https://www.apache.org">Apache</a> and <a |
|
24 href="https://www.php.net">PHP</a>. However, PHP is notoriously insecure, |
|
25 as evident by the |
|
26 <a href="https://www.cvedetails.com/vulnerability-list.php?vendor_id=74&… |
|
27 Apache is <a href="https://www.cvedetails.com/vulnerability-list/vendor_… |
|
28 |
|
29 <p>This weekend I finally made the long-overdue transition to a <a |
|
30 href="https://en.wikipedia.org/wiki/Static_web_page">static web page</a>, |
|
31 which improves security and performance. The backend is an |
|
32 <a href="https://www.openbsd.org">OpenBSD</a> instance at a cloud provid… |
|
33 There's a plethora of free static hosting providers available, but I |
|
34 prefer running and maintaining a server myself. |
|
35 The SSL certificate is provided by <a href="https://letsencrypt.org">Let… |
|
36 Encrypt</a>. |
|
37 The html front end is generated using |
|
38 <a href="https://www.codemadness.nl">Hiltjo Posthuma</a>'s |
|
39 <a href="https://git.codemadness.nl/saait">saait</a> and |
|
40 <a href="https://git.codemadness.nl/stagit">stagit</a>.</p> |
|
41 |
|
42 <p>I am keeping the retro theme, but all CSS is reduced to a bare |
|
43 minimum. The page is entirely free of cookies, javascript, and |
|
44 tracking. It is also 100% compatible with terminal browsers (Fig. 2).</p> |
|
45 |
|
46 <figure class="pagefigure"> |
|
47 <img src="img/adamsgaard.dk-new-w3m.png" |
|
48 alt="New adamsgaard.dk" |
|
49 class="pageimg"/> |
|
50 <figcaption> |
|
51 Fig. 2: New adamsgaard.dk seen with <a |
|
52 href="http://w3m.sourceforge.net/">w3m</a>. |
|
53 </figcaption> |
|
54 </figure> |
|
55 |
|
56 <p>I moved all of my personal software projects to my own git server at |
|
57 <a href="https://src.adamsgaard.dk">src.adamsgaard.dk</a>. I do not tru… |
|
58 corporations like Github (Microsoft), Gitlab, Sourceforce, etc., to alwa… |
|
59 act in the users' best interest. However, for the time being I will |
|
60 continue to contribute to other software projects on these platforms.</p> |
|
61 My git server has a <a href="https://src.adamsgaard.dk">web interface</a> |
|
62 which provides an overview of projects, commits, and files. Git access |
|
63 is possible through git (read only) and ssh (r/w) protocols.</p> |
|
64 |
|
65 <p>Please <a href="contact.html">let me know</a> if you encounter any |
|
66 problems with the new infrastructure.</p> |
