WEBVTT

1
00:00:00.080 --> 00:00:02.720
<v Speaker 1>Have you ever looked at the whole world of servers,

2
00:00:02.919 --> 00:00:06.599
<v Speaker 1>IT infrastructure and just thought, wow, that's a completely different language,

3
00:00:06.799 --> 00:00:08.400
<v Speaker 1>you know, intimidating expensive.

4
00:00:08.960 --> 00:00:11.279
<v Speaker 2>Yeah, like it's only for big companies with huge IT

5
00:00:11.359 --> 00:00:13.480
<v Speaker 2>teams and budgets exactly.

6
00:00:14.119 --> 00:00:16.359
<v Speaker 1>But what if I told you that running your own server,

7
00:00:16.800 --> 00:00:20.199
<v Speaker 1>getting that incredible control and capability for your digital stuff

8
00:00:20.719 --> 00:00:24.000
<v Speaker 1>is actually well pretty accessible now if you have the

9
00:00:24.039 --> 00:00:26.839
<v Speaker 1>right knowledge. That is so today we're doing a deep

10
00:00:26.879 --> 00:00:32.039
<v Speaker 1>dive into virtual private servers VPS for short. And this

11
00:00:32.079 --> 00:00:33.119
<v Speaker 1>isn't just about tech.

12
00:00:32.960 --> 00:00:34.039
<v Speaker 3>Talk, No, not at all.

13
00:00:34.119 --> 00:00:37.560
<v Speaker 2>It's really about unlocking a level of digital independence for

14
00:00:37.640 --> 00:00:40.960
<v Speaker 2>your own projects, maybe your startup or even a small business.

15
00:00:41.280 --> 00:00:44.640
<v Speaker 2>Our mission here really is to demystify the vps. We're

16
00:00:44.640 --> 00:00:48.159
<v Speaker 2>going to unpack the idea, walk you through picking a provider,

17
00:00:48.240 --> 00:00:50.159
<v Speaker 2>the setup essential, and then what you can actually do

18
00:00:50.200 --> 00:00:52.719
<v Speaker 2>with it right, explore the possibilities. We want to pull

19
00:00:52.719 --> 00:00:55.439
<v Speaker 2>out the key bits of knowledge so you feel genuinely informed,

20
00:00:55.479 --> 00:00:58.280
<v Speaker 2>but you know, not totally overwhelmed by jargon.

21
00:00:58.679 --> 00:01:01.840
<v Speaker 1>And guiding us is joh On west Fall's fantastic book,

22
00:01:02.079 --> 00:01:05.400
<v Speaker 1>Set Up and Manage your Virtual Private Server, making system

23
00:01:05.439 --> 00:01:07.480
<v Speaker 1>administration accessible to professionals.

24
00:01:07.760 --> 00:01:08.719
<v Speaker 4>It's our core source.

25
00:01:08.959 --> 00:01:12.519
<v Speaker 2>It's a great one, really practical, translates the techiek stuff

26
00:01:12.519 --> 00:01:15.519
<v Speaker 2>into normal person speak, exactly what we need.

27
00:01:15.640 --> 00:01:17.400
<v Speaker 1>Okay, so let's set the scene. There was a time,

28
00:01:17.560 --> 00:01:20.640
<v Speaker 1>not that long ago really, when having your own server

29
00:01:20.840 --> 00:01:25.159
<v Speaker 1>was just incredibly expensive, dedicated machines, special.

30
00:01:24.799 --> 00:01:26.640
<v Speaker 3>Facilities, thousands a month easily.

31
00:01:26.799 --> 00:01:30.680
<v Speaker 1>So what changed? What made this level of control available

32
00:01:30.719 --> 00:01:32.079
<v Speaker 1>to welp us?

33
00:01:32.400 --> 00:01:36.519
<v Speaker 2>The big game changer was virtualization. It's this clever way

34
00:01:36.560 --> 00:01:41.079
<v Speaker 2>to host multiple totally separate servers on one single, powerful

35
00:01:41.120 --> 00:01:42.079
<v Speaker 2>physical machine.

36
00:01:42.400 --> 00:01:42.719
<v Speaker 4>Wow.

37
00:01:42.799 --> 00:01:45.400
<v Speaker 2>So what used to need massive cash and it staff

38
00:01:45.519 --> 00:01:48.640
<v Speaker 2>now just needs well your knowledge. It's a powerful idea

39
00:01:48.680 --> 00:01:51.359
<v Speaker 2>and it's what makes server ownership so much cheaper today.

40
00:01:51.439 --> 00:01:55.120
<v Speaker 1>Okay, So if virtualization is the magic, what exactly is

41
00:01:55.159 --> 00:01:57.719
<v Speaker 1>the server the thing we're actually using and how does

42
00:01:57.760 --> 00:01:59.680
<v Speaker 1>this virtual part work in practice?

43
00:01:59.760 --> 00:01:59.879
<v Speaker 2>Well?

44
00:02:00.120 --> 00:02:00.920
<v Speaker 3>Think about the Internet.

45
00:02:00.959 --> 00:02:04.359
<v Speaker 2>Fundamentally, it's millions of computers talking.

46
00:02:04.519 --> 00:02:06.760
<v Speaker 3>Right. You've got clients, your phone.

47
00:02:06.560 --> 00:02:10.759
<v Speaker 2>Your laptop, asking for stuff, right, and then servers, which

48
00:02:10.759 --> 00:02:13.800
<v Speaker 2>are the computers designed to give that stuff, provide that

49
00:02:13.879 --> 00:02:17.080
<v Speaker 2>information or service. Every time you open a web page,

50
00:02:17.120 --> 00:02:19.879
<v Speaker 2>your device is a client talking to a server. Makes

51
00:02:19.879 --> 00:02:24.280
<v Speaker 2>sense now, the virtual bit. Imagine a big shopping mall,

52
00:02:24.639 --> 00:02:28.560
<v Speaker 2>that whole building that's like one giant, powerful physical server. Okay,

53
00:02:28.719 --> 00:02:31.319
<v Speaker 2>Inside that mall, you have loads of different stores, right,

54
00:02:31.520 --> 00:02:34.439
<v Speaker 2>Each one is separate, unique, does its own thing, but

55
00:02:34.479 --> 00:02:37.960
<v Speaker 2>they all share the mall structure, the power, the air conditioning.

56
00:02:38.599 --> 00:02:40.319
<v Speaker 3>A physical server is like the mall.

57
00:02:40.680 --> 00:02:44.039
<v Speaker 2>It hosts many virtual servers, the stores, each getting a

58
00:02:44.039 --> 00:02:47.080
<v Speaker 2>slice of the resources, totally isolated from the others, but

59
00:02:47.240 --> 00:02:48.840
<v Speaker 2>sharing the underlying hardware.

60
00:02:48.919 --> 00:02:51.520
<v Speaker 1>That mall analogy really helped. Okay, So let's connect that

61
00:02:51.560 --> 00:02:54.240
<v Speaker 1>to something we do every day, like opening a web page,

62
00:02:54.280 --> 00:02:57.639
<v Speaker 1>saybipyer dot com. How does that virtual magic happen?

63
00:02:57.680 --> 00:02:57.840
<v Speaker 4>Then?

64
00:02:58.039 --> 00:03:00.879
<v Speaker 2>Right, So, behind the scenes, your computer first needs the

65
00:03:00.919 --> 00:03:05.680
<v Speaker 2>server's address. It asks a Domain Name service a DNS

66
00:03:05.719 --> 00:03:08.719
<v Speaker 2>server for the numerical IP address for beetpirate dot com.

67
00:03:08.960 --> 00:03:10.439
<v Speaker 2>Think of it like a global phone book.

68
00:03:10.520 --> 00:03:10.800
<v Speaker 4>Okay.

69
00:03:11.039 --> 00:03:13.159
<v Speaker 2>Once it has that number, it knocks on the door

70
00:03:13.159 --> 00:03:16.479
<v Speaker 2>of the web server using a specific port number, usually

71
00:03:16.759 --> 00:03:19.759
<v Speaker 2>Port eighty for regular web pages or four hundred and

72
00:03:19.759 --> 00:03:21.000
<v Speaker 2>forty three for secure ones.

73
00:03:21.080 --> 00:03:22.680
<v Speaker 3>The HPTPS ones.

74
00:03:22.560 --> 00:03:24.240
<v Speaker 5>The little padlock exactly.

75
00:03:24.840 --> 00:03:28.400
<v Speaker 2>Now, Sometimes things go wrong here, maybe the domain doesn't exist,

76
00:03:28.599 --> 00:03:31.919
<v Speaker 2>or the DNS records are messed up or rarely your

77
00:03:31.919 --> 00:03:35.520
<v Speaker 2>ISP might even sort of poison the result and send

78
00:03:35.599 --> 00:03:36.280
<v Speaker 2>you somewhere else.

79
00:03:36.319 --> 00:03:36.719
<v Speaker 4>Oh wow.

80
00:03:36.719 --> 00:03:38.840
<v Speaker 2>But assuming it works, the web server answers on that

81
00:03:38.919 --> 00:03:40.919
<v Speaker 2>port and sends the web page data back to you.

82
00:03:41.000 --> 00:03:42.039
<v Speaker 3>That's the basic flow.

83
00:03:42.639 --> 00:03:45.719
<v Speaker 1>So with all this power and control, the big question

84
00:03:45.759 --> 00:03:47.479
<v Speaker 1>for a lot of folks is going to be cost.

85
00:03:48.400 --> 00:03:50.719
<v Speaker 1>Is it really that much cheaper now to run your

86
00:03:50.719 --> 00:03:51.439
<v Speaker 1>own vps?

87
00:03:51.520 --> 00:03:54.199
<v Speaker 2>It absolutely is, and the difference is pretty striking. Shared

88
00:03:54.240 --> 00:03:56.759
<v Speaker 2>hosting where you're crammed in with tons of other sites

89
00:03:56.800 --> 00:03:59.479
<v Speaker 2>averages what maybe four dollars and sixty three someone, yeah,

90
00:03:59.520 --> 00:04:03.000
<v Speaker 2>something like that, a basic VPS more like seventeen dollars

91
00:04:03.000 --> 00:04:04.199
<v Speaker 2>and forty nine cents a month.

92
00:04:04.719 --> 00:04:06.360
<v Speaker 3>But a dedicated.

93
00:04:05.759 --> 00:04:08.319
<v Speaker 2>Physical server you're looking at over one hundred bucks maybe

94
00:04:08.319 --> 00:04:10.319
<v Speaker 2>one hundred and seven dollars and twenty five a month.

95
00:04:10.479 --> 00:04:12.319
<v Speaker 2>Huge difference, and it gets even cheaper.

96
00:04:12.719 --> 00:04:13.439
<v Speaker 3>Aws.

97
00:04:13.520 --> 00:04:16.800
<v Speaker 2>Amazon's cloud service has EC two instances free for the

98
00:04:16.800 --> 00:04:20.800
<v Speaker 2>first year, then it's billed hourly, super flexible hourly.

99
00:04:20.959 --> 00:04:21.240
<v Speaker 4>Wow.

100
00:04:21.399 --> 00:04:23.360
<v Speaker 2>And if you really hunt around on sites like low

101
00:04:23.360 --> 00:04:26.920
<v Speaker 2>inbox dot com, you can find bargain basement VPS deals,

102
00:04:26.920 --> 00:04:29.040
<v Speaker 2>sometimes as low as two dollars and fifty cents a month,

103
00:04:29.160 --> 00:04:31.079
<v Speaker 2>or even ten twenty dollars a year during sales.

104
00:04:31.120 --> 00:04:33.160
<v Speaker 1>Okay, two dollars and fifty cents a month. That sounds

105
00:04:33.160 --> 00:04:35.879
<v Speaker 1>almost suspicious. What's the catch?

106
00:04:35.920 --> 00:04:37.439
<v Speaker 2>There has to be a trade off, right, there is,

107
00:04:37.480 --> 00:04:41.399
<v Speaker 2>and it's simple responsibility. You are the tech support. Your

108
00:04:41.439 --> 00:04:43.920
<v Speaker 2>provider might reset your server if things go really bad,

109
00:04:44.000 --> 00:04:46.600
<v Speaker 2>reimage it, basically wipe it clean. But all your data,

110
00:04:46.639 --> 00:04:50.480
<v Speaker 2>your set up, your customization's gone. So you are responsible

111
00:04:50.480 --> 00:04:52.720
<v Speaker 2>for your data, backup, security, keeping things running.

112
00:04:52.759 --> 00:04:54.000
<v Speaker 3>It takes time commitment.

113
00:04:54.040 --> 00:04:56.759
<v Speaker 2>If you're the type who likes to outsource everything technical, yeah,

114
00:04:56.839 --> 00:04:57.199
<v Speaker 2>maybe a.

115
00:04:57.240 --> 00:04:58.079
<v Speaker 3>VPS isn't for you.

116
00:04:58.240 --> 00:04:59.839
<v Speaker 5>Right, it's hands on totally.

117
00:05:00.480 --> 00:05:03.680
<v Speaker 2>The author John Westfall he became a research psychologist but

118
00:05:03.759 --> 00:05:06.759
<v Speaker 2>still manages his own it. That kind of tells you

119
00:05:06.839 --> 00:05:08.720
<v Speaker 2>the level of self sufficiency involved.

120
00:05:08.800 --> 00:05:11.639
<v Speaker 1>Okay, So if we're ready for that responsibility, the next

121
00:05:11.680 --> 00:05:14.879
<v Speaker 1>big step is picking a provider. And you mentioned it's

122
00:05:14.879 --> 00:05:19.079
<v Speaker 1>not like buying a car. The waters are muddier, Yeah,

123
00:05:19.120 --> 00:05:20.040
<v Speaker 1>definitely muddier.

124
00:05:20.079 --> 00:05:22.879
<v Speaker 2>It helps to think about providers in like three main

125
00:05:22.959 --> 00:05:26.199
<v Speaker 2>groups based on price and service. First, you've got the

126
00:05:26.399 --> 00:05:28.279
<v Speaker 2>low end price small shop guys.

127
00:05:28.399 --> 00:05:30.120
<v Speaker 1>The bargain basement ones pretty much.

128
00:05:30.439 --> 00:05:33.560
<v Speaker 2>Often one person shows advertising on places like low inbox

129
00:05:33.639 --> 00:05:36.120
<v Speaker 2>dot com. Their whole thing is lowest costs. They assume

130
00:05:36.160 --> 00:05:38.360
<v Speaker 2>you know your stuff technically and won't need much higher Right,

131
00:05:38.600 --> 00:05:41.279
<v Speaker 2>you'll see specs like one CPU core often just a

132
00:05:41.319 --> 00:05:44.199
<v Speaker 2>slice of a standard CPU, maybe twenty two gigabee and

133
00:05:44.279 --> 00:05:48.879
<v Speaker 2>vme SSD storage small but fast, one gbp port plenty fast.

134
00:05:48.959 --> 00:05:52.360
<v Speaker 2>Usually they might mention the OPENBZ hypervisor that's the software

135
00:05:52.360 --> 00:05:55.519
<v Speaker 2>managing the virtual servers, and a location like.

136
00:05:55.439 --> 00:05:58.639
<v Speaker 5>Los Angeles, so super cheap. But you're on your own largely.

137
00:05:58.680 --> 00:06:01.199
<v Speaker 2>Yeah, and watch out for human reasons for downtime, like

138
00:06:01.240 --> 00:06:02.759
<v Speaker 2>the owners on vacation or something.

139
00:06:02.839 --> 00:06:04.079
<v Speaker 3>It demands a lot from you.

140
00:06:04.800 --> 00:06:07.600
<v Speaker 2>Then you have the high end price large shop providers

141
00:06:07.759 --> 00:06:11.120
<v Speaker 2>names you probably know like dream host, Blue host host.

142
00:06:10.879 --> 00:06:12.879
<v Speaker 5>Gator, Okay, the bigger names, right.

143
00:06:13.079 --> 00:06:17.439
<v Speaker 2>Hundreds of staff, custom portals, maybe apps, often two hundred

