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
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
|
<!DOCTYPE html>
<html lang="" xml:lang="" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8"/>
<meta content="pandoc" name="generator"/>
<meta content="width=device-width, initial-scale=1.0, user-scalable=yes" name="viewport"/>
<title>how-to-make-this-site</title>
<style>
html {
line-height: 1.5;
font-family: Georgia, serif;
font-size: 20px;
color: #1a1a1a;
background-color: #fdfdfd;
}
body {
margin: 0 auto;
max-width: 36em;
padding-left: 50px;
padding-right: 50px;
padding-top: 50px;
padding-bottom: 50px;
hyphens: auto;
overflow-wrap: break-word;
text-rendering: optimizeLegibility;
font-kerning: normal;
}
@media (max-width: 600px) {
body {
font-size: 0.9em;
padding: 1em;
}
h1 {
font-size: 1.8em;
}
}
@media print {
body {
background-color: transparent;
color: black;
font-size: 12pt;
}
p, h2, h3 {
orphans: 3;
widows: 3;
}
h2, h3, h4 {
page-break-after: avoid;
}
}
p {
margin: 1em 0;
}
a {
color: #1a1a1a;
}
a:visited {
color: #1a1a1a;
}
img {
max-width: 100%;
}
h1, h2, h3, h4, h5, h6 {
margin-top: 1.4em;
}
h5, h6 {
font-size: 1em;
font-style: italic;
}
h6 {
font-weight: normal;
}
ol, ul {
padding-left: 1.7em;
margin-top: 1em;
}
li > ol, li > ul {
margin-top: 0;
}
blockquote {
margin: 1em 0 1em 1.7em;
padding-left: 1em;
border-left: 2px solid #e6e6e6;
color: #606060;
}
code {
font-family: Menlo, Monaco, 'Lucida Console', Consolas, monospace;
font-size: 85%;
margin: 0;
}
pre {
margin: 1em 0;
overflow: auto;
}
pre code {
padding: 0;
overflow: visible;
overflow-wrap: normal;
}
.sourceCode {
background-color: transparent;
overflow: visible;
}
hr {
background-color: #1a1a1a;
border: none;
height: 1px;
margin: 1em 0;
}
table {
margin: 1em 0;
border-collapse: collapse;
width: 100%;
overflow-x: auto;
display: block;
font-variant-numeric: lining-nums tabular-nums;
}
table caption {
margin-bottom: 0.75em;
}
tbody {
margin-top: 0.5em;
border-top: 1px solid #1a1a1a;
border-bottom: 1px solid #1a1a1a;
}
th {
border-top: 1px solid #1a1a1a;
padding: 0.25em 0.5em 0.25em 0.5em;
}
td {
padding: 0.125em 0.5em 0.25em 0.5em;
}
header {
margin-bottom: 4em;
text-align: center;
}
#TOC li {
list-style: none;
}
#TOC ul {
padding-left: 1.3em;
}
#TOC > ul {
padding-left: 0;
}
#TOC a:not(:hover) {
text-decoration: none;
}
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
</head>
<body>
<nav id="TOC" role="doc-toc">
<h2 id="toc-title">Contents</h2>
<ul>
<li><a href="#background" target="_self">Background</a></li>
<li><a href="#what-is-a-web-server-and-how-do-i-run-one" target="_self">What is a web
server and how do I run one?</a>
<ul>
<li><a href="#getting-from-localhost-to-the-internet" target="_self">Getting from
localhost to the internet</a></li>
</ul></li>
<li><a href="#how-can-i-make-this-server-available-on-the-internet-cheaply-and-independently" target="_self">How
can I make this server available on the Internet <em>cheaply</em> and
<em>independently</em></a>
<ul>
<li><a href="#can-i-run-a-web-server-at-home" target="_self">Can I run a web server at
home</a></li>
<li><a href="#so-what-should-i-do" target="_self">So what should I do</a></li>
</ul></li>
<li><a href="#whats-a-domain-name" target="_self">What's a "Domain Name"</a></li>
<li><a href="#setup-https-and-tls-for-some-sense-of-security" target="_self">Setup
HTTPS and TLS, for some sense of security</a></li>
<li><a href="#perspective" target="_self">Perspective</a></li>
<li><a href="#references" target="_self">References</a>
<ul>
<li><a href="#terms-of-service-for-certain-isps" target="_self">Terms of service for
certain ISPs</a>
<ul>
<li><a href="#verizon" target="_self">Verizon</a></li>
<li><a href="#optimum" target="_self">Optimum</a></li>
<li><a href="#spectrum" target="_self">Spectrum</a></li>
<li><a href="#att" target="_self">AT&T</a></li>
<li><a href="#cox-communications" target="_self">Cox Communications</a></li>
</ul></li>
</ul></li>
</ul>
</nav>
<h2 id="background">Background</h2>
<p><em>TL;DR get to </em><a href="#thepoint" target="_self">the point</a></p>
<p>I think it was roughly the end of high school when I first had the
idea I wanted to make <em>some</em> kind of website. This would be
around 2010 and I did what I thought would be a good idea and bought a
book on the subject: "Web Sites for Dummies." I was dummy after
all...</p>
<p>I got up to hyper linking with the "a" tag until I hit a wall. I
don't want to link the exact page since I don't want to get sued, but it
basically read:</p>
<pre><code>Web design programs:
- Adobe Dreamweaver
- Adobe Contribute
- Microsoft Expression Web</code></pre>
<p>Well, damn. I didn't have any of those. And as a stingy high school
kid, I didn't want to buy anything. So I shelved that book and forgot
about for a while since making a website seemed too expensive and needed
too much flashy software to make it. I knew nothing about free software
at that age, other than music software like Audacity which is what I was
into at the time.</p>
<p>A few years later I caught a bit of a poetry bug--and maybe a bit of
a snooty college kid bug--and tried to run a blog. At that point, I had
learned about WordPress, which lets you easily make a space for sharing
writing, media, content, whatever really. And it's free as in
<em>freedom</em> as I understand since it's licensed under the GPL (if
you want to take the time to deploy it yourself). But they also give out
free .wordpress domains and some storage space with a snazzy dashboard
to manage it all.</p>
<p>I had fun with that one, I don't update it anymore, but it's still up
at <a href="https://postquantumpoetry.wordpress.com">postquantumpoetry.wordpress.com</a>.
WordPress got closer to what I wanted, but it still wasn't
<em>really</em> my site; it was WordPress's site unless I wanted to pay
the hosting and domain fee. It's pretty modest, but I wasn't sold on
sticking with a .com or .space domain, or even sticking with WordPress.
I was getting tired of blogging anyway. I was getting more interested in
the stuff that made it work; it seemed a lot more fruitful than writing
to no one.</p>
<p>It's now 2021, five years later, when I write this (and this website
isn't even finished yet). So what led me down the rabbit hole again? It
probably started where the last one left off, when I decided I wanted to
switch to more practical IT things over the academic things I had
previously wanted to pursue. I signed up for a Cybersecurity program,
somehow got in, and eventually managed to land an entry-level SOC role
after graduating. At this point, it was getting a little weird that I
had no web presence, especially after I decided to take down most of my
social media accounts a few years ago.</p>
<p>So I was back at "how do I make a website," again, but this time, I
at least had some understanding of what a server was and how networks
work. And more importantly, I had a better idea of what it meant for a
computer to be <em>mine</em>.</p>
<p>Even though--let's be real--it <em>still isn't.</em></p>
<p>I can't get high-speed Internet easily which I need to host a server
long-term so I'm stuck using some else's computer, otherwise called a
Virtual Private Server (VPS). Even if I could host at home, I'm still at
the mercy of my ISP.</p>
<p>Because of that, I think it's important to understand that "running
your own website" is not just a <em>technical</em> ordeal, but also an
<em>economic</em> one since you have to carefully think about what it
means to you to <em>own</em> your server, your software, and your
hardware. That doesn't mean it's hard to do, just that there's
options.</p>
<p><a id="thepoint"></a></p>
<h2 id="what-is-a-web-server-and-how-do-i-run-one">What is a web server
and how do I run one?</h2>
<p><em>TL;DR a web server is just a program that lets other computers on
a network view files in a chosen folder. All you need to do is download
a web server: apache and nginx are popular ones, but you can easily
program your own with web frameworks like <a href="https://flask.palletsprojects.com/en/2.0.x/">Flask</a> or <a href="https://facil.io/">Facil</a></em></p>
<p>You can run a web server for free right now. These instructions will
be for Linux just for consistency since I'm as used to setting this up
on a Windows server. If you've never used Linux, don't be scared! It's
very easy to setup and manage in Windows now with Windows Subsystem for
Linux. If you're on Windows, follow their guide <a href="https://docs.microsoft.com/en-us/windows/wsl/install">here</a>. It
should be pretty straightforward, but if you have any issues: 1) Make
sure you check your Windows version as noted in the "Prerequisites," 2)
Try a different distribution, like Debian with
<code>wsl --install -d Debian</code>. Once you're at a command prompt,
come back here.</p>
<p>There are many web servers out there, but I like nginx since the
configuration file is a bit easier to read than others. So let's install
it.</p>
<pre><code>$ sudo apt install nginx</code></pre>
<p>On Ubuntu or Debian, nginx puts the default server configuration in
the folder "/etc/nginx/sites-enabled/default". Open that in a text
editor like vim or nano, and you should see something like this
(neglecting the commented lines starting with "#"):</p>
<pre><code>server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
}</code></pre>
<p>For now, you don't need to change anything, so don't worry about what
it means.</p>
<p>But do note the directory set on "root." This is where the web server
looks for files and folders. You can change this, but usually, you don't
need too. Any files or folders you put under "/var/www/html" will be
included as part of the web server when viewed in a web browser.</p>
<p>So let's put some stuff there! If you're on WSL as mentioned before,
you can access your C drive at "/mnt/c". So let's say you had a folder
of cat pics in "C:\Users\username\Desktop\cats"; you can copy this into
your website by running:</p>
<pre><code>$ cp -vr /mnt/c/Users/username/Desktop/cats /var/www/html</code></pre>
<p>Run the server, then go to your web browser and type:
"http://localhost". You'll find a directory with your files in it! And
you can access them at "http://localhost/foldername/filename.extension".
Following our previous example, you can get your cats at
"https://localhost/cats".</p>
<h3 id="getting-from-localhost-to-the-internet">Getting from localhost
to the internet</h3>
<p>The problem is, only you and others on your home network can visit
your site right now.</p>
<p>Your computer's most likely behind your router's firewall, which will
not allow any traffic in. You'll need to forward a port from your router
(port 80 is for HTTP) to point to the device hosting the server.</p>
<p>Router's differ when it comes to to exact configuration, but MOST
routers will have some kind of steps similar to this:</p>
<ol type="1">
<li><p>Click "Advanced" then click "Firewall"</p></li>
<li><p>Scroll to the add new rule form</p></li>
<li><p>Put in the following values:</p></li>
</ol>
<ul>
<li>source/original port: 80</li>
<li>forward to address/device: your device's local ip</li>
<li>forward to/destination port: 80</li>
</ul>
<p>You can get your device's local ip by typing "ipconfig" (Windows) or
"ip a" (Linux). Typically it is listed first and will start with
"192.168" or "10.0" but it depends on the manufacturer. Here's my output
at home for example:</p>
<pre><code>1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 4c:cc:6a:93:eb:0b brd ff:ff:ff:ff:ff:ff
inet 192.168.1.202/24 brd 192.168.1.255 scope global dynamic noprefixroute enp7s0
valid_lft 74501sec preferred_lft 74501sec
inet6 fe80::4ecc:6aff:fe93:eb0b/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 82:e2:e4:c2:0c:a1 brd ff:ff:ff:ff:ff:ff permaddr 98:de:d0:f3:d6:ea</code></pre>
<p>The device "enp7s0" is my Ethernet adapter (starts with an 'e') and
my current local ip address for the device is shown. If you use wifi, it
will likely start with a "wl." Set the forwarding rule according to this
value.</p>
<p>Now get your <em>public</em> ip address at this site https://who.is/
and share it with your friends. Watch in horror as they access all the
files in the directory you launched the server!</p>
<h2 id="how-can-i-make-this-server-available-on-the-internet-cheaply-and-independently">How
can I make this server available on the Internet <em>cheaply</em> and
<em>independently</em></h2>
<p><i> TL;DR Expense scales with independence. It's possible to become
your own service provider, get IP addresses from ICANN, your own
hardware to host it, to host your cat pics; but it's also a lot of time,
work and money to do all that (<a href="https://hackaday.com/2018/09/20/one-mans-journey-to-become-his-own-isp/">this
guy</a> did it apparently, and so did <a href="https://en.wikipedia.org/wiki/Kiwi_Farms">Null</a>)</i></p>
<p>Most likely you'll want to rent someone else's server, usually a VPS.
</p>
<p>Once you understand the basic installation above, you can now
populate your site with content just by adding HTML files to your web
directory. You can use an HTML editor to write these, or you can
download a full content management system to help you. Here are some
options I know about:</p>
<ul>
<li><strong>You can just write the damn HTML and use apache or
nginx</strong></li>
</ul>
<p>This honestly is not that hard, it just takes long and takes away
from the joy of writing in my opinion. I personally have set up my own
little system where I write content in markdown and templates in the
Jinja template language to render it automatically. But if your content
is short and sweet, or you're mostly hosting files, writing a few basic
HTML files in vim or notepad and adding some CSS goes a long way. I
wrote my own view of the topic in the context of how I wrote this site
<a href="/tutorials/www/quick-intro-to-html-css.html">here</a>. And you
can find a number of great guides on how to write files, copy them and
manage them in the <a href="#references" target="_self">references</a>.</p>
<p>One easy way to create HTML templates with these servers is through
the use of "Server Side Includes," which essentially let you past one
html document into another. This varies by server, for example, nginx
has their own options and syntax detailed <a href="https://nginx.org/en/docs/http/ngx_http_ssi_module.html">here</a>.</p>
<ul>
<li><a href="https://neocities.org/"><strong>Neocities</strong></a></li>
</ul>
<p>Neocities is based on the old Geocities from the mid 90s which allows
simple static hosting and features and amazing array of creative
projects. Everything is managed through the website, and you can pay to
set your own custom <a href="#whats-a-domain-name" target="_self">domain name</a>.</p>
<ul>
<li><strong>Wordpress</strong> (but this time, you set it up)</li>
</ul>
<p>Before wordpress was a social media blogging thingamajig, it was just
a content management system to spin up a pretty blog. You can download
and install Wordpress by following:</p>
<p>https://wordpress.org/support/article/how-to-install-wordpress/</p>
<p>The benefit of installing yourself is enormous, since you have full
control and can even edit the source if you have the guts.</p>
<ul>
<li><a href="https://guides.github.com/features/pages/"><strong>Github
pages</strong></a></li>
</ul>
<p>In addition to hosting code repositories, you can host small sites on
github for mostly free. I've never used it, but I definitely would if I
needed something like a small wiki.</p>
<p>But once you have stuff to share, how do you keep this stuff
online?</p>
<h3 id="can-i-run-a-web-server-at-home">Can I run a web server at
home</h3>
<p>Technically yes, but practically probably not. At least not at a lot
of extra cost to you. If you do want to host a small thing at home, like
some text or some cat pics, a <a href="/tutorials/tor/how-to-host-a-tor-hidden-service.html">tor hidden
service</a> is a great option.</p>
<p>I spent a lot of time searching on this (you can find a full list of
references at the bottom), and I've even tested a little bit by hosting
game servers and web projects for code jams, but the problem is twofold.
First, if you are in the United States and not a business, you probably
have a standard plan with one of the major ISPs (Verizon, Optimum,
etc.). This limits you in a few ways.</p>
<ul>
<li><p>Your bandwidth is limited, which limits the amount of people you
can serve at one time <em>and</em> the rate you can transfer data to
them. Think laggy games and videos that take 10 years to
download.</p></li>
<li><p>Your ISP probably explicitly does not allow this (at least in the
US). I have <em>never</em> had my ISP complain about hosting small
personal servers at home, but I imagine if I hosted higher traffic
things, I would have some problems.</p></li>
</ul>
<h3 id="so-what-should-i-do">So what should I do</h3>
<p>As mentioned above, it kind of depends on what your hosting. A small
game server can be run just fine from home. A website with an email
server and other bells and whistles is another thing.</p>
<p>In those cases most people will find it cheapest to rent from a VPS
provider. VPS stands for "Virtual Private Server," which just means an
Internet-connected server stored somewhere in someone's private data
center. You pay them for the storage and to keep your server online and
accessible.</p>
<p>Once you've got enough content and a way to manage it, all you have
to do is just copy all that stuff over to your VPS. Usually that looks
like:</p>
<ul>
<li>Installing a web server and a CMS tweaked to your liking</li>
<li>Copying over your stuff to the web directory</li>
<li>Opening up your ports to the outside world.</li>
</ul>
<p>And in a nutshell that's it. There's fancy stuff of course, like
you'll want a <a href="#whats-a-domain-name" target="_self">domain name</a> probably
and I'll talk about that too, but at this point, your stuff is on the
Internet! Just tell your friends to paste in your public ip address
(your VPS provider will tell you this) and there's your stuff!</p>
<h2 id="whats-a-domain-name">What's a "Domain Name"</h2>
<p>Expecting people to save your IP address is not really a good idea
though. It's better to have an easy name they can remember. Enter DNS:
the Domain Name System. If an IP address is a telephone number, DNS is
the telephone book. ICANN and IANA host the top level servers, which
point to local domain registries who buy names like "mjfer.net" on
behalf of their customers.</p>
<p>The actual business of domain names is complicated and not something
I understand all that well. But setting up a domain name to point to an
IP address is typically easy, once you've chosen a domain registrar
(just search that online and you'll find a ton) and name you like. Be
aware that shorter names are rarer and usually more expensive and
different TLDs--that is, the ending parts like ".net" and ".io,"--will
be priced differently.</p>
<p>Once you have a domain name, you'll need to set up a DNS record.
Again, this varies a bit based on the provider, but all will have some
kind of text input or API where you can edit DNS records. You'll want to
make two records</p>
<ul>
<li><p>A Type A that will be your main record</p>
<ul>
<li><p>set the HOST to your domain name (like mjfer.net)</p></li>
<li><p>set the ANSWER to your IP address (like 8.9.36.54)</p></li>
</ul></li>
<li><p>A CNAME record, that will help point to all your other
records</p>
<ul>
<li><p>set the HOST to your domain name, with a wildcard subdomain (like
*.mjfer.net)</p></li>
<li><p>set the ANSWER to your main record (like mjfer.net)</p></li>
</ul></li>
</ul>
<p>The reason for the second record is in case you want to set
subdomains on the same IP address like "git.mjfer.net".</p>
<p>Wait a few minutes for the DNS servers to update and you should now
be able access your server by name.</p>
<h2 id="setup-https-and-tls-for-some-sense-of-security">Setup HTTPS and
TLS, for some sense of security</h2>
<p>A decade of half-though through security advice has convinced
everyone that HTTPS and <em>only</em> HTTPS is secure. This is simply
not true. Using HTTP alone doesn't inherently make you insecure and
using HTTPS doesn't automatically guarantee the app your communicating
with is secure.</p>
<p>What HTTPS means is that the <em>data you send to the server</em> and
the <em>data the server sends back</em> is encrypted. This only provides
security in contexts where you're entering information like a credit
card number or a password; or in the reverse case when the server is
authenticating you. In those cases <em>you need HTTPS</em>. But if
you're just requesting a text document, or a cat picture, and not
sending any data, HTTP is perfectly acceptable for retrieving that
information. HTTPS is also no guarantee that the information your
retrieving is actually what you want. There's plenty of malware and
other nasty things over HTTPS, just because it's sent encrypted doesn't
make it safe.</p>
<p>Web browsers have largely responded to this fact by assuming that
HTTP is always insecure and printing a warning when you visit a site
without HTTPS enabled. Unfortunately, most users interpret this to mean
the site is somehow dangerous, even if it doesn't collect any
information about the user. Because of that, most you will want to go
the extra mile to make your visitors feel warm and fuzzy inside and
implement HTTPS.</p>
<p>Fortunately, this is now much easier than is used to be thanks to <a href="https://letsencrypt.org/">LetsEncrypt</a>. LetsEncrypt generously
serves as a free certificate authority, which allows you to generate
signed certificates that are recognized by every web browser in the
world. The tool they recommend, <a href="https://certbot.eff.org/">certbot</a> is painless to install. I've
rarely had to do much more than "certbot certonly" and follow the
prompts to get a certificate. Once you've obtained one, add it to <a href="https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html">apache</a>
or <a href="https://www.nginx.com/blog/nginx-ssl/#Examples">nginx</a>,
switch the port to 443 instead of 80 and bam, you've got HTTPS!</p>
<h2 id="perspective">Perspective</h2>
<p>What I tried to present here was the brief overview of how you get
from files on your computer to files accessible of the Internet. The
full picture though is something you need to seek out yourself. I intend
to add more guides on how I manage this site, but there is so much
material out there already it hardly feels worth adding to. I hope at
the very least to have got you through the start.</p>
<h2 id="references">References</h2>
<ol type="1">
<li>https://dataswamp.org/~solene/2021-07-23-why-selfhosting-is-important.html</li>
<li>https://selfhostedweb.org/yourserver/</li>
<li>https://www.howtogeek.com/362602/can-you-host-a-web-server-on-your-home-internet-connection/</li>
<li>https://googiehost.com/blog/create-your-own-server-at-home-for-web-hosting/</li>
<li>https://en.wikipedia.org/wiki/ICANN</li>
<li>https://landchad.net/</li>
</ol>
<h3 id="terms-of-service-for-certain-isps">Terms of service for certain
ISPs</h3>
<p>There's always more ISPs out there, but I went the one's I'm most
familiar with in my area. I'll probably expand this as I go, let me know
if there are important ones in your area worth listing here for
others.</p>
<h4 id="verizon">Verizon</h4>
<ul>
<li>https://www.verizon.com/support/lte-home-internet-legal/
<ul>
<li>Point 5.</li>
</ul></li>
<li>https://www.verizon.com/support/residential/announcements/terms-of-service
<ul>
<li>p. 23, section 1 "Restrictions on use"</li>
</ul></li>
</ul>
<h4 id="optimum">Optimum</h4>
<ul>
<li>https://www.optimum.net/pages/terms/general-residential.html
<ul>
<li>Point 11 a. "Residential Use"</li>
</ul></li>
<li>https://www.optimum.com/terms-of-service/residential/internet
<ul>
<li>Point 11. "Additional Restrictions"</li>
</ul></li>
</ul>
<h4 id="spectrum">Spectrum</h4>
<ul>
<li>https://www.spectrum.com/policies/internet-use-policy
<ul>
<li>Point 2 j through l</li>
</ul></li>
</ul>
<h4 id="att">AT&T</h4>
<ul>
<li>https://www.att.com/legal/terms.consumerServiceAgreement.html
<ul>
<li>2.5.3 Examples of Prohibited Network Uses of Data Service</li>
</ul></li>
</ul>
<h4 id="cox-communications">Cox Communications</h4>
<ul>
<li>https://www.cox.com/aboutus/policies/acceptable-use-policy.html
<ul>
<li><ol type="1">
<li>Prohibited Activities, point 5</li>
</ol></li>
</ul></li>
</ul>
</body>
</html>
|
