1 files changed, 1 insertions, 1 deletions
diff --git a/content/projects/stoic_productions.md b/content/projects/stoic_productions.md
index a7e9a85..14a9ecf 100644
--- a/content/projects/stoic_productions.md
+++ b/content/projects/stoic_productions.md
@@ -27,7 +27,7 @@ I'd like to lay out the current set of services we utilize to run Stoic Producti
  - 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.
  - 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
  - KeyCloak: Arguably one of the most important services being run, this is our Authentication and Identity Federation server. Most of our services (like Nextcloud and Discourse) use either SAML or OpenID to communicate with the Keycloak instance. For services that need access to the user accounts that may not be able to take advatntage of either technology, we fall back to the LDAP protocol. Most applications that need some sort of authentication will provide a mechanism to use LDAP. This is how we authenticate Postfix and Dovecot with our users. It allows me to make the users once and have them propogate everywhere. I also had to implement custom LDAP attributes to reflect whether a user was enabled in Keycloak or not to better control login access.
-  - Main Site: for the main site, I used to use Wordpress to generate the site and all of its content. However, around January of 2021, I took two afternoons and converted the theme to a Hugo theme (essentially picked and chose items and rebuilt the HTML in a Hugo way) and converted the site to a statically generated site using Hugo. This closed a huge attack platform off, sped up our website, sped up my development, and decreased the load on the server. Instead of waiting for PHP to execute and make my way through half a dozen menus just to update a word or phrase, I can now just use Git to manage the website. Plus, I set-up a webhook from the Git Repo (hosted privately by me as well) to detect whenever I push a change and rebuild the site, allowing near instant changes to be made on the website.
+  - Main Site: for the main site, I used to use Wordpress to generate the site and all of its content. However, around January of 2021, I took two afternoons and converted the theme to a Hugo theme (essentially picked and chose items and rebuilt the HTML in a Hugo way) and converted the site to a statically generated site using Hugo. This closed a off a huge attack vector, sped up our website, sped up my development, and decreased the load on the server. Instead of waiting for PHP to execute or needing to make my way through half a dozen menus just to update a word or phrase, I can now just use Git to manage the website. Plus, I set-up a webhook from the Git Repo (hosted privately by me as well) to detect whenever I push a change and rebuild the site, allowing near instant changes to be made on the website.
  ### Challenges

diff --git a/content/projects/stoic_productions.md b/content/projects/stoic_productions.md index a7e9a85..14a9ecf 100644 --- a/content/projects/stoic_productions.md +++ b/content/projects/stoic_productions.md
@@ -27,7 +27,7 @@ I'd like to lay out the current set of services we utilize to run Stoic Producti
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
29	- KeyCloak: Arguably one of the most important services being run, this is our Authentication and Identity Federation server. Most of our services (like Nextcloud and Discourse) use either SAML or OpenID to communicate with the Keycloak instance. For services that need access to the user accounts that may not be able to take advatntage of either technology, we fall back to the LDAP protocol. Most applications that need some sort of authentication will provide a mechanism to use LDAP. This is how we authenticate Postfix and Dovecot with our users. It allows me to make the users once and have them propogate everywhere. I also had to implement custom LDAP attributes to reflect whether a user was enabled in Keycloak or not to better control login access.	29	- KeyCloak: Arguably one of the most important services being run, this is our Authentication and Identity Federation server. Most of our services (like Nextcloud and Discourse) use either SAML or OpenID to communicate with the Keycloak instance. For services that need access to the user accounts that may not be able to take advatntage of either technology, we fall back to the LDAP protocol. Most applications that need some sort of authentication will provide a mechanism to use LDAP. This is how we authenticate Postfix and Dovecot with our users. It allows me to make the users once and have them propogate everywhere. I also had to implement custom LDAP attributes to reflect whether a user was enabled in Keycloak or not to better control login access.
30	- Main Site: for the main site, I used to use Wordpress to generate the site and all of its content. However, around January of 2021, I took two afternoons and converted the theme to a Hugo theme (essentially picked and chose items and rebuilt the HTML in a Hugo way) and converted the site to a statically generated site using Hugo. This closed a huge attack platform off, sped up our website, sped up my development, and decreased the load on the server. Instead of waiting for PHP to execute and make my way through half a dozen menus just to update a word or phrase, I can now just use Git to manage the website. Plus, I set-up a webhook from the Git Repo (hosted privately by me as well) to detect whenever I push a change and rebuild the site, allowing near instant changes to be made on the website.	30	- Main Site: for the main site, I used to use Wordpress to generate the site and all of its content. However, around January of 2021, I took two afternoons and converted the theme to a Hugo theme (essentially picked and chose items and rebuilt the HTML in a Hugo way) and converted the site to a statically generated site using Hugo. This closed a off a huge attack vector, sped up our website, sped up my development, and decreased the load on the server. Instead of waiting for PHP to execute or needing to make my way through half a dozen menus just to update a word or phrase, I can now just use Git to manage the website. Plus, I set-up a webhook from the Git Repo (hosted privately by me as well) to detect whenever I push a change and rebuild the site, allowing near instant changes to be made on the website.
31		31
32	### Challenges	32	### Challenges
33		33