144
00:06:17.480 --> 00:06:20.759
<v Speaker 2>for seven support. It's a more polished experience, but you're

145
00:06:20.759 --> 00:06:25.160
<v Speaker 2>still responsible for your content, backups, security scans usually extra cost,

146
00:06:25.920 --> 00:06:29.480
<v Speaker 2>and finally, the priced by the minute. Cloud infrastructure players

147
00:06:29.560 --> 00:06:34.600
<v Speaker 2>the giants Amazon Web Services, AWS, Google Cloud, Microsoft, Azure, oh,

148
00:06:34.639 --> 00:06:37.600
<v Speaker 2>the cloud providers exactly, pay only for what you use,

149
00:06:37.680 --> 00:06:40.439
<v Speaker 2>often by the minute. Great for fluctuating needs like heavy

150
00:06:40.519 --> 00:06:44.639
<v Speaker 2>data crunching sometimes or big website spikes during say tax season.

151
00:06:44.839 --> 00:06:46.480
<v Speaker 2>AWS even has a price.

152
00:06:46.240 --> 00:06:48.560
<v Speaker 1>Calculator, flexible but potentially complex.

153
00:06:48.639 --> 00:06:52.360
<v Speaker 2>Can be They introduce cool concepts like autoscaling, adding resources

154
00:06:52.360 --> 00:06:57.199
<v Speaker 2>automatically when needed, elasticity growing and shrinking easily, high availability

155
00:06:57.279 --> 00:07:00.560
<v Speaker 2>or HA for uptime, load balancing, traffic.

156
00:07:00.680 --> 00:07:01.439
<v Speaker 3>Powerful stuff.

157
00:07:01.639 --> 00:07:04.319
<v Speaker 1>Okay, that's a diverse landscape. So how do you protect

158
00:07:04.319 --> 00:07:06.319
<v Speaker 1>yourself legally? How do you know what you're actually signing

159
00:07:06.360 --> 00:07:06.600
<v Speaker 1>up for?

160
00:07:07.040 --> 00:07:07.839
<v Speaker 3>Crucial question.

161
00:07:08.480 --> 00:07:12.079
<v Speaker 2>You need to look at two key documents, often buried. First,

162
00:07:12.160 --> 00:07:14.959
<v Speaker 2>the terms of service tos. I think of it like

163
00:07:15.000 --> 00:07:19.199
<v Speaker 2>your lease agreement. The fine print exactly, usually long, complex

164
00:07:19.279 --> 00:07:21.800
<v Speaker 2>and written to protect them. It'll say they're not liable

165
00:07:21.800 --> 00:07:24.759
<v Speaker 2>for your data loss or lost income, that backups usually

166
00:07:24.759 --> 00:07:28.240
<v Speaker 2>cost extra. It covers maintenance, windows, bandwidth limits go over,

167
00:07:28.360 --> 00:07:31.560
<v Speaker 2>you might get suspended. Wow, It'll likely say hacks aren't

168
00:07:31.560 --> 00:07:35.560
<v Speaker 2>their fault. Covers billing, copyright takedowns, often forty eight hours,

169
00:07:35.879 --> 00:07:38.480
<v Speaker 2>rules about porn fishing, stuff like that. You have to

170
00:07:38.480 --> 00:07:41.079
<v Speaker 2>review it carefully, search for the bits that matter to you.

171
00:07:42.120 --> 00:07:44.480
<v Speaker 2>The second if they offer it is the Service Level

172
00:07:44.519 --> 00:07:48.920
<v Speaker 2>Agreement SLA. This is more like a legal contract guaranteeing uptime,

173
00:07:49.160 --> 00:07:52.399
<v Speaker 2>often aiming for five nine's ninety nine point nine nine

174
00:07:52.480 --> 00:07:54.920
<v Speaker 2>nine percent uptime, which is just over five minutes of

175
00:07:54.920 --> 00:07:57.720
<v Speaker 2>downtime per year, tiny amount. If they breach the SLA,

176
00:07:57.800 --> 00:08:01.160
<v Speaker 2>you might get service credits, but not all offer slas,

177
00:08:01.399 --> 00:08:04.360
<v Speaker 2>and good ones often cost more or need longer contracts.

178
00:08:04.680 --> 00:08:08.000
<v Speaker 1>Okay, Besides reading the legal docs, what are some practical

179
00:08:08.040 --> 00:08:10.480
<v Speaker 1>red flags to watch out for when choosing Well?

180
00:08:10.600 --> 00:08:13.519
<v Speaker 2>Definitely be wary of rates that seem too good to

181
00:08:13.560 --> 00:08:17.000
<v Speaker 2>be true. Could be an inexperienced provider or someone trying

182
00:08:17.040 --> 00:08:19.800
<v Speaker 2>to you know, hide a bad rep. Right the old

183
00:08:19.839 --> 00:08:23.079
<v Speaker 2>saying you get what you pay for really applies. Higher

184
00:08:23.120 --> 00:08:26.800
<v Speaker 2>price often means better support, better docks, faster help when

185
00:08:26.800 --> 00:08:27.079
<v Speaker 2>you need.

186
00:08:27.079 --> 00:08:27.720
<v Speaker 4>It makes sense.

187
00:08:28.000 --> 00:08:31.319
<v Speaker 2>Big red flag if a company forbids you from encrypting

188
00:08:31.360 --> 00:08:34.519
<v Speaker 2>your data or setting your own passwords, huge security issue.

189
00:08:34.559 --> 00:08:37.679
<v Speaker 2>WHOA yeah, And be cautious if they only take untraceable

190
00:08:37.679 --> 00:08:41.080
<v Speaker 2>payments like crypto or wire transfers, unless that's their whole

191
00:08:41.159 --> 00:08:45.200
<v Speaker 2>known business model, which raises other questions. Always always check

192
00:08:45.200 --> 00:08:47.960
<v Speaker 2>online reviews, Maybe ask questions on social media before.

193
00:08:47.720 --> 00:08:48.639
<v Speaker 4>You buy good advice.

194
00:08:48.679 --> 00:08:52.039
<v Speaker 1>Okay, say we've picked one, what do we need ready financially,

195
00:08:52.200 --> 00:08:53.000
<v Speaker 1>time wise.

196
00:08:53.039 --> 00:08:56.720
<v Speaker 2>Financially besides the VPS cost, you'll need a domain name

197
00:08:56.840 --> 00:08:59.559
<v Speaker 2>that's cheap. Maybe ten twenty dollars a year for a

198
00:08:59.639 --> 00:09:03.080
<v Speaker 2>decent high end provider. Maybe budget around three hundred dollars

199
00:09:03.080 --> 00:09:06.000
<v Speaker 2>for the first year all in, okay, And it's a commitment,

200
00:09:06.159 --> 00:09:09.440
<v Speaker 2>especially at first. Sign up is quick, maybe twenty minutes

201
00:09:09.559 --> 00:09:11.840
<v Speaker 2>getting the server actually set up by the provider, could

202
00:09:11.840 --> 00:09:13.919
<v Speaker 2>be ten minutes, could be twelve hours, depends.

203
00:09:14.039 --> 00:09:15.600
<v Speaker 4>Then the real work starts.

204
00:09:15.320 --> 00:09:20.240
<v Speaker 2>Yeah, logging in, installing the basics honestly, block out maybe

205
00:09:20.320 --> 00:09:23.960
<v Speaker 2>ten twenty hours for that initial phase, including troubleshooting. Then

206
00:09:24.120 --> 00:09:27.559
<v Speaker 2>plan for say thirty sixty minutes of weekly.

207
00:09:27.279 --> 00:09:28.679
<v Speaker 4>Maintenance, weekly check ins.

208
00:09:28.799 --> 00:09:31.879
<v Speaker 2>Definitely, And if you're moving from old hosting, keep the

209
00:09:31.879 --> 00:09:33.799
<v Speaker 2>old one active for a month overlap.

210
00:09:33.840 --> 00:09:35.200
<v Speaker 3>Trust me, it saves headaches.

211
00:09:35.720 --> 00:09:36.159
<v Speaker 4>Smart.

212
00:09:36.360 --> 00:09:40.200
<v Speaker 1>So okay, server's ready, accounts active. How do we actually

213
00:09:40.200 --> 00:09:41.000
<v Speaker 1>connect to this thing?

214
00:09:41.279 --> 00:09:44.360
<v Speaker 2>First step, point your domain name like theepirate dot com

215
00:09:44.399 --> 00:09:46.720
<v Speaker 2>to your server's IP address. You do this with a

216
00:09:46.799 --> 00:09:50.159
<v Speaker 2>DNSA record at your domain registrar. Okay, just know dinas

217
00:09:50.240 --> 00:09:52.759
<v Speaker 2>changes take time to spread, maybe two four hours. It's

218
00:09:52.759 --> 00:09:55.120
<v Speaker 2>called propagation based on TTL setting.

219
00:09:55.159 --> 00:09:56.600
<v Speaker 5>I get wait a minute, then what Then?

220
00:09:56.639 --> 00:10:00.000
<v Speaker 2>You connect using secure shell or SSH. If you're on Window,

221
00:10:00.279 --> 00:10:02.840
<v Speaker 2>you'll likely use a tool called putty glee. Mac and

222
00:10:02.879 --> 00:10:05.960
<v Speaker 2>Linux have SSH built in now. Instead of just passwords,

223
00:10:06.240 --> 00:10:09.919
<v Speaker 2>many providers use private key files for better security. You

224
00:10:10.000 --> 00:10:13.240
<v Speaker 2>download this key file once, keep it super safe. It's

225
00:10:13.360 --> 00:10:15.720
<v Speaker 2>part of cryptographic authentication.

226
00:10:15.320 --> 00:10:17.360
<v Speaker 1>More secure than a password, much more.

227
00:10:17.840 --> 00:10:20.399
<v Speaker 2>Your computer also keeps a record of servers you connect

228
00:10:20.440 --> 00:10:23.399
<v Speaker 2>to in a known hosts file. It helps stop you

229
00:10:23.440 --> 00:10:27.279
<v Speaker 2>connecting to fake servers. Oh and we'll mostly use Debian

230
00:10:27.320 --> 00:10:28.879
<v Speaker 2>and Sento Linux examples here.

231
00:10:28.919 --> 00:10:31.960
<v Speaker 1>All right, Now, the command line for a lot of people,

232
00:10:32.039 --> 00:10:35.240
<v Speaker 1>that sounds old school, maybe intimidating.

233
00:10:35.440 --> 00:10:38.039
<v Speaker 4>Yeah, why is it still so key for a VPS?

234
00:10:38.360 --> 00:10:41.159
<v Speaker 2>It really comes down to efficiency. Linux was built for

235
00:10:41.200 --> 00:10:44.559
<v Speaker 2>a world of dumb terminals, just keyboards and screens connected

236
00:10:44.600 --> 00:10:45.480
<v Speaker 2>to a central computer.

237
00:10:46.080 --> 00:10:47.240
<v Speaker 3>You typed commands.

238
00:10:47.399 --> 00:10:49.799
<v Speaker 1>Sounds like how we use a VPS now exactly.

239
00:10:49.840 --> 00:10:52.759
<v Speaker 2>The command line is just faster, more direct, more powerful

240
00:10:52.759 --> 00:10:55.799
<v Speaker 2>for managing a server. You can automate things, do complex

241
00:10:55.840 --> 00:10:58.279
<v Speaker 2>stuff quickly with just text commands. It puts the power

242
00:10:58.399 --> 00:10:59.039
<v Speaker 2>right in your hands.

243
00:10:59.039 --> 00:11:02.240
<v Speaker 1>Okay, efficiency makes So we're logged in via SSH. What

244
00:11:02.320 --> 00:11:04.960
<v Speaker 1>are the first practical steps the core commands we need?

245
00:11:05.240 --> 00:11:09.240
<v Speaker 2>Well, besides SSH for login, you'll want SFTP Secure File

246
00:11:09.279 --> 00:11:13.200
<v Speaker 2>Transfer Protocol, probably using a tool like cyberduc. That's for

247
00:11:13.279 --> 00:11:15.440
<v Speaker 2>moving files between your computer and the server.

248
00:11:15.600 --> 00:11:17.320
<v Speaker 4>Got it files back and forth.

249
00:11:17.399 --> 00:11:20.639
<v Speaker 2>Crucially, first thing, create your own user account, one that

250
00:11:20.679 --> 00:11:25.039
<v Speaker 2>isn't root. The root user idzero has god mode full permissions.

251
00:11:25.480 --> 00:11:27.960
<v Speaker 2>Way safer to use a regular account for daily.

252
00:11:27.720 --> 00:11:30.600
<v Speaker 5>Stuff and use root powers only when needed exactly.

253
00:11:30.799 --> 00:11:33.679
<v Speaker 2>You use the pseudo command to temporarily elevate your privileges

254
00:11:33.720 --> 00:11:35.559
<v Speaker 2>for specific tasks. Much safer.

255
00:11:35.679 --> 00:11:37.240
<v Speaker 4>Okay, what about finding things?

256
00:11:37.639 --> 00:11:38.519
<v Speaker 3>You got to understand?

257
00:11:38.519 --> 00:11:41.279
<v Speaker 2>The Linux file system structure starts with the route directory

258
00:11:41.440 --> 00:11:45.519
<v Speaker 2>key places BIN for es central programs, boot for startup files,

259
00:11:45.639 --> 00:11:47.039
<v Speaker 2>Home where your user files live.

260
00:11:47.159 --> 00:11:48.200
<v Speaker 3>Usually the only place you.

261
00:11:48.159 --> 00:11:49.879
<v Speaker 5>Can write by default home is MySpace.

262
00:11:50.120 --> 00:11:53.840
<v Speaker 2>Right, then etc for config files, varlog for logs, VROW

263
00:11:53.919 --> 00:11:56.919
<v Speaker 2>for website files and moving around. You'll use CD to

264
00:11:57.000 --> 00:12:01.039
<v Speaker 2>change directory, pbdwd to see where you are. Ella's list files,

265
00:12:01.159 --> 00:12:04.879
<v Speaker 2>use LS for details and hidden files, LSLH for easy

266
00:12:04.919 --> 00:12:05.399
<v Speaker 2>to read.

267
00:12:05.240 --> 00:12:06.919
<v Speaker 5>Sizes elslow got it.

268
00:12:07.279 --> 00:12:11.440
<v Speaker 2>Kat lets you view file contents. You can use wild cards,

269
00:12:11.600 --> 00:12:15.720
<v Speaker 2>pipes to combine commands, very powerful for files. Touch creates

270
00:12:15.759 --> 00:12:18.960
<v Speaker 2>empty ones, MV moves or renames CEP poppies, and deleting

271
00:12:19.200 --> 00:12:22.639
<v Speaker 2>r M deletes. Be super careful with rmdashar that recursively

272
00:12:22.679 --> 00:12:24.279
<v Speaker 2>deletes everything in a directory.

273
00:12:24.720 --> 00:12:28.240
<v Speaker 4>No undo button, yikes? Okay, caution advised.

274
00:12:28.440 --> 00:12:31.320
<v Speaker 3>Definitely Find helps you search for files. And if you're

275
00:12:31.360 --> 00:12:31.759
<v Speaker 3>stuck on.

276
00:12:31.759 --> 00:12:34.679
<v Speaker 2>A command, type man than the command name, give you

277
00:12:34.720 --> 00:12:36.840
<v Speaker 2>the manual page. Look for the example section.

278
00:12:36.960 --> 00:12:38.879
<v Speaker 5>Super helpful man like manual.

279
00:12:39.480 --> 00:12:40.039
<v Speaker 4>Good tip.

280
00:12:40.240 --> 00:12:43.720
<v Speaker 2>Oh and Linux uses links, especially symbolic links l n nds.

281
00:12:43.879 --> 00:12:45.679
<v Speaker 2>They're like shortcuts to files elsewhere.

282
00:12:45.799 --> 00:12:47.000
<v Speaker 5>Helps keep things organized.

283
00:12:47.039 --> 00:12:49.440
<v Speaker 1>Okay, that's a good set of basics. Now a big

284
00:12:49.480 --> 00:12:51.559
<v Speaker 1>part of Linux's permissions, right, who can do?

285
00:12:51.639 --> 00:12:53.519
<v Speaker 4>What? Can you break that down simply?

286
00:12:53.799 --> 00:12:54.080
<v Speaker 3>Yeah?

287
00:12:54.120 --> 00:12:57.440
<v Speaker 2>Absolutely? Use the home ownership idea. Your VPS is your

288
00:12:57.440 --> 00:13:01.600
<v Speaker 2>digital house. Every file, every folder has permission read write.

289
00:13:01.519 --> 00:13:03.320
<v Speaker 4>Execute, read write execute okay.

290
00:13:03.480 --> 00:13:07.039
<v Speaker 2>Is applied to three groups. The owner, you or maybe

291
00:13:07.080 --> 00:13:11.159
<v Speaker 2>a system process. The group like collaborators, family and others.

292
00:13:11.200 --> 00:13:13.039
<v Speaker 5>Everyone else strangers lower group others.

293
00:13:13.320 --> 00:13:15.799
<v Speaker 2>Got it, so you might have full ReadWrite execute on

294
00:13:15.840 --> 00:13:18.639
<v Speaker 2>your stuff. Your group might only read write a shared file,

295
00:13:19.039 --> 00:13:20.960
<v Speaker 2>others might only read something public.

296
00:13:21.080 --> 00:13:21.559
<v Speaker 4>Makes sense.

297
00:13:21.720 --> 00:13:24.279
<v Speaker 2>You control this with CHUMD can use numbers like seven

298
00:13:24.320 --> 00:13:27.799
<v Speaker 2>seven means full access for everyone usually bad or symbols

299
00:13:27.879 --> 00:13:30.879
<v Speaker 2>like G plus W give right access to the group.

300
00:13:31.200 --> 00:13:34.639
<v Speaker 2>Challenge changes the owner, ghg R changes.

301
00:13:34.320 --> 00:13:36.000
<v Speaker 4>The group, and Root ignores all this.

302
00:13:36.279 --> 00:13:36.759
<v Speaker 3>Root is the.

303
00:13:36.679 --> 00:13:39.519
<v Speaker 2>Superadmin bypasses all permissions. That's why you use it carefully.

304
00:13:40.200 --> 00:13:43.919
<v Speaker 2>So to use Root powers safely, you could log out

305
00:13:43.919 --> 00:13:45.320
<v Speaker 2>and log back in as Root, but.

306
00:13:45.279 --> 00:13:46.720
<v Speaker 3>That's risky for everyday stuff.

307
00:13:46.720 --> 00:13:49.000
<v Speaker 2>You could use SUE to switch users, but the best

308
00:13:49.000 --> 00:13:53.120
<v Speaker 2>way is pseudo super user. Do it lets your regular

309
00:13:53.240 --> 00:13:57.120
<v Speaker 2>user run specific commands's route temporarily. It's safer and it

310
00:13:57.240 --> 00:13:59.720
<v Speaker 2>logs what you did. That's the standard preferred method.

311
00:14:00.039 --> 00:14:02.759
<v Speaker 1>Zudo got it limits the risk. Now let's peek under

312
00:14:02.759 --> 00:14:05.240
<v Speaker 1>the hood. How does the vps actually start up?

313
00:14:05.279 --> 00:14:09.399
<v Speaker 2>Okay, So basically biostarts loads a bootloader. Bootloader loads the

314
00:14:09.440 --> 00:14:13.039
<v Speaker 2>kernel the core Linux os Linus Torvold's baby from nineteen kernel,

315
00:14:13.240 --> 00:14:17.320
<v Speaker 2>then on modern systems like Wan nine or Cento seven onwards,

316
00:14:17.720 --> 00:14:21.200
<v Speaker 2>systems takes over. It's the master process that starts and

317
00:14:21.279 --> 00:14:24.759
<v Speaker 2>manages everything else network, web server, all background.

318
00:14:24.399 --> 00:14:26.679
<v Speaker 5>Services, system the boss pretty much.

319
00:14:26.799 --> 00:14:30.559
<v Speaker 2>It manages services, devices, mounts, swap space and targets like

320
00:14:30.799 --> 00:14:33.679
<v Speaker 2>multi user dot target for command line only good for

321
00:14:33.759 --> 00:14:37.120
<v Speaker 2>servers versus graphical dot target for a full desktop.

322
00:14:37.240 --> 00:14:39.559
<v Speaker 5>And we manage systemed with system patal.

323
00:14:39.559 --> 00:14:42.799
<v Speaker 2>It's your command center for services. System title, list, units, type,

324
00:14:42.840 --> 00:14:45.840
<v Speaker 2>service shows what's running. You can stop services or disable

325
00:14:45.879 --> 00:14:47.039
<v Speaker 2>them so they don't start on boot.

326
00:14:47.159 --> 00:14:49.279
<v Speaker 5>Ah, so you can trim the fat exactly.

327
00:14:49.399 --> 00:14:52.320
<v Speaker 2>Maybe you don't need the printing service cups running. Stop

328
00:14:52.320 --> 00:14:54.600
<v Speaker 2>it if it restarts, maybe something else depends on it.

329
00:14:55.159 --> 00:14:58.480
<v Speaker 2>Use system taitle reverse list dependencies cupstock service to find

330
00:14:58.480 --> 00:15:01.120
<v Speaker 2>out what, then disable that. System tato lets you make

331
00:15:01.159 --> 00:15:03.559
<v Speaker 2>your Linux install lean and mean for just what you need.

332
00:15:03.720 --> 00:15:07.799
<v Speaker 1>Optimizing is good and keeping things secure means updates right.

333
00:15:08.080 --> 00:15:09.679
<v Speaker 1>How do we handle software updates?

334
00:15:09.919 --> 00:15:14.639
<v Speaker 2>Linux has great package managers. Debian uses APT Advanced Package Tool,

335
00:15:14.879 --> 00:15:18.240
<v Speaker 2>Santos uses Yum or the newer DNF. You run commands

336
00:15:18.279 --> 00:15:21.320
<v Speaker 2>like appt update then APPED upgrade on Debian or Yum

337
00:15:21.480 --> 00:15:22.399
<v Speaker 2>update on Cento US.

338
00:15:22.519 --> 00:15:25.279
<v Speaker 3>This checks for and installs updates for all your software.

339
00:15:25.399 --> 00:15:28.360
<v Speaker 2>How often we strongly recommend doing this weekly keeps you

340
00:15:28.399 --> 00:15:30.519
<v Speaker 2>patched against security holes, gets bug fixes.

341
00:15:30.600 --> 00:15:31.200
<v Speaker 3>It's crucial.

342
00:15:31.440 --> 00:15:33.799
<v Speaker 2>You can install from source code, but package managers make

343
00:15:33.840 --> 00:15:35.440
<v Speaker 2>it so much easier for most things.

344
00:15:35.519 --> 00:15:37.919
<v Speaker 4>Okay, weekly updates, got it. Now.

345
00:15:38.799 --> 00:15:41.720
<v Speaker 1>The command line is powerful, but let's be honest, it

346
00:15:41.759 --> 00:15:45.919
<v Speaker 1>can't be intimidating. Is there a friendlier option, A graphical way.

347
00:15:46.120 --> 00:15:46.519
<v Speaker 3>There is.

348
00:15:46.559 --> 00:15:51.679
<v Speaker 2>It's called webman, a really solid open source GUI graphical

349
00:15:51.879 --> 00:15:55.159
<v Speaker 2>user interface for Linux admin been around forever, like twenty

350
00:15:55.159 --> 00:15:55.759
<v Speaker 2>plus years.

351
00:15:55.799 --> 00:15:58.399
<v Speaker 1>Webmin okay, but as using a GUI on a server

352
00:15:58.720 --> 00:15:59.240
<v Speaker 1>frowned upon.

353
00:15:59.519 --> 00:16:03.759
<v Speaker 2>Huh, there's definitely a debate. Pros webmin simplifies things, less

