diff --git a/content/blog/offlinepip.md b/content/blog/offlinepip.md
new file mode 100644
index 0000000..1e69ff0
--- /dev/null
+++ b/content/blog/offlinepip.md
@@ -0,0 +1,61 @@
+---
+title: "Offline Pip Packages"
+date: 2020-01-20T23:11:05-05:00
+draft: false
+images: []
+---
+
+There are a few reasons I can think of to have offline pip packages:
+
+- A package isn't able to compile on a friend's computer since they don't have the million linear algebra libraries that `numpy` /`scipy` require.
+- You want to archive everything to run a piece of software
+- You want to control the packages available to a closed network
+
+Regardless, to my surprise, setting up a repository of python wheels doesn't take many steps. 
+
+## Setup
+
+First I would recommend that you setup a virtual environment. Either through [pyenv](https://brandonrozek.com/blog/pyenv/) or [python-virtualenv](https://brandonrozek.com/blog/virtualenv/).
+
+Then, install whatever packages you would like. Let us use tensorflow as an example:
+
+```bash
+pip install tensorflow
+```
+
+After you install all the packages you want to be available, freeze the requirements to a text file.
+
+```bash
+pip freeze > requirements.txt
+```
+
+Install the wheel package to make the binary wheels.
+
+```bash
+pip install wheel
+```
+
+Create the wheels
+
+```bash
+pip wheel --wheel-dir=wheels -r requirements.txt
+```
+
+With this you have a whole repository of wheels under the wheels folder!
+
+## Client Side
+
+Now you can get [all fancy with your deployment](https://realpython.com/offline-python-deployments-with-docker/#deploy), though I just assumed that the files were mounted in some shared folder.
+
+The client can install all the wheels
+
+```bash
+pip install /path/to/wheels/*
+```
+
+Or they can just install the packages they want
+
+```bash
+pip install --no-index -f /path/to/wheels/wheels package_name
+```
+