Congo
Django Congo contains many useful tools for faster and more efficient Django application developing.
Requirements
Djanog Congo requires Python 2.7 and Django 1.10 or newer.
Installation
To install congo, run the following command inside this directory::
python setup.py install
You can also install the package with a symlink, so that changes to the source files will be immediately available to other users of the package on your system::
python setup.py develop
If you're using pip:
pip install django-congo
You can also install directly from GIT repo:
pip install git+https://gitlab.com/integree/internal/congo3.git
or, if you need install from branch:
pip install git+https://gitlab.com/integree/internal/congo3.git@branch-name
Project download
Run console and cd to your working directory, eg. D:\serwer\www. Create a project dir and clone project from repo:
cd \serwer\www
mkdir congo
git clone https://gitlab.com/integree/internal/congo3.git congo
Project development
Before you start verify that packages bellow are installed:
- Python 2.7
- Microsoft Visual C++ Compiler for Python 2.7
- MySQL 5.6 or 5.7 x64
- MySQL Connector C 6.0.2
- Git for Windows
- GetText
- Ruby & Compass
- Node & Bower
- virtualenv
- virtualenvwrapper-win
Verify that WORKON_HOME points to virtual env home directory
set WORKON_HOME
Make virtual env
virtualenv -p "c:\Python27\python.exe" "%WORKON_HOME%\congo"
workon congo
Verify Python version is 2.7.x
python -V
Upgrade PIP and verify it's version
python -m pip install --upgrade pip
pip -V
Set project dir
cd \serwer\www\congo
setprojectdir .
Install requirements
pip install -r env\requirements.txt
Run Django migrations
migrate.bat
Run HTTP server
runserver.bat
Authors
Made with love by Integree Bussines Solutions from Warsaw, Poland
Metadata
Release files for django-congo 2.3.2
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 | Actions |
|---|---|---|---|---|
| django-congo-2.3.2.tar.gz | 1.3 MB | Without provenance | Details for django-congo-2.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_congo-2.3.2-py2-none-any.whl | Python 2 | none | any | Details for django_congo-2.3.2-py2-none-any.whl |
Total release size: 2.8 MB
Release files / django-congo-2.3.2.tar.gz
| Download URL | django-congo-2.3.2.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a814da03927ef16c12c831813f6cf3f61ce74df720350495d81b610245e65fed
|
|
BLAKE2b-256 checksum How to use checksums |
fe86136015191dc118fd9a510d9415835f352337b36717272ecd87fb879943a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.15
|
Release files / django_congo-2.3.2-py2-none-any.whl
| Download URL | django_congo-2.3.2-py2-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
9f719a2bb7f36ed9a3d11d36d041d73a48c86bc8b7929661823bd528c039f889
|
|
BLAKE2b-256 checksum How to use checksums |
88cb36e4165257d140bc1a4e75e6c079541c704290fbf876052a717b01f5b03b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.15
|
Security for django-congo 2.3.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.