354
00:16:03.799 --> 00:16:07.600
<v Speaker 2>chance of typos and commands. Easy user management includes usermen

355
00:16:07.720 --> 00:16:08.759
<v Speaker 2>letting users manage their.

356
00:16:08.679 --> 00:16:10.080
<v Speaker 5>Own stuff on cons.

357
00:16:10.080 --> 00:16:12.159
<v Speaker 2>Cons you might not learn the command line as well

358
00:16:12.159 --> 00:16:14.679
<v Speaker 2>if you rely on it too much. Uses more server resources,

359
00:16:14.960 --> 00:16:18.600
<v Speaker 2>can be slower on small screens. Advice, use it for convenience,

360
00:16:18.639 --> 00:16:21.720
<v Speaker 2>but don't get totally dependent. Keep those CLI skills sharp.

361
00:16:21.879 --> 00:16:24.279
<v Speaker 4>Makes sense. So how do we install Webmin?

362
00:16:24.600 --> 00:16:27.279
<v Speaker 2>Pretty easy? Use bubby a get to download the package

363
00:16:27.360 --> 00:16:30.559
<v Speaker 2>Debian dot deb or CentOS dot rpm from the webmin

364
00:16:30.639 --> 00:16:34.720
<v Speaker 2>site on Debian. Install with these pgi than apt get

365
00:16:35.559 --> 00:16:40.120
<v Speaker 2>f install to fix any missing dependencies on Cento, YUMNOGPG

366
00:16:40.279 --> 00:16:43.600
<v Speaker 2>check local install, then access at house in your browser.

367
00:16:43.679 --> 00:16:47.000
<v Speaker 2>Go to https dot your Dash server dash ep dot

368
00:16:47.000 --> 00:16:49.879
<v Speaker 2>one zero zero zero zero use https. You'll get a

369
00:16:49.879 --> 00:16:53.320
<v Speaker 2>certificate warning at first because it's self signed. But and

370
00:16:53.360 --> 00:16:55.320
<v Speaker 2>this is cool, it's really easy to get rid of

371
00:16:55.360 --> 00:16:58.320
<v Speaker 2>that warning and make it properly secure. You install a

372
00:16:58.399 --> 00:17:00.799
<v Speaker 2>trusted SSL certificate use let's encrypt.

373
00:17:00.919 --> 00:17:01.519
<v Speaker 3>It's free.

374
00:17:01.759 --> 00:17:03.919
<v Speaker 2>Usually need to patch you web server installed first because

375
00:17:04.000 --> 00:17:06.279
<v Speaker 2>let's encrypt uses that to check you on the server, AmAm.

376
00:17:06.319 --> 00:17:09.599
<v Speaker 2>Then inside webmen there's an SSL module. Few clicks, request

377
00:17:09.599 --> 00:17:12.759
<v Speaker 2>the certificate, install it, Boom, secure padlock in your browser,

378
00:17:12.799 --> 00:17:13.519
<v Speaker 2>no more warnings.

379
00:17:13.599 --> 00:17:14.079
<v Speaker 4>Nice.

380
00:17:14.200 --> 00:17:16.880
<v Speaker 2>And while you're at it, add two factor authentication to

381
00:17:17.039 --> 00:17:20.079
<v Speaker 2>FA to your Webman login using Google Authenticator or similar

382
00:17:20.200 --> 00:17:21.960
<v Speaker 2>extra security layer. Highly recommend it.

383
00:17:21.960 --> 00:17:25.319
<v Speaker 1>Definitely good practice. So beyond setup, what can webmen actually

384
00:17:25.359 --> 00:17:27.279
<v Speaker 1>do for managing the server day to day?

385
00:17:27.440 --> 00:17:30.680
<v Speaker 2>Its strength is modules. It scans your server, finds installed

386
00:17:30.720 --> 00:17:33.920
<v Speaker 2>software and gives you modules to manage them. Okay, like

387
00:17:33.960 --> 00:17:37.279
<v Speaker 2>what well the webman group lets you configure webmen itself

388
00:17:37.359 --> 00:17:39.839
<v Speaker 2>back up its settings. See logs of who did what

389
00:17:40.039 --> 00:17:43.519
<v Speaker 2>manage Webman users the system group gives you visual ways

390
00:17:43.559 --> 00:17:47.960
<v Speaker 2>to manage services, system sadle stuff, users in groups, view logs,

391
00:17:48.240 --> 00:17:49.720
<v Speaker 2>configure the SSH server.

392
00:17:50.119 --> 00:17:51.920
<v Speaker 4>Ah like disabling root log in.

393
00:17:51.880 --> 00:17:56.599
<v Speaker 2>Easily exactly and requiling SSH keys critical stuff made easier.

394
00:17:56.960 --> 00:18:00.000
<v Speaker 2>And remember usermen lets your regular users manage their own

395
00:18:00.039 --> 00:18:03.920
<v Speaker 2>own email, maybe databases, simple web stuff without needing full

396
00:18:03.920 --> 00:18:04.759
<v Speaker 2>admin access.

397
00:18:05.000 --> 00:18:07.920
<v Speaker 4>Handy Okay. Managing the server is one thing. What about

398
00:18:08.000 --> 00:18:10.240
<v Speaker 4>running cool applications on the server? What kind of stuff

399
00:18:10.240 --> 00:18:10.640
<v Speaker 4>can we do?

400
00:18:11.039 --> 00:18:11.240
<v Speaker 3>Oh?

401
00:18:11.400 --> 00:18:14.039
<v Speaker 2>Tons, That's where the fun begins. Thanks to open source,

402
00:18:14.240 --> 00:18:17.480
<v Speaker 2>most installs follow a pattern. Download, unpack, create a database,

403
00:18:17.480 --> 00:18:19.880
<v Speaker 2>maybe run a web installer customized.

404
00:18:19.400 --> 00:18:20.400
<v Speaker 4>Where do you find these apps?

405
00:18:20.640 --> 00:18:23.160
<v Speaker 2>A great place to browse? And even fried demos? Is

406
00:18:23.200 --> 00:18:27.680
<v Speaker 2>opensource cms dot com really useful? So examples. You could

407
00:18:27.720 --> 00:18:31.519
<v Speaker 2>run moodle a massive learning management system, create online courses

408
00:18:31.559 --> 00:18:35.079
<v Speaker 2>training platforms. Hosting it yourself gives you total control over

409
00:18:35.160 --> 00:18:37.359
<v Speaker 2>content and data, unlike hosted options.

410
00:18:37.440 --> 00:18:39.160
<v Speaker 4>Total ownership nice or.

411
00:18:39.119 --> 00:18:42.519
<v Speaker 2>Astick it a great help desk system, track customer issues,

412
00:18:42.599 --> 00:18:46.119
<v Speaker 2>manage support, automatically create tickets from emails. People think it's

413
00:18:46.160 --> 00:18:48.400
<v Speaker 2>overkill for small shops, but it quickly becomes essential.

414
00:18:48.680 --> 00:18:50.200
<v Speaker 3>Got long ugly links.

415
00:18:50.240 --> 00:18:53.759
<v Speaker 2>URLs lets you run your own URL shortener, custom links, stats,

416
00:18:53.799 --> 00:18:57.480
<v Speaker 2>password protection. You control it, not some company that might disappear.

417
00:18:57.519 --> 00:19:01.039
<v Speaker 2>Handy work about privacy. OpenVPN, Set up your own VPN

418
00:19:01.079 --> 00:19:04.920
<v Speaker 2>on your vps, encrypt your traffic bypass geoblocks, securely access

419
00:19:04.920 --> 00:19:07.799
<v Speaker 2>your stuff. More set up than commercial VPNs, but way

420
00:19:07.799 --> 00:19:11.960
<v Speaker 2>more control and potentially better security for businesses ODO is amazing.

421
00:19:12.000 --> 00:19:16.559
<v Speaker 2>It's a suite CRM, accounting, HR sales, inventory, all integrated.

422
00:19:16.599 --> 00:19:20.720
<v Speaker 2>Start early with something like this, grow smoothly. Comprehensive need surveys,

423
00:19:20.880 --> 00:19:25.839
<v Speaker 2>lime survey, really advance questionnaires, conditional logic quizzes, even secure voting,

424
00:19:26.039 --> 00:19:30.640
<v Speaker 2>super flexible data export too. Need mailing lists GNU mailman

425
00:19:30.839 --> 00:19:34.839
<v Speaker 2>the standard for discussion lists, announcements, simple web interface for

426
00:19:34.960 --> 00:19:37.680
<v Speaker 2>archives admin Spam detection built in.

427
00:19:37.839 --> 00:19:40.279
<v Speaker 1>We're about selling stuff online off commerce.

428
00:19:40.480 --> 00:19:43.519
<v Speaker 2>Build your own online store. Just remember handling payments and

429
00:19:43.559 --> 00:19:47.359
<v Speaker 2>customer data means you need really tight security, non negotiable

430
00:19:47.839 --> 00:19:51.119
<v Speaker 2>and finally, ever wanted your own Wikipedia media wiki. The

431
00:19:51.160 --> 00:19:54.880
<v Speaker 2>software Wikipedia uses great for collaborative knowledge bases, group editing,

432
00:19:55.000 --> 00:19:58.200
<v Speaker 2>version tracking, dynamic faques, oh and back in Webman the

433
00:19:58.279 --> 00:20:01.599
<v Speaker 2>system and server status module set up, scheduled monitoring, get

434
00:20:01.599 --> 00:20:04.440
<v Speaker 2>email alerts if disk space gets low, memory runs out,

435
00:20:04.519 --> 00:20:07.920
<v Speaker 2>server loads spikes, even if your SSL certificate is expiring.

436
00:20:08.200 --> 00:20:10.519
<v Speaker 2>Acts like a central dashboard for your VPS health.

437
00:20:10.559 --> 00:20:13.920
<v Speaker 1>That monitoring sounds crucial. Okay, this whole journey's about control,

438
00:20:13.960 --> 00:20:16.680
<v Speaker 1>but you know the same, great power, great responsibility. What's

439
00:20:16.720 --> 00:20:18.599
<v Speaker 1>the bedrock of VPS security?

440
00:20:18.960 --> 00:20:19.160
<v Speaker 3>Right?

441
00:20:19.359 --> 00:20:22.359
<v Speaker 2>It starts with thinking about physical security even though it's virtual.

442
00:20:23.000 --> 00:20:26.640
<v Speaker 2>Your provider handles the actual hardware security, but your console

443
00:20:26.920 --> 00:20:28.759
<v Speaker 2>access that direct roof login.

444
00:20:29.279 --> 00:20:31.759
<v Speaker 3>Disable it when you're not using it. That password often

445
00:20:31.799 --> 00:20:32.680
<v Speaker 3>only gets shown once.

446
00:20:32.960 --> 00:20:33.440
<v Speaker 4>Good point.

447
00:20:33.599 --> 00:20:38.000
<v Speaker 2>Then then file permissions. We talked about ReadWrite, execute for owner, group,

448
00:20:38.039 --> 00:20:42.039
<v Speaker 2>other mastering, chown and chamaud is. Vital system programs run

449
00:20:42.039 --> 00:20:46.240
<v Speaker 2>as specific users like www dot data for apatche mess

450
00:20:46.319 --> 00:20:49.160
<v Speaker 2>up permissions. You can break things badly. I once locked

451
00:20:49.160 --> 00:20:51.960
<v Speaker 2>myself out by removing world read from etc past.

452
00:20:52.160 --> 00:20:52.680
<v Speaker 3>Don't do that.

453
00:20:52.960 --> 00:20:53.599
<v Speaker 4>Lesson learned.

454
00:20:53.720 --> 00:20:56.200
<v Speaker 2>There's also advanced stuff like set would set GID for

455
00:20:56.279 --> 00:20:58.839
<v Speaker 2>running commands as the file owner and cylinics for super

456
00:20:58.880 --> 00:21:02.039
<v Speaker 2>tight security. But honestly, cy Linux is complex. Often beginners

457
00:21:02.119 --> 00:21:04.519
<v Speaker 2>leave it off for admin access to do as king

458
00:21:04.799 --> 00:21:08.559
<v Speaker 2>granular control audit trail way better than everyone being route.

459
00:21:08.599 --> 00:21:10.799
<v Speaker 4>Okay, what about network attacks.

460
00:21:10.640 --> 00:21:14.279
<v Speaker 2>Open ports and firewalls. Your firewall is the bouncer. Use

461
00:21:14.319 --> 00:21:17.119
<v Speaker 2>netstat to see what services are listening on which ports,

462
00:21:17.319 --> 00:21:20.039
<v Speaker 2>like twenty two for Ssh, twenty five for email. Then

463
00:21:20.160 --> 00:21:23.519
<v Speaker 2>use a firewall tool like firewall d common on Sentos,

464
00:21:23.599 --> 00:21:27.839
<v Speaker 2>installable on Debian to set rules. Use zones to control access,

465
00:21:28.160 --> 00:21:29.599
<v Speaker 2>block bad ips.

466
00:21:29.200 --> 00:21:30.359
<v Speaker 3>Trying to hammer your server.

467
00:21:30.559 --> 00:21:31.960
<v Speaker 5>Lock get down definitely.

468
00:21:32.200 --> 00:21:36.880
<v Speaker 2>And for SSH key based authentication, use keys, not just passwords.

469
00:21:37.200 --> 00:21:39.839
<v Speaker 2>Generate a public private key pair, put the public key

470
00:21:39.839 --> 00:21:43.519
<v Speaker 2>on the server, then crucially disabled password login completely in

471
00:21:43.559 --> 00:21:46.960
<v Speaker 2>your shot config. Makes brute force attacks much harder.

472
00:21:47.079 --> 00:21:48.720
<v Speaker 4>Keys not passwords. Got it?

473
00:21:48.880 --> 00:21:52.079
<v Speaker 2>And finally logs your eyes and ears. Everything gets logged

474
00:21:52.079 --> 00:21:55.400
<v Speaker 2>in varlog check secure or off, dot log for logins,

475
00:21:55.480 --> 00:21:59.440
<v Speaker 2>BTMP for failed logins, patchee logs, et cetera. Use tail

476
00:21:59.519 --> 00:22:02.279
<v Speaker 2>to watch log live, grep to search for patterns like

477
00:22:02.359 --> 00:22:03.960
<v Speaker 2>failed password attempts from bots.

478
00:22:04.119 --> 00:22:06.000
<v Speaker 4>Use knocking exactly and.

479
00:22:06.200 --> 00:22:08.960
<v Speaker 2>Log ritate automatically manages these logs that they don't fill

480
00:22:09.000 --> 00:22:10.359
<v Speaker 2>your disc essential housekeeping.

481
00:22:10.400 --> 00:22:13.680
<v Speaker 1>Okay, security sounds manageable if you follow the steps, but

482
00:22:14.000 --> 00:22:17.359
<v Speaker 1>stuff happens backups. You said, nothing is more frustrating than

483
00:22:17.359 --> 00:22:19.559
<v Speaker 1>making a small change and finding it trashes everything.

484
00:22:19.640 --> 00:22:23.359
<v Speaker 2>Oh. Absolutely, backups are non negotiable. Backup basics, know what

485
00:22:23.440 --> 00:22:28.960
<v Speaker 2>to backup, etc. Canfigx, dot, home user data, varww web files, databases,

486
00:22:29.079 --> 00:22:29.680
<v Speaker 2>key logs.

487
00:22:29.920 --> 00:22:31.519
<v Speaker 3>Decide how far back you need copies?

488
00:22:31.559 --> 00:22:32.359
<v Speaker 4>Where do you store them?

489
00:22:32.440 --> 00:22:36.759
<v Speaker 2>Options another VPS, different provider. Location is best your home computer,

490
00:22:36.880 --> 00:22:42.160
<v Speaker 2>cloud storage, dropbox, Google Drive, etc. My paranoid rule, if

491
00:22:42.200 --> 00:22:44.839
<v Speaker 2>losing the data would make you literally cry, back it

492
00:22:44.920 --> 00:22:49.000
<v Speaker 2>up at least three waste places, version history, multiple virtual spots,

493
00:22:49.079 --> 00:22:50.160
<v Speaker 2>multiple physical.

494
00:22:49.839 --> 00:22:51.519
<v Speaker 4>Spots, three places for crying data.

495
00:22:51.599 --> 00:22:56.359
<v Speaker 2>Got it and scheduled versus on demand, automated daily, maybe

496
00:22:56.400 --> 00:22:59.279
<v Speaker 2>hourly if needed. Schedule time to check your backups work,

497
00:22:59.359 --> 00:23:01.720
<v Speaker 2>not make them. I've seen people find out their backups

498
00:23:01.759 --> 00:23:04.200
<v Speaker 2>failed silently for weeks right when they needed them.

499
00:23:04.319 --> 00:23:04.960
<v Speaker 3>Awful feeling.

500
00:23:05.039 --> 00:23:07.880
<v Speaker 4>Check the backups regularly. Okay, how do we actually do

501
00:23:07.920 --> 00:23:08.480
<v Speaker 4>the backups?

502
00:23:08.519 --> 00:23:09.839
<v Speaker 3>Methods? Very simple way.

503
00:23:10.200 --> 00:23:12.880
<v Speaker 2>Use Tarta archive files, ges it to compress them, write

504
00:23:12.880 --> 00:23:15.640
<v Speaker 2>a shell script, schedule it with chrontab use ersing to

505
00:23:15.680 --> 00:23:16.680
<v Speaker 2>efficiently copy.

506
00:23:16.480 --> 00:23:18.880
<v Speaker 5>Files off site, man line way YEP.

507
00:23:19.240 --> 00:23:22.559
<v Speaker 2>Or use a jewy tool like duplicat free open source

508
00:23:22.640 --> 00:23:27.839
<v Speaker 2>web interface access via ssh tunnel. Does incremental version backups

509
00:23:28.160 --> 00:23:31.200
<v Speaker 2>save space lets you restore from specific points in time.

510
00:23:31.400 --> 00:23:35.440
<v Speaker 2>Pretty neat. Also version control with Git not a full backup,

511
00:23:35.480 --> 00:23:38.440
<v Speaker 2>but amazing for tracking changes to specific files. Can figs

512
00:23:38.519 --> 00:23:41.880
<v Speaker 2>code get in it, ad commit, roll back mistakes easily,

513
00:23:42.119 --> 00:23:45.440
<v Speaker 2>push to GitHub for off site history, great frontline defense.

514
00:23:45.200 --> 00:23:48.200
<v Speaker 4>For changes, get for tracking changes smart Now.

515
00:23:48.640 --> 00:23:53.400
<v Speaker 2>The synchronization debate. Sinking data like dropbox seems easy instant

516
00:23:53.400 --> 00:23:58.319
<v Speaker 2>access everywhere, but it's risky errors ransomware they sink instantly too.

517
00:23:58.599 --> 00:24:03.119
<v Speaker 2>Better to have air gapped backs external drives disconnected stored.

518
00:24:02.799 --> 00:24:05.000
<v Speaker 5>Safely air gapped makes sense.

519
00:24:04.759 --> 00:24:08.640
<v Speaker 2>And finally simulated disaster recovery. You must test restoring your

520
00:24:08.640 --> 00:24:12.680
<v Speaker 2>backups regularly monthly at least build confidence, know your migration

521
00:24:12.759 --> 00:24:15.559
<v Speaker 2>plan if you need to move servers, copy files, databases,

522
00:24:15.680 --> 00:24:17.319
<v Speaker 2>users can figs test everything.

523
00:24:17.359 --> 00:24:19.119
<v Speaker 4>Practice makes perfect totally.

524
00:24:19.000 --> 00:24:21.039
<v Speaker 2>And like the book says, best feeling ever is when

525
00:24:21.039 --> 00:24:23.440
<v Speaker 2>someone panics about deleted data and you can calmly say,

526
00:24:23.640 --> 00:24:25.400
<v Speaker 2>no problem, got last night's backup.

527
00:24:25.519 --> 00:24:28.119
<v Speaker 5>That's backup, Zen, backup, Zen, I like it.

528
00:24:28.759 --> 00:24:32.640
<v Speaker 1>So we've covered a ton concept setup security backups. Now

529
00:24:32.680 --> 00:24:36.559
<v Speaker 1>the really exciting part unleashing the power what cool stuff

530
00:24:36.559 --> 00:24:38.039
<v Speaker 1>can we run on this vps we've built.

531
00:24:38.119 --> 00:24:39.920
<v Speaker 2>Yeah, this is where it gets fun. The open source

532
00:24:39.960 --> 00:24:42.599
<v Speaker 2>world is huge. Like we said, installation is often similar

533
00:24:43.079 --> 00:24:47.400
<v Speaker 2>download unpacked, maybe database setup web install, check opensource cms dot.

534
00:24:47.200 --> 00:24:48.000
<v Speaker 3>Com for demos.

535
00:24:48.039 --> 00:24:51.599
<v Speaker 2>So think about moodle world class learning platform, run your

536
00:24:51.599 --> 00:24:54.680
<v Speaker 2>own courses, training, total control or as stick it for

537
00:24:54.720 --> 00:24:57.279
<v Speaker 2>help desk support, track issues and proof customer service.

538
00:24:57.319 --> 00:24:58.000
<v Speaker 5>Super useful.

539
00:24:58.039 --> 00:24:58.920
<v Speaker 4>We mentioned those well.

540
00:24:59.279 --> 00:25:02.000
<v Speaker 2>RLS for your your own short links, open VPN for

541
00:25:02.039 --> 00:25:05.519
<v Speaker 2>your own private secure network connection, ODO for running your

542
00:25:05.680 --> 00:25:10.160
<v Speaker 2>entire business, CRM accounting, the works, keep going, Lime Survey

543
00:25:10.200 --> 00:25:13.599
<v Speaker 2>for powerful online surveys and quizzes, gn you Mailman for

544
00:25:13.720 --> 00:25:17.000
<v Speaker 2>managing email discussion lists, as commerce to build your own

545
00:25:17.039 --> 00:25:20.319
<v Speaker 2>online store. Remember that security first, and the wiki one

546
00:25:20.440 --> 00:25:24.359
<v Speaker 2>media wiki run your own collaborative knowledge base just like Wikipedia.

547
00:25:24.400 --> 00:25:27.880
<v Speaker 2>Great for teams or FAQs. The possibilities with open source

548
00:25:27.960 --> 00:25:30.200
<v Speaker 2>on your own vps are just immense.

549
00:25:30.640 --> 00:25:32.039
<v Speaker 4>Wow, what a journey.

550
00:25:32.119 --> 00:25:35.119
<v Speaker 1>Indeed, we went from asking what even is a VPS

551
00:25:35.599 --> 00:25:40.160
<v Speaker 1>to understanding setup, command line basics, security, backups, and now

552
00:25:40.200 --> 00:25:41.720
<v Speaker 1>all these amazing applications you.

553
00:25:41.640 --> 00:25:44.640
<v Speaker 2>Can run exactly. It's a deep dive that hopefully gives

554
00:25:44.640 --> 00:25:47.240
<v Speaker 2>you more than just surface level info. You should now

555
00:25:47.319 --> 00:25:50.240
<v Speaker 2>have that foundational knowledge to really take control of your

556
00:25:50.240 --> 00:25:52.279
<v Speaker 2>digital space shape at how you want it.

557
00:25:52.400 --> 00:25:54.319
<v Speaker 1>So, listening to this, the final question for you is

558
00:25:55.160 --> 00:25:59.240
<v Speaker 1>what new possibility does your newfound VPS knowledge open up

559
00:25:59.480 --> 00:26:02.440
<v Speaker 1>for your prices, your business, maybe just your own curiosity.

560
00:26:02.440 --> 00:26:04.720
<v Speaker 1>The digital world, in a very real sense, is now

561
00:26:04.759 --> 00:26:05.519
<v Speaker 1>yours to build
