Tomasz Wójcik tomwojcik

## python_environment_setup.md

      
              1 file
            
          
              34 forks
            
          
              18 comments
            
          
              142 stars
            
          
                wronk
                / python_environment_setup.md
            
            
              Last active
              June 21, 2024 04:52
            
              
                Setting up your python development environment (with pyenv, virtualenv, and virtualenvwrapper)
              
          
    Overview of Python Virtual Environments

This guide is targetted at intermediate or expert users who want low-level control over their Python environments.
When you're working on multiple coding projects, you might want a couple different version of Python and/or modules installed. This helps keep each workflow in its own sandbox instead of trying to juggle multiple projects (each with different dependencies) on your system's version of Python. The guide here covers one way to handle multiple Python versions and Python environments on your own (i.e., without a package manager like conda). See the Using the workflow section to view the end result.

  
  h/t @sharkinsspatial for linking me to the perfect cartoon

  
## mongodb-ssl.sh
#!/bin/sh

# Generate self signed root CA cert
openssl req -nodes -x509 -newkey rsa:2048 -keyout ca.key -out ca.crt -subj "/C=AU/ST=NSW/L=Sydney/O=MongoDB/OU=root/CN=`hostname -f`/emailAddress=kevinadi@mongodb.com"


# Generate server cert to be signed
openssl req -nodes -newkey rsa:2048 -keyout server.key -out server.csr -subj "/C=AU/ST=NSW/L=Sydney/O=MongoDB/OU=server/CN=`hostname -f`/emailAddress=kevinadi@mongodb.com"

# Sign the server cert

## sane-caching.nginx.conf
# Sample Nginx config with sane caching settings for modern web development
#
# Motivation:
# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
# and juicy version of your assets available.
# At some point, however, you want to show your work to testers, your boss or your client.
# After you implemented and deployed their feedback, they reload the testing page – and report
# the exact same issues as before! What happened? Of course, they did not have developer tools
# open, and of course, they did not empty their caches before navigating to your site.

## aliases
# ------------------------------------
# Docker alias and function
# ------------------------------------

# Get latest container ID
alias dl="docker ps -l -q"

# Get container process
alias dps="docker ps"

## models_committed.py
from sqlalchemy import create_engine, event, orm
from sqlalchemy.orm import sessionmaker
from sqlalchemy.orm.session import Session as SessionBase, object_session
from sqlalchemy.event.api import listen

# The following adds delete, insert, and update events after successful commits.
# SQLAlchemy provides only events after flushes, but not after commits.
# The classes are adapted from Flask-SQLAlchemy.
# see also https://stackoverflow.com/a/12026787/60982
	#!/bin/sh

	# Generate self signed root CA cert
	openssl req -nodes -x509 -newkey rsa:2048 -keyout ca.key -out ca.crt -subj "/C=AU/ST=NSW/L=Sydney/O=MongoDB/OU=root/CN=`hostname -f`/emailAddress=kevinadi@mongodb.com"


	# Generate server cert to be signed
	openssl req -nodes -newkey rsa:2048 -keyout server.key -out server.csr -subj "/C=AU/ST=NSW/L=Sydney/O=MongoDB/OU=server/CN=`hostname -f`/emailAddress=kevinadi@mongodb.com"

	# Sign the server cert
	# Sample Nginx config with sane caching settings for modern web development
	#
	# Motivation:
	# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
	# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
	# and juicy version of your assets available.
	# At some point, however, you want to show your work to testers, your boss or your client.
	# After you implemented and deployed their feedback, they reload the testing page – and report
	# the exact same issues as before! What happened? Of course, they did not have developer tools
	# open, and of course, they did not empty their caches before navigating to your site.
	# ------------------------------------
	# Docker alias and function
	# ------------------------------------

	# Get latest container ID
	alias dl="docker ps -l -q"

	# Get container process
	alias dps="docker ps"
	from sqlalchemy import create_engine, event, orm
	from sqlalchemy.orm import sessionmaker
	from sqlalchemy.orm.session import Session as SessionBase, object_session
	from sqlalchemy.event.api import listen

	# The following adds delete, insert, and update events after successful commits.
	# SQLAlchemy provides only events after flushes, but not after commits.
	# The classes are adapted from Flask-SQLAlchemy.
	# see also https://stackoverflow.com/a/12026787/60982