nu_lpw_final
MLOps Lab Practical Work scenario file generator and reference package.
Generate complete, runnable source code, Dockerfiles, docker-compose setups, configs, and models for any MLOps practical scenario directly into your working directory with a single function call.
Installation
pip install nu_lpw_final
Quick Start
from nu_lpw_final import mlops as numpy
# View all practical scenarios and function mappings
numpy.doc()
# Generate all files for Docker Scenario 7 in current directory
numpy.p3s7()
# Or generate files into a specific folder
numpy.p3s7("my_scenario7_folder")
Scenarios Index
Practical 1: Git Restore Scenarios
| Function | Focus |
|---|---|
p1s1() |
Baseline: restore right after commit (no-op) |
p1s2() |
Restore discards an unstaged edit |
p1s3() |
Restore only touches working tree, not index |
p1s4() |
Restore brings back deleted file and reverts edit (unstaged) |
p1s5() |
Staged edit + deleted file (divergent index & worktree) |
p1s6() |
Deleted file is re-added (staged deletion) |
p1s7() |
Both changes staged together |
p1s8() |
Restoring from an older commit after deletion (untracked) |
p1s9() |
Staged resurrected file removed on forward restore |
Practical 2: Deployment Scenarios
| Function | Scenario Description |
|---|---|
p2s1() |
Plain Flask Dev Server (no waitress, no nginx) |
p2s2() |
Waitress + Flask WSGI production server |
p2s3() |
nginx + Waitress (1 domain) + Flask |
p2s4() |
nginx (1 server block) + Waitress (2 domains, 1 app) + Flask |
p2s5() |
nginx (2 server blocks) + Waitress (2 domains, 1 app) |
p2s6() |
nginx (2 server blocks) + 2 separate Waitress instances |
p2s7() |
4 physical machines on LAN |
p2s8() |
HTTPS with self-signed certificate (OpenSSL) |
p2s9() |
HTTPS with mkcert (trusted local cert) |
p2s10() |
Serving static files directly via nginx |
p2s11() |
Load balancing + sticky sessions (ip_hash) |
p2_final() / p2s12() |
Multi-device demo (client + boston_backend + iris_backend) |
Practical 3: Docker Scenarios
| Function | Scenario Description |
|---|---|
p3s1() |
Dockerize a simple Flask webapp |
p3s2() |
Webapp + SQLite DB in one container |
p3s3() |
Webapp + MySQL in separate containers (custom network) |
p3s4() |
Separate containers + named volume (no compose) |
p3s5() |
Separate containers via docker-compose (no volume) |
p3s6() |
docker-compose + named volume (data persists) |
p3s7() |
Export/Import & Save/Load demo |
p3s8() |
Multi-Stage Build (Go binary in scratch image) |
License
MIT License. See LICENSE for details.
1 maintainer
Metadata
1 maintainer
Release files for nu-lpw-final 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| nu_lpw_final-0.0.1.tar.gz | 1.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nu_lpw_final-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 MB
Release files / nu_lpw_final-0.0.1.tar.gz
| Download URL | nu_lpw_final-0.0.1.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0923f2d60e50b14368535f643f53c21dbb78c3358469f52bb31a4ee11e339671
|
|
BLAKE2b-256 checksum How to use checksums |
8434199d9b71c3204d19d9b0a6187f609f72f056f4a7d64da0e4a1cd7ff488c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / nu_lpw_final-0.0.1-py3-none-any.whl
| Download URL | nu_lpw_final-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da4847ae9a63e6672b9fe10cbe6f5cf84aaad4304fe1d1a1abd3e3e1c86b3a55
|
|
BLAKE2b-256 checksum How to use checksums |
9a7cc75d16ab7b70784dddf5b86adfdb5603e024a54db5e4ac97b3788a564411
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for nu-lpw-final 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
