There are many deployment scenarios with Python web applications. Without diving into all the options I’ll suppose part of your deployment is utilizing Paste Deployment (http://pythonpaste.org/deploy/) . To test and develop your application you use “paster serve some_name.ini”. Now to setup the application so that it runs after log off or restart you need a customized Windows service.
There are a couple of recipes around to achieve this but, you have to copy and paste some code and hardcode the name and config file into it. I’ve put together a little tool which helps creating windows services, based on arbitrary configuration parameters.
1. install the tool
easy_install wsgisvc
This adds the wsgisvc.exe into your scripts directory. Python extensions for Windows are a prerequisite. If you don’t have them download (http://sourceforge.net/project/showfiles.php?group_id=78018) them and install.
2. Extend your *.ini file
with a [winservice] section. The list of options you can use:
svc_name
svc_display_name
svc_description
log_file
virtual_env
If you don’t use the [winservice] section, the configuration file will be used as service name. Sensible defaults will be made up for the rest.
3. Install the service
wsgisvc -c some_name.ini install
This adds the service “svc1” to your system. You can check it out under display name “svc1 Paste Service” through Administrative Tools -> Services. To start the service you can either use that or command line:
wsgisvc -c some_name.ini start
And the last thing, to list display names of all installed Paste services:
wsgisvc list
Source code of the package
http://bitbucket.org/tibor_arpas/wsgisvc/
Any feedback or corrections are appreciated.
1 maintainer
Metadata
1 maintainer
Release files for wsgisvc 0.8.2.0
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 | |
|---|---|---|---|---|
| wsgisvc-0.8.2.0.zip | 14.1 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wsgisvc-0.8.2.0-py2.6.egg | Legacy Egg format | - | - | Details |
| wsgisvc-0.8.2.0-py2.5.egg | Legacy Egg format | - | - | Details |
Total release size: 37.7 kB
Release files / wsgisvc-0.8.2.0.zip
| Download URL | wsgisvc-0.8.2.0.zip |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e53df62616cc043ab15388529a0b3e0df398291dd471b469afb4fbe3dd15647
|
|
BLAKE2b-256 checksum How to use checksums |
b428abd24beee0da3cc2b3a38e1488bc24503fc712616cc97117ab9a013f06c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / wsgisvc-0.8.2.0-py2.6.egg
| Download URL | wsgisvc-0.8.2.0-py2.6.egg |
|---|---|
| Size | 11.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
98e49d470387beb9f223c85bcca0525d1b43172b3b499b2cdc77bdfa74dfe1e5
|
|
BLAKE2b-256 checksum How to use checksums |
7e4f9d67bb62a29bc3f6cadb41fc0f225fd08766959f2b6ea36f80c3a892dd92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / wsgisvc-0.8.2.0-py2.5.egg
| Download URL | wsgisvc-0.8.2.0-py2.5.egg |
|---|---|
| Size | 11.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
c6c0ba6b1b7d7a390b382292b9c1702e67916ef00783790e8196eeddcdc6368d
|
|
BLAKE2b-256 checksum How to use checksums |
3c91df6097028616d509010de114d8252b500a594f370358a08ac6fe9dbc6557
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wsgisvc 0.8.2.0
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.
