Latest Articles
When attempting to create a Python 3.10 environment using `pipenv install` and encountering the error "RuntimeError: location not created nor specified," it may be due to using the pipenv installed in a Python 3.9 environment. To resolve this issue, you should install pipenv in the Python 3.10 environment.
This article provides key points to check the configuration in cases where you are using the Nginx Ingress Controller with Kubernetes and Uwsgi for the application server within the Pod, to prevent slow response services from timing out. If these configurations are not extended, it could result in 502 or 504 errors.
When using version locking systems like Pipenv to set up a Python environment with an Alpine Linux Docker image, installations often encounter difficulties. If installing `cryptography` via Rust is unsuccessful (or too slow and thus undesirable), it is more effective to install `cryptography` via `apk` rather than through Pipenv.
I attempted to retrieve the source global IP address from HTTP requests through Kubernetes Ingress, but I ended up obtaining the IP address of Kubernetes' local network, which did not work as intended. After switching Kubernetes to MicroK8s and using its built-in Ingress controller, I was able to successfully retrieve the global remote IP address. This is a note on that experience.