You're Invited:Meet the Socket Team at RSAC and BSidesSF 2026, March 23–26.RSVP →
envdir
Artifacts are distributable versions of a package. It typically includes the source code and metadata
Advanced tools
envdir - pypi Package Compare versions
| Metadata-Version: 1.1 | ||
| Name: envdir | ||
| Version: 0.2 | ||
| Version: 0.2.1 | ||
| Summary: A Python port of daemontools' envdir. | ||
@@ -18,9 +18,58 @@ Home-page: http://github.com/jezdez/envdir | ||
| What? | ||
| ----- | ||
| envdir runs another program with a modified environment according to files | ||
| in a specified directory. | ||
| So for example, imagine a software you want to run on a server but don't | ||
| want to leave certain configuration variables embedded in the program's source | ||
| code. A common pattern to solve this problem is to use environment variables | ||
| to separate configuration from code. | ||
| envdir allows you to set a series of environment variables at once to simplify | ||
| maintaing complicated environments, for example in wich you have multiple sets | ||
| of those configuration variables depending on the infrastructure you run your | ||
| program on (e.g. Windows vs. Linux, Staging vs. Production, Old system vs. | ||
| New system etc). | ||
| Let's have a look at a typical envdir:: | ||
| $ tree mysite_env/ | ||
| mysite_env/ | ||
| ├── DJANGO_SETTINGS_MODULE | ||
| ├── MYSITE_DEBUG | ||
| ├── MYSITE_DEPLOY_DIR | ||
| ├── MYSITE_SECRET_KEY | ||
| └── PYTHONSTARTUP | ||
| 0 directories, 3 files | ||
| $ cat mysite_env/DJANGO_SETTINGS_MODULE | ||
| mysite.settings | ||
| $ | ||
| As you can see each file has a capitalized name and contains the value of the | ||
| environment variable to set when running your program. To use it, simply | ||
| prefix the call to your program with envdir:: | ||
| $ envdir mysite_env python manage.py runserver | ||
| That's it, nothing more and nothing less. The way you structure your envdir | ||
| is left to you but can easily match your configuration requirements and | ||
| integrate with other configuration systems. envdirs contain just files after | ||
| all. | ||
| An interesting summary about why it's good to store configuration values in | ||
| environment variables can be found on the 12factor_ site. | ||
| .. _12factor: http://12factor.net/config | ||
| Why? | ||
| ---- | ||
| Because it's small enough that it shouldn't be tied to a bigger | ||
| software distribution like daemontools. Also, this Python port | ||
| can easily be used on Windows, not only UNIX systems. | ||
| Because envdir small enough that it shouldn't be tied to a bigger | ||
| software distribution like daemontools that requires a compiler. | ||
| Also, this Python port can easily be used on Windows, not only UNIX systems. | ||
| Installation | ||
@@ -40,5 +89,10 @@ ------------ | ||
| Command line | ||
| ^^^^^^^^^^^^ | ||
| Quoting the envdir documentation: | ||
| envdir runs another program with environment modified according to files in a specified directory. | ||
| envdir runs another program with environment modified according to files | ||
| in a specified directory. | ||
| Interface:: | ||
@@ -69,4 +123,7 @@ | ||
| To use envdir **in a Python file** (e.g. Django's ``manage.py``) you can use:: | ||
| Python | ||
| ^^^^^^ | ||
| To use envdir in a Python file (e.g. Django's ``manage.py``) you can use:: | ||
| import envdir | ||
@@ -96,2 +153,8 @@ envdir.read() | ||
| 0.2.1 (07/11/2013) | ||
| ^^^^^^^^^^^^^^^^^^ | ||
| * Fixed ``python -m envdir`` | ||
| * Extended README to better describe the purpose | ||
| 0.2 (07/10/2013) | ||
@@ -98,0 +161,0 @@ ^^^^^^^^^^^^^^^^ |
@@ -1,8 +0,3 @@ | ||
| import sys | ||
| from .__main__ import envdir, __version__ # noop | ||
| from .__main__ import envdir, main, __version__ # noop | ||
| read = envdir.read | ||
| def main(): | ||
| envdir.main(sys.argv[1:]) |
@@ -7,3 +7,3 @@ import glob | ||
| __version__ = '0.2' | ||
| __version__ = '0.2.1' | ||
@@ -90,1 +90,8 @@ | ||
| envdir = Envdir() | ||
| def main(): | ||
| envdir.main(sys.argv[1:]) | ||
| if __name__ == '__main__': | ||
| main() |
+69
-6
| Metadata-Version: 1.1 | ||
| Name: envdir | ||
| Version: 0.2 | ||
| Version: 0.2.1 | ||
| Summary: A Python port of daemontools' envdir. | ||
@@ -18,9 +18,58 @@ Home-page: http://github.com/jezdez/envdir | ||
| What? | ||
| ----- | ||
| envdir runs another program with a modified environment according to files | ||
| in a specified directory. | ||
| So for example, imagine a software you want to run on a server but don't | ||
| want to leave certain configuration variables embedded in the program's source | ||
| code. A common pattern to solve this problem is to use environment variables | ||
| to separate configuration from code. | ||
| envdir allows you to set a series of environment variables at once to simplify | ||
| maintaing complicated environments, for example in wich you have multiple sets | ||
| of those configuration variables depending on the infrastructure you run your | ||
| program on (e.g. Windows vs. Linux, Staging vs. Production, Old system vs. | ||
| New system etc). | ||
| Let's have a look at a typical envdir:: | ||
| $ tree mysite_env/ | ||
| mysite_env/ | ||
| ├── DJANGO_SETTINGS_MODULE | ||
| ├── MYSITE_DEBUG | ||
| ├── MYSITE_DEPLOY_DIR | ||
| ├── MYSITE_SECRET_KEY | ||
| └── PYTHONSTARTUP | ||
| 0 directories, 3 files | ||
| $ cat mysite_env/DJANGO_SETTINGS_MODULE | ||
| mysite.settings | ||
| $ | ||
| As you can see each file has a capitalized name and contains the value of the | ||
| environment variable to set when running your program. To use it, simply | ||
| prefix the call to your program with envdir:: | ||
| $ envdir mysite_env python manage.py runserver | ||
| That's it, nothing more and nothing less. The way you structure your envdir | ||
| is left to you but can easily match your configuration requirements and | ||
| integrate with other configuration systems. envdirs contain just files after | ||
| all. | ||
| An interesting summary about why it's good to store configuration values in | ||
| environment variables can be found on the 12factor_ site. | ||
| .. _12factor: http://12factor.net/config | ||
| Why? | ||
| ---- | ||
| Because it's small enough that it shouldn't be tied to a bigger | ||
| software distribution like daemontools. Also, this Python port | ||
| can easily be used on Windows, not only UNIX systems. | ||
| Because envdir small enough that it shouldn't be tied to a bigger | ||
| software distribution like daemontools that requires a compiler. | ||
| Also, this Python port can easily be used on Windows, not only UNIX systems. | ||
| Installation | ||
@@ -40,5 +89,10 @@ ------------ | ||
| Command line | ||
| ^^^^^^^^^^^^ | ||
| Quoting the envdir documentation: | ||
| envdir runs another program with environment modified according to files in a specified directory. | ||
| envdir runs another program with environment modified according to files | ||
| in a specified directory. | ||
| Interface:: | ||
@@ -69,4 +123,7 @@ | ||
| To use envdir **in a Python file** (e.g. Django's ``manage.py``) you can use:: | ||
| Python | ||
| ^^^^^^ | ||
| To use envdir in a Python file (e.g. Django's ``manage.py``) you can use:: | ||
| import envdir | ||
@@ -96,2 +153,8 @@ envdir.read() | ||
| 0.2.1 (07/11/2013) | ||
| ^^^^^^^^^^^^^^^^^^ | ||
| * Fixed ``python -m envdir`` | ||
| * Extended README to better describe the purpose | ||
| 0.2 (07/10/2013) | ||
@@ -98,0 +161,0 @@ ^^^^^^^^^^^^^^^^ |
+68
-5
@@ -10,9 +10,58 @@ envdir | ||
| What? | ||
| ----- | ||
| envdir runs another program with a modified environment according to files | ||
| in a specified directory. | ||
| So for example, imagine a software you want to run on a server but don't | ||
| want to leave certain configuration variables embedded in the program's source | ||
| code. A common pattern to solve this problem is to use environment variables | ||
| to separate configuration from code. | ||
| envdir allows you to set a series of environment variables at once to simplify | ||
| maintaing complicated environments, for example in wich you have multiple sets | ||
| of those configuration variables depending on the infrastructure you run your | ||
| program on (e.g. Windows vs. Linux, Staging vs. Production, Old system vs. | ||
| New system etc). | ||
| Let's have a look at a typical envdir:: | ||
| $ tree mysite_env/ | ||
| mysite_env/ | ||
| ├── DJANGO_SETTINGS_MODULE | ||
| ├── MYSITE_DEBUG | ||
| ├── MYSITE_DEPLOY_DIR | ||
| ├── MYSITE_SECRET_KEY | ||
| └── PYTHONSTARTUP | ||
| 0 directories, 3 files | ||
| $ cat mysite_env/DJANGO_SETTINGS_MODULE | ||
| mysite.settings | ||
| $ | ||
| As you can see each file has a capitalized name and contains the value of the | ||
| environment variable to set when running your program. To use it, simply | ||
| prefix the call to your program with envdir:: | ||
| $ envdir mysite_env python manage.py runserver | ||
| That's it, nothing more and nothing less. The way you structure your envdir | ||
| is left to you but can easily match your configuration requirements and | ||
| integrate with other configuration systems. envdirs contain just files after | ||
| all. | ||
| An interesting summary about why it's good to store configuration values in | ||
| environment variables can be found on the 12factor_ site. | ||
| .. _12factor: http://12factor.net/config | ||
| Why? | ||
| ---- | ||
| Because it's small enough that it shouldn't be tied to a bigger | ||
| software distribution like daemontools. Also, this Python port | ||
| can easily be used on Windows, not only UNIX systems. | ||
| Because envdir small enough that it shouldn't be tied to a bigger | ||
| software distribution like daemontools that requires a compiler. | ||
| Also, this Python port can easily be used on Windows, not only UNIX systems. | ||
| Installation | ||
@@ -32,5 +81,10 @@ ------------ | ||
| Command line | ||
| ^^^^^^^^^^^^ | ||
| Quoting the envdir documentation: | ||
| envdir runs another program with environment modified according to files in a specified directory. | ||
| envdir runs another program with environment modified according to files | ||
| in a specified directory. | ||
| Interface:: | ||
@@ -61,4 +115,7 @@ | ||
| To use envdir **in a Python file** (e.g. Django's ``manage.py``) you can use:: | ||
| Python | ||
| ^^^^^^ | ||
| To use envdir in a Python file (e.g. Django's ``manage.py``) you can use:: | ||
| import envdir | ||
@@ -88,2 +145,8 @@ envdir.read() | ||
| 0.2.1 (07/11/2013) | ||
| ^^^^^^^^^^^^^^^^^^ | ||
| * Fixed ``python -m envdir`` | ||
| * Extended README to better describe the purpose | ||
| 0.2 (07/10/2013) | ||
@@ -90,0 +153,0 @@ ^^^^^^^^^^^^^^^^ |
+1
-1
@@ -5,5 +5,5 @@ [wheel] | ||
| [egg_info] | ||
| tag_date = 0 | ||
| tag_svn_revision = 0 | ||
| tag_build = | ||
| tag_date = 0 | ||
Alert delta unavailable
Currently unable to show alert delta for PyPI packages.
Improved metrics
- Total package byte prevSize
23657
39.73%- Lines of code
123
0.82%