[](http://badge.fury.io/py/django-sae)
用于新浪云平台SAE
### 扩展命令
* compress_site_packages:压缩 site_packages
* upgrade_requirements:更新requirements.txt中所有依赖的库
* sae_migrate:切换到SAE数据库,并进行migrate操作
使用sae_migrate等与数据库相关的扩展命令时,请手工获取SAE数据库的相关常数,如MYSQL_DB、MYSQL_USER、MYSQL_PASS等,并在settings中对DATABASES进行修改。
### 数据库
如需数据库读写操作分离,请在settings中进行设置(示例如下):
```python
from sae.const import MYSQL_HOST, MYSQL_HOST_S, MYSQL_PORT, MYSQL_USER, MYSQL_PASS, MYSQL_DB
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': MYSQL_DB,
'USER': MYSQL_USER,
'PASSWORD': MYSQL_PASS,
'HOST': MYSQL_HOST,
'PORT': MYSQL_PORT,
'OPTIONS': {'init_command': "SET storage_engine=MYISAM;"},
},
'slave': {
'ENGINE': 'django.db.backends.mysql',
'NAME': MYSQL_DB,
'USER': MYSQL_USER,
'PASSWORD': MYSQL_PASS,
'HOST': MYSQL_HOST_S,
'PORT': MYSQL_PORT,
'OPTIONS': {'init_command': "SET storage_engine=MYISAM;"},
},
}
DATABASE_ROUTERS = ['django_sae.db.routers.MasterSlaveRouter']
```
### 缓存
使用 SAE Memcache 服务时,请在settings中进行设置(示例如下):
```python
CACHES={
'default': {
'BACKEND': 'django_sae.cache.backends.SaePyLibMCCache',
}
}
```
### 日志
使用日志过滤器RequireInSAE和RequireNotInSAE时,请在settings中进行设置(示例如下):
```python
LOGGING = {
'version': 1,
'disable_existing_loggers': True,
'filters': {
'require_in_sae': {
'()': 'django_sae.utils.log.RequireInSAE',
},
'require_not_in_sae': {
'()': 'django_sae.utils.log.RequireNotInSAE',
},
},
'handlers': {
'console': {
'level': 'DEBUG',
'class': 'logging.StreamHandler',
'filters': [ 'require_in_sae'],
},
},
'loggers': {
'django': {
'handlers': ['console'],
},
}
}
```
.. :changelog:
Release History
---------------
0.2.1 (2014-06-27)
++++++++++++++++++
- 删除模块:http(Django1.7已支持JsonResponse)
- 修改设置:LANGUAGE_CODE为zh-hans(zh-cn从1.9版本后弃用)
0.2.0 (2014-05-17)
++++++++++++++++++
- 修改扩展命令:sae_migrate(使用Django1.7自带的migrate命令)
- 删除扩展命令:sae_syncdb(Django1.7已移除syncdb命令)
0.1.23 (2014-03-21)
++++++++++++++++++
- 添加日志过滤器:RequireInSAE,RequireNotInSAE
0.1.21 (2014-03-20)
++++++++++++++++++
- 删除扩展命令:sae_schemamigration(因为此命令不需要链接SAE数据库)
0.1.18 (2014-03-19)
++++++++++++++++++
- 添加扩展命令:upgrade_requirements
0.1.13 (2014-03-18)
++++++++++++++++++
- 重命名扩展命令: updatepackages -> compress_site_packages,
- 添加扩展命令:sae_migrate, sae_schemamigration, sae_syncdb
0.1.11 (2014-03-17)
++++++++++++++++++
- commands(扩展命令): updatepackages(更新依赖库并压缩为site-packages.zip)
0.1.1 (2014-03-16)
++++++++++++++++++
- patches: 自动设置
- conf: SAE平台的默认设置
0.1.0 (2014-03-15)
++++++++++++++++++
- db: 通用模型和读写分离
- cache: 缓存模型
- utils: 时间戳模块和装饰模块
- tasks: 用于执行任务
Metadata
Release files for django-sae 0.2.1
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-sae-0.2.1.zip | 31.2 kB | Without provenance | Details for django-sae-0.2.1.zip |
Release files / django-sae-0.2.1.zip
| Download URL | django-sae-0.2.1.zip |
|---|---|
| Size | 31.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d32d651c0a7f3d6b6c495d16e2f512a137ffa5628428c8dd650e0191e52ce076
|
|
BLAKE2b-256 checksum How to use checksums |
5a6d2518a9df74b050297f950ab6eb1ba1f75d6a364924495a465eb2ab5ab07a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-sae 0.2.1
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.