Added Online! post

This commit is contained in:
Xavi 2023-02-18 23:37:04 -08:00
parent 8b107d63db
commit 79da22ba37

View File

@ -0,0 +1,88 @@
title: "Online!"
date: 2023-02-18T12:58:09-08:00
description: Web Development - Administration
tags: ["Web Development","Administration"]
---
Hopefully you can see this because that means that I didn\'t mess
anything up when updating the site! I\'ll quickly recap what I did over
the last week and clarify what\'s in the pipeline for this upcoming
week.
So I ended up destroying and remaking the
[Vultr](https://www.vultr.com/)
VPS **\[Virtual Private Server if I didn\'t
clarify that previously\]** so that I could have a fresh, clean
environment to start messing around in. I decided to go with their
smallest, and cheapest plan to start things off **\[I think it can
handle the traffic that I expect to start \"pouring\" in\]**.
{{< image_sc "/vultr_1.png" "Vultr Pricing" "Vultr Cloud Pricing" >}}
I found this
[video](https://www.youtube.com/watch?v=-B-4RG8Q0aw)
that explained how to calculate how much
needed bandwidth I needed to budget for. Again I don\'t think I need
much **\[something tells me I\'m the only one checking in on this
website 100 times a day\]**. I stuck with a
[Debian](https://www.debian.org/)
distribution for no reason in particular
other than it\'s what I used previously on other VPSs **\[if your
unfamiliar with Linux and Linux distributions I\'ll make some intro to
Linux guides in the future that\'ll explain all the common nerd
jargon\]**.
I grabbed the domain name from
[dynadot](https://www.dynadot.com/)
and changed the DNS records to have it point
to the IP of the VPS. I\'ll write up a full guide for this in a bit
**\[honestly it\'s pretty easy\]**. I then installed nGinx, changed the
config files to point to the html/css files, and started the service
**\[kinda skipped the nitty gritty but again, guide incoming\]**.
I was able to visit the site at this point from a client device but
still had to set up
[SSL](https://www.ssl.com/faqs/what-is-https/)
**\[Secure Sockets Layer\]** so that the
connection was encrypted. Apparently it was pretty uncommon in the past
to have encrypted connections on personal websites but that was changed
with the help of the [EFF](https://www.eff.org/)
with [let\'s
encrypt](https://letsencrypt.org/)
which offers free, open certificates
**\[pretty cool of them honestly\]**. To make things even easier they
also provide a python script(?) called
[certbot](https://certbot.eff.org/)
which automates the process of obtaining one
of these ssl certificates. After I ran it I got the cool green lock icon
in the address bar and was feeling pretty cool myself! **:)**
Those were the major updates for this week. Next week I\'ll be looking
into hosting a git server to upload my code **\[including anything that
I create for this website ie. html/css/scripting stuff\]** and a git
visualiser. Hosting a git server seems easy enough but finding the right
visualiser might need a bit more research. Right now the most promising
candidate is
[stagit](https://codemadness.org/stagit.html)
which is a static git page generator. Hope
that works out.
The stretch goal for this week is the possibility to host videos with
**\[maybe?\]** a [peertube](https://joinpeertube.org/)
instance. Not sure how much of a pain and/or
the bandwidth limitations will throttle the experience too much but it
sounds useful to post, even short, videos demonstrating processes
explicitly **\[if a picture is 1000 words than what does that make a
video\]**.
That\'s the update for the week.
Next *TODOS! **\[Can be updated throughout the week\]***
- Look into hosting git server
- Set up gitolite for git permissions
- Set up stagit for git visualization
- Possibly Peertube for embedded videos