Skip to content

Commit

Permalink
Basic Kinto Example
Browse files Browse the repository at this point in the history
  • Loading branch information
Bill Prin committed Feb 17, 2016
1 parent 2615c04 commit 9b97c28
Show file tree
Hide file tree
Showing 4 changed files with 27 additions and 7 deletions.
8 changes: 4 additions & 4 deletions managed_vms/kinto/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -27,16 +27,16 @@ RUN virtualenv /env
# the context of the virtualenv and will have access to its dependencies.
ENV VIRTUAL_ENV /env
ENV PATH /env/bin:$PATH

# Kinto config file
ENV KINTO_INI /etc/kinto/kinto.ini

# Install dependencies.
ADD requirements.txt /app/requirements.txt
RUN pip install -r /app/requirements.txt
#Create Kinto config file and replace 8888 with 8080
RUN kinto --ini $KINTO_INI --backend=memory init && sed -i 's/8888/8080/g' $KINTO_INI

# Add application code.
ADD . /app

# Use Gunicorn to serve the application.
# Run the Kinto kickoff command
CMD kinto --ini $KINTO_INI migrate && kinto --ini $KINTO_INI start

18 changes: 18 additions & 0 deletions managed_vms/kinto/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Kinto Example

This is a basic example of running Mozillas [Kinto](https://github.com/Kinto/kinto/blob/master/docs/index.rst)
on Managed VMs. Kinto provides a framework to sync JSON data across many devices and provide push notifications.
Thius example uses a custom runtime to install Kinto and edit the config to run it on port 8080, which is the port that
the base Docker image is expecting.

Since Kinto is being imported as a Python library and run as-is, no additional code is necessary.

Note that this is using Kinto's basic in-memory backend. As such, the instances are tied to 1. A production
version of Kinto would use a PostgreSQL database and Redis cluster, which would allow scaling to many instances.

If you are interested in seeing this example expanded to use PostgreSQL, you can file an Issue on the Issue
Tracker, or submit a Pull Request if you've accomplished it yourself.




6 changes: 4 additions & 2 deletions managed_vms/kinto/app.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -17,14 +17,16 @@

runtime: custom
vm: true
health_check:
enable_health_check: False

# Kinto does not respond 404 to /_ah/health (sends a redirect)
vm_health_check:
enable_health_check: False

# Using an in-memory backend so lock instances to 1
manual_scaling:
instances: 1


# Temporary setting to keep gcloud from uploading the virtualenv
skip_files:
- ^v?env$
2 changes: 1 addition & 1 deletion managed_vms/kinto/requirements.txt
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
gunicorn==19.4.5
oauth2client==1.5.2
kinto
kinto==1.11.2

0 comments on commit 9b97c28

Please sign in to comment.