extend impressum
This commit is contained in:
parent
8c5574c054
commit
82a4bfab86
@ -1,27 +1,6 @@
|
||||
<!-- { "toc": "compute", "title": "Projects - Just for Fun" } -->
|
||||
|
||||
<h1>So ugly ... why not Wordpress?</h1>
|
||||
<p>
|
||||
I shut down my homepage at wordpress.com since it was absolutely unclear to me which data was collected there. I decided to run the homepage on my own server again, since I know exactly which data is collected here: There is the Apache log with the requesters IP stripped away:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<pre>
|
||||
<code language="Apache">
|
||||
CustomLog "logs/access_log" common
|
||||
#LogFormat "%h %l %u %t \"%r\" %>s %b" common
|
||||
LogFormat "%l %u %t \"%r\" %>s %b" common
|
||||
</pre>
|
||||
</code>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Nothing else. The homepage engine just logs which post or page is accessed and served, nothing more. If you like to have a look: <a href="https://gitlab.com/wolutator/homepage" target="_blank">https://gitlab.com/wolutator/homepage</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
And since I'm quite bad in CSS, it currently looks so ugly.
|
||||
</p>
|
||||
|
||||
|
||||
<h1>My Blog</h1>
|
||||
|
||||
@ -2,4 +2,81 @@
|
||||
<h1>Impressum</h1>
|
||||
|
||||
Wolfgang Hottgenroth<br/>
|
||||
Eupenstr. 20<br/>
|
||||
45259 Essen<br/>
|
||||
<address>woho@hottis.de</address><br/>
|
||||
|
||||
<p>
|
||||
This is a hobby-only homepage without any advertising or other commercial interests.
|
||||
</p>
|
||||
|
||||
<h1>So ugly ... why not Wordpress?</h1>
|
||||
<p>
|
||||
I shut down my homepage at wordpress.com since it was absolutely unclear to me which data was collected there. I decided to run the homepage on my own server again.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Although according to Art. 2 (2) c of DSGVO that regulation is completely irrelevant for me, since this is a hobby-only blog without any advertising or commercial interests, it appeared to me, that limiting the number of collected data could be a good idea.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
For this system I know exactly which data is collected here: There is the Apache httpd running on an old PowerPC MacMini with OpenBSD bastion host, which proxies requests to the homepage engine. For the Apache log the requesters IP has been stripped away:
|
||||
<p>
|
||||
<pre>
|
||||
<code language="Apache">
|
||||
CustomLog "logs/access_log" common
|
||||
#LogFormat "%h %l %u %t \"%r\" %>s %b" common
|
||||
LogFormat "%l %u %t \"%r\" %>s %b" common
|
||||
</pre>
|
||||
</code>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The logfile looks like this now:
|
||||
</p>
|
||||
<p>
|
||||
<pre>
|
||||
- - [25/May/2018:12:43:58 +0200] "GET /wolutator HTTP/1.1" 302 76
|
||||
- - [25/May/2018:12:43:58 +0200] "GET /wolutator/index HTTP/1.1" 304 -
|
||||
- - [25/May/2018:12:43:58 +0200] "GET /wolutator/files/default.css HTTP/1.1" 304 -
|
||||
- - [25/May/2018:12:43:58 +0200] "GET /wolutator/files/highlight/styles/default.css HTTP/1.1" 304 -
|
||||
- - [25/May/2018:12:43:58 +0200] "GET /wolutator/files/highlight/highlight.pack.js HTTP/1.1" 304 -
|
||||
- - [25/May/2018:12:43:58 +0200] "GET /wolutator/files/cropped-img_2723.jpg HTTP/1.1" 304 -
|
||||
- - [25/May/2018:12:43:59 +0200] "GET /favicon.ico HTTP/1.1" 404 209
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The homepage engine is running on an old Intel MacMini with Debian. It just logs which post or page is accessed and served, nothing more. If you like to have a look: <a href="https://gitlab.com/wolutator/homepage" target="_blank">https://gitlab.com/wolutator/homepage</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The logging of the homepage engine looks like this:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<pre>
|
||||
wn@mac:/opt/services/homepage$ npm start -- -c homepage.conf
|
||||
|
||||
> homepage@1.0.0 start /opt/services/homepage
|
||||
> node dist/main.js "-c" "homepage.conf"
|
||||
|
||||
12:57:59.910 [ II ] Homepage starting
|
||||
12:57:59.922 [ II ] building toc
|
||||
12:57:59.937 [ II ] Homepage running
|
||||
12:57:59.938 [ II ] Homepage is listening
|
||||
12:58:19.008 [ II ] redirecting / to /index
|
||||
12:58:19.142 [ II ] /opt/services/homepage/docroot/index.pag not yet in cache
|
||||
12:58:24.178 [ II ] /opt/services/homepage/docroot/posts/2018-04-30.01/article.pag not yet in cache
|
||||
12:58:25.550 [ II ] /opt/services/homepage/docroot/index.pag served from cache
|
||||
12:58:26.985 [ II ] /opt/services/homepage/docroot/pages/impressum.pag not yet in cache
|
||||
12:58:29.647 [ II ] /opt/services/homepage/docroot/index.pag served from cache
|
||||
12:58:31.060 [ II ] /opt/services/homepage/docroot/posts/2018-02-22.01/article.pag not yet in cache
|
||||
12:58:35.230 [ II ] /opt/services/homepage/docroot/index.pag served from cache
|
||||
12:58:37.717 [ II ] /opt/services/homepage/docroot/index.pag served from cache
|
||||
</pre>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
And since I'm quite bad in CSS, it currently looks so ugly.
|
||||
</p>
|
||||
@ -1,8 +1,8 @@
|
||||
body {
|
||||
font-family: "Optima", sans-serif;
|
||||
font-size: 16px;
|
||||
margin: 0 5% 0 5%;
|
||||
width: 1080px;
|
||||
margin: 20px 10% 0 10%;
|
||||
width: 80%;
|
||||
background-color: lightblue;
|
||||
}
|
||||
|
||||
|
||||
@ -1,50 +0,0 @@
|
||||
0 info it worked if it ends with ok
|
||||
1 verbose cli [ '/usr/bin/node',
|
||||
1 verbose cli '/usr/bin/npm',
|
||||
1 verbose cli 'start',
|
||||
1 verbose cli '--',
|
||||
1 verbose cli '-c',
|
||||
1 verbose cli 'homepage.' ]
|
||||
2 info using npm@3.10.10
|
||||
3 info using node@v6.14.2
|
||||
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
|
||||
5 info lifecycle homepage@1.0.0~prestart: homepage@1.0.0
|
||||
6 silly lifecycle homepage@1.0.0~prestart: no script for prestart, continuing
|
||||
7 info lifecycle homepage@1.0.0~start: homepage@1.0.0
|
||||
8 verbose lifecycle homepage@1.0.0~start: unsafe-perm in lifecycle true
|
||||
9 verbose lifecycle homepage@1.0.0~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/opt/services/homepage/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games://opt/jdk1.8.0_152/bin:/opt/apache-maven-3.5.2/bin
|
||||
10 verbose lifecycle homepage@1.0.0~start: CWD: /opt/services/homepage
|
||||
11 silly lifecycle homepage@1.0.0~start: Args: [ '-c', 'node dist/main.js "-c" "homepage."' ]
|
||||
12 silly lifecycle homepage@1.0.0~start: Returned: code: 1 signal: null
|
||||
13 info lifecycle homepage@1.0.0~start: Failed to exec start script
|
||||
14 verbose stack Error: homepage@1.0.0 start: `node dist/main.js "-c" "homepage."`
|
||||
14 verbose stack Exit status 1
|
||||
14 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
|
||||
14 verbose stack at emitTwo (events.js:106:13)
|
||||
14 verbose stack at EventEmitter.emit (events.js:191:7)
|
||||
14 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
|
||||
14 verbose stack at emitTwo (events.js:106:13)
|
||||
14 verbose stack at ChildProcess.emit (events.js:191:7)
|
||||
14 verbose stack at maybeClose (internal/child_process.js:920:16)
|
||||
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
|
||||
15 verbose pkgid homepage@1.0.0
|
||||
16 verbose cwd /opt/services/homepage
|
||||
17 error Linux 4.9.0-6-amd64
|
||||
18 error argv "/usr/bin/node" "/usr/bin/npm" "start" "--" "-c" "homepage."
|
||||
19 error node v6.14.2
|
||||
20 error npm v3.10.10
|
||||
21 error code ELIFECYCLE
|
||||
22 error homepage@1.0.0 start: `node dist/main.js "-c" "homepage."`
|
||||
22 error Exit status 1
|
||||
23 error Failed at the homepage@1.0.0 start script 'node dist/main.js "-c" "homepage."'.
|
||||
23 error Make sure you have the latest version of node.js and npm installed.
|
||||
23 error If you do, this is most likely a problem with the homepage package,
|
||||
23 error not with npm itself.
|
||||
23 error Tell the author that this fails on your system:
|
||||
23 error node dist/main.js "-c" "homepage."
|
||||
23 error You can get information on how to open an issue for this project with:
|
||||
23 error npm bugs homepage
|
||||
23 error Or if that isn't available, you can get their info via:
|
||||
23 error npm owner ls homepage
|
||||
23 error There is likely additional logging output above.
|
||||
24 verbose exit [ 1, true ]
|
||||
Loading…
x
Reference in New Issue
Block a user