asyncio REST API Resource database
Project description
Introduction
Please read the detailed docs
This is the working project of the next generation Guillotina server based on asyncio.
Dependencies
python >= 3.6
postgresql >= 9.6
Quickstart
We use pip:
pip install guillotina
Run postgresql
If you don’t have a postgresql server to play with, you can run one easily with docker.
Download and start the docker container by running:
make run-postgres
Run the server
To run the server:
g
Then…
Or, better yet, use postman to start playing with API.
You can also navigate in your Guillotina server with its built-in web admin interface by visiting http://localhost:8080/+admin/.
Deploy on Heroku
Read more Guillotina-Heroku.
Getting started with development
Using pip(requires python > 3.6):
git clone git@github.com:plone/guillotina.git cd guillotina python -m venv . ./bin/pip install -r requirements.txt ./bin/pip install -e .[test]
Run tests
We’re using pytest:
./bin/pytest guillotina
and for test coverage:
./bin/pytest --cov=guillotina guillotina/
With file watcher…
./bin/ptw guillotina –runner=./bin/py.test
To run tests with cockroach db:
USE_COCKROACH=true ./bin/pytest guillotina
Default
Default root access can be done with AUTHORIZATION header : Basic root:root
Docker
You can also run Guillotina with Docker!
First, run postgresql:
docker run --rm \
-e POSTGRES_DB=guillotina \
-e POSTGRES_USER=guillotina \
-p 127.0.0.1:5432:5432 \
--name postgres \
postgres:9.6
Then, run guillotina:
docker run --rm -it \
--link=postgres -p 127.0.0.1:8080:8080 \
guillotina/guillotina:latest \
g -c '{"databases": [{"db": {"storage": "postgresql", "dsn": "postgres://guillotina:@postgres/guillotina"}}], "root_user": {"password": "root"}}'
This assumes you have a config.yaml in your current working directory
Chat
Join us to talk about Guillotina at https://gitter.im/plone/guillotina
CHANGELOG
4.8.4 (2019-06-06)
Fix aiohttp startup bug [vangheem]
propagate unique violation errors on deletion as they should not happen anymore unless db hasn’t been migrated [vangheem]
4.8.3 (2019-06-06)
Upgrade to aiohttp 3.5.0 [vangheem]
4.8.2 (2019-05-28)
Fix bug where non-async object subscribers were getting called twice [vangheem]
4.8.2 (unreleased)
Nothing changed yet.
4.8.1 (2019-05-25)
Improve startup speed by not using glogger for startup code [vangheem]
Support zope.Interface inheritance in schema.Object [masipcat]
4.8.0 (2019-05-13)
get_object_by_oid now raises KeyError since it provided unsafe behavior when used with tombstoned objects [vangheem]
4.7.8 (2019-05-06)
Fix potential memory leak in security lookup cache [vangheem]
Fix security policy cache lookup to distinguish between types of cached decisions for parent vs top level object [vangheem]
4.7.7 (2019-05-01)
Fix json schema definitions and provide get_schema_validator utility [vangheem]
Fix managed_transaction context manager to correctly adopt parent transaction along with new transaction objects [vangheem]
4.7.6 (2019-04-28)
Provide connection_settings on the request object with tests.utils.get_container [vangheem]
4.7.5 (2019-04-27)
Fix command cleanup procedure to correctly cleanup asyncio tasks for commands [vangheem]
4.7.4 (2019-04-26)
use execute utility for index future
4.7.3 (2019-04-26)
Fix missing indexer [vangheem]
4.7.2 (2019-04-26)
Provide request_indexer setting to be able to override how we handle indexing data [vangheem]
Provide connection_settings on the request object with tests.utils.get_container [vangheem]
4.7.1 (2019-04-26)
Update postgresql constraint to also not allow having parent id same as zoid [vangheem]
Do not allow moving content into itself [vangheem]
4.7.0 (2019-04-16)
Remove IBeforeFieldModified event and replace with IBeforeObjectModifiedEvent [vangheem]
4.6.3 (2019-04-16)
Proper ContentAPI login to define user [bloodbare]
Util function to get a database object [bloodbare]
PyYaml 5.1 upgrade version [bloodbare]
Add async feature on patch operation set [bloodbare]
4.6.2 (2019-04-12)
enable the option to define specific transaction manager for each database [bloodbare]
4.6.1 (2019-04-12)
check for trashed parent id with get_object_by_oid to make sure object has not been tombstoned for deletion. [vangheem]
Do not allow bad logging config cause guillotina to fail to start [vangheem]
4.6.0 (2019-04-09)
Fixes:
Fix potential configuration conflict errors when sub-packages are used as unique applications [vangheem]
New:
Remove dependency on aioconsole and move to ipython for shell support [vangheem]
Added Heroku deploy button [karannaoh]
Start to improve the docker setup [svx]
4.5.13 (2019-04-04)
Provide api.container.create_container function [vangheem]
Fix docker build [vangheem]
…
You are seeing a truncated changelog.
You can read the changelog file for a complete list.
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for guillotina-4.8.4-py3-none-any.whl
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 3648708386919d8dde181a18f0760e6ed9109c9ebdaa29496f6f58a146caa818 |
|
| MD5 | 82052ad98cc4027730d1bf83a09abe19 |
|
| BLAKE2b-256 | db0489c0594c1f0faaaabd5afb7e3226eef435ba6a3b5eedde627e4a741088e4 |
