summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRyan Schanzenbacher <ryan@rschanz.org>2021-12-24 03:17:57 -0500
committerRyan Schanzenbacher <ryan@rschanz.org>2021-12-24 03:17:57 -0500
commitf5adec0767089978f139b79617c7122b9e91c440 (patch)
tree9e41e932213d684f588eb7c86a0fd32c13ec2542
parent6610ba2088307f2d406fce7666678945d447a818 (diff)
Spelling error
-rw-r--r--content/projects/stoic_productions.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/projects/stoic_productions.md b/content/projects/stoic_productions.md
index 14a9ecf..9f88cff 100644
--- a/content/projects/stoic_productions.md
+++ b/content/projects/stoic_productions.md
@@ -22,7 +22,7 @@ I'd like to lay out the current set of services we utilize to run Stoic Producti
22 - The rationale behind this is all of Stoic Productions' services run in an OpenSUSE Leap VM. This is done for two reasons. First, it keeps other services I have running for my own personal use separate from Stoic Productions' services. Second, it means that if anything happens to my personal services (perhaps I underestimate the memory something may use), the website stays available since its VM won't crash. 22 - The rationale behind this is all of Stoic Productions' services run in an OpenSUSE Leap VM. This is done for two reasons. First, it keeps other services I have running for my own personal use separate from Stoic Productions' services. Second, it means that if anything happens to my personal services (perhaps I underestimate the memory something may use), the website stays available since its VM won't crash.
23 - Reverse Proxy: This is another physical machine, and it's sole purpose is to be as invisible as possible. I put this in when I was having stability issues with an old machine the server used to run on. Its job is if it cannot reach the main server, it will serve a backed up copy of the main site and display a nice error page to describe the problem to the user, rather than them getting an error like "No route to host" 23 - Reverse Proxy: This is another physical machine, and it's sole purpose is to be as invisible as possible. I put this in when I was having stability issues with an old machine the server used to run on. Its job is if it cannot reach the main server, it will serve a backed up copy of the main site and display a nice error page to describe the problem to the user, rather than them getting an error like "No route to host"
24 - NGINX: This is the main content provider for our website. Any service that we utilize through a web browser will go through this. This application manages requests for our subdomains and routes each request to their respective endpoint. 24 - NGINX: This is the main content provider for our website. Any service that we utilize through a web browser will go through this. This application manages requests for our subdomains and routes each request to their respective endpoint.
25 - Postfix & Dovecot: I'm going to group these together as they form the "email" portion of the server. Postfix is used as an MTU to send and receive messages while Dovecot is used to allow IMAP clients to actually view the messages we've gotten. In the background, I run spamassassin, have potential senders get screened by blacklists like Spamhaus' SBL, and emails also get screened through clamav for potential viruses. 25 - Postfix & Dovecot: I'm going to group these together as they form the "email" portion of the server. Postfix is used as an MTA to send and receive messages while Dovecot is used to allow IMAP clients to actually view the messages we've gotten. In the background, I run spamassassin, have potential senders get screened by blacklists like Spamhaus' SBL, and emails also get screened through clamav for potential viruses.
26 - Nextcloud: I've set this up for internal use. It's what our team (currently about 12 members, but fluctuates with each production cycle) uses to share files with one another. We use this over things like Google Drive simply because the data stays completely in-house. 26 - Nextcloud: I've set this up for internal use. It's what our team (currently about 12 members, but fluctuates with each production cycle) uses to share files with one another. We use this over things like Google Drive simply because the data stays completely in-house.
27 - Discourse Forum: This is the site people can use to talk with us, view our films, or talk with others about our films. It's run inside of a docker container to provide to allow it to be run as "a service" rather than trying to install all of its dependencies (like Ruby on Rails) and making the underlying system a tangled mess. I've added customizations to allow for the proper embedding of our video player. 27 - Discourse Forum: This is the site people can use to talk with us, view our films, or talk with others about our films. It's run inside of a docker container to provide to allow it to be run as "a service" rather than trying to install all of its dependencies (like Ruby on Rails) and making the underlying system a tangled mess. I've added customizations to allow for the proper embedding of our video player.
28 - OvenMediaEncoder: This is seldom used, but it is our service that allows us to host a live stream. Usually used when we are premiering a new film, we use this plus chat extensions within Discourse to provide end users a "Youtube like" stream experience 28 - OvenMediaEncoder: This is seldom used, but it is our service that allows us to host a live stream. Usually used when we are premiering a new film, we use this plus chat extensions within Discourse to provide end users a "Youtube like" stream experience