master
km0 1 year ago
parent 8f4d78bd4d
commit e59a5bcc8a

@ -106,6 +106,31 @@ Going online depends on several variables, many of them being out of reach.
For this reason this section doesn't provide a comprehensive guide to put the project online, but just a reference to the configuration currently in use on the Soupboat.
-->
## Deployment ?? Production ??
There are so many technical terms I'm not confortable _just using_, so I need to negotiate a glossary.
Sometimes to find alternatives: like what happened with the naming of default branch in platforms such as GitHub, that switched from `master` to `main` in order to stop using terms related to slavery.
Sometimes to retreace genealogies, that is: to offer other contexts for a word to refer to. A redemption arc for cursed words. No clue how to do it though, a way could be to use them critically, stumbling upon them, connnecting with different images. So here some attempts.
Deployment in software and web application means to push changes from a development environment to a production one. To move and install the code from your computer to a server, for example.
When writing a piece of documentation together with my friend Chae, she reacted puzzled to my generic use of this very specific word? I reacted puzzled to this puzzlessness, and went searching for the real-world meaning of a term imported and naturalized in the technical jargon.
Deployment is a military term, that refers to moving troops and army around on the battlefield. The spatiality of this gesture, going from home to the warzone, or from a target to another, suggests a form of detachment from its consequences, rendering them far away. Do we feel less responsible for what's happening so far? Perhaps the contrary. When something goes wrong on a distant server, what we feel is the helplessness of something being out of reach.
It's not surprising that technologies developed within army still talk the army language. But being so un-surprising, words and the worlds they carry along sneak into our worldviews, becoming normal, natural, invisible. Becoming just the way the world is, justifying and reinforcing the separation between user and developer, server and served, etc.
Looking at etymology, _deploy_ feels close to _display_. They share roots and gestures of making something visible and public, not to seclude far away, but to make accessible.
Let's see.
## NGINX Configuration
To deploy the padliography on a server, and make it accessible from a web browser, it's necessary to configure some ports to make the communication between the application and the world possible.
## License
This Padliography was distilled with the help and within the context of XPUB, 2022.

Loading…
Cancel
Save