Commit 3ba7e1a9 authored by Michael Bailey's avatar Michael Bailey

Hot off the presses from w3schools to your production environment

parent b0306761
......@@ -8,15 +8,25 @@ date: 2018-04-29T00:00:00-0400
hero_image: "/assets/img/servers.jpg"
hero_alt: "Future Aquia Servers in a car"
---
<style>
img[alt=imt] { width: 25%; }
img[alt="imt"] {
width: 25%;
}
@media only screen and (max-width: 600px) {
img[alt="imt"] {
width: 100%;
}
}
</style>
This is going to be one part of what will presumably be part of a multi-piece transparency initiative in which I, Michael Bailey (Lead Systems Admin on the Infrastructure Management Team at SRCT), show the campus community (and SRCT) how information is served at SRCT. I'll cover how our sites are served and a few IT tricks we use including Host matching, reverse proxy, and auditing. **These pieces are going to tow a line between what is right and what we do**. I will try to disclaim what we do and what the right move would be to do, because they aren't always the same as this is effectively a volunteer position with limited resources.
# Addressing Aquia
I've been hearing a lot in terms of people wondering what the situation is with Aquia. Presently we are working on getting edits shuffled between us and Professor Bell per ITS's request. We are working now on getting our servers to a new intermediate location until we can move in. After all of this is done, we may need to hold for background checks. They have not started to my knowledge and really only apply to me.
I've been hearing a lot in terms of people wondering what the situation is with Aquia. Presently we are working on having relatively semantic changes shuffled between us and Professor Bell according to ITS's requests and concerns. We are working now on getting our servers to a new intermediate location until we can move in. After all of this is done, we may need to hold for background checks. They have not started to my knowledge and really only apply to me.
# How Requests are Made to Us
......@@ -123,6 +133,6 @@ We won't go in depth as to how the service is configured, but I should disclose
**It's worth noting another (probably better) way to do all of this is through UNIX Sockets** or in Django's case uwsgi. For more on Sockets, see the Tweet below by Julia Evans aka @b0rk.
[![imt](/assets/img/imt/sockets.png "Sockets comic")](https://twitter.com/b0rk/status/810261842291462145)
[![imt]({{ site.baseurl | prepend: site.url }}/assets/img/imt/sockets.png "Sockets comic"){: .img-fluid }](https://twitter.com/b0rk/status/810261842291462145)
So now we have a request that goes from the browser, to our server, to an internal port, and back out to the interwebz! Could be better, could be worse, but given limited man-hours and infrastructure, this is how most SRCT services look.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment