Autoenv VS flask_for_startups

the way I manage (2) is with a kind of DIY pipenv system i've come up with. i have a tool installed in my terminal called autoenv. when i navigate to a new directory, if there's a .env file in it, autoenv executes it. that's basically all autoenv does. I have a .env in my home folder that, among other things, activates my "master" venv. when I create a new project that I want to have its own venv, I just add a .env file to that folder to activate it. otherwise, the master venv is active whenever I roam around my filesystem, functionally serving as a default environment i reuse.

Inspired by autoenv, pyautoenv hooks into the cd command in your shell and will automatically activate a poetry or venv Python environment if that environment is defined in the directory you're cd-ing into. Zsh, Bash, and PowerShell are supported.

There is an autoenv tool you can use to automatically activate a python virtualenv when you cd into a directory but it’s a little annoying to set up https://github.com/hyperupcall/autoenv

But IMO the best solution by far is to use autoenv. There is autoenv for bash and autoenv for zsh.

Ref

Example of .flaskenv Example of config file

If you want to see the full example, here's my repo

Here's the flask repo that I used. The repo doesn't have the specific ML bits, but all you have to do is:

I use this structure: https://github.com/nuvic/flask_for_startups

@app.teardown_appcontext def shutdown_session(response_or_exc): db.remove() Ref

for reference: https://github.com/nuvic/flask_for_startups/blob/main/app/permissions.py

I also made a repo https://github.com/nuvic/flask_for_startups showing some of the patterns I found useful while working in startups.

Here's my conftest setup for reference (repo here: