Skip to content
This repository was archived by the owner on Apr 25, 2023. It is now read-only.

[WIP] Add docker development environment#424

Open
doodyparizada wants to merge 1 commit into
hasadna:masterfrom
doodyparizada:doody/development_docker
Open

[WIP] Add docker development environment#424
doodyparizada wants to merge 1 commit into
hasadna:masterfrom
doodyparizada:doody/development_docker

Conversation

@doodyparizada

Copy link
Copy Markdown

run docker-compose up and you have a full development environment in docker.

@oryband

There is also an automated build on docker hub: https://hub.docker.com/r/doodyparizada/open-knesset/

@noamelf

noamelf commented Nov 17, 2015

Copy link
Copy Markdown

So cool!
On Nov 17, 2015 10:19 PM, "Doody Parizada" notifications@github.com wrote:

run docker-compose up and you have a full development environment in
docker.

@oryband https://github.com/oryband

You can view, comment on, or merge this pull request online at:

#424
Commit Summary

  • Add docker development environment

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#424.

Comment thread Dockerfile Outdated

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MAINTAINER Doody Parizada <doody.parizada @ gmail.com>

@oryband

oryband commented Nov 18, 2015

Copy link
Copy Markdown

sorry for being strict, this is the first introduction to docker in hasadna so we better get this right

@doodyparizada doodyparizada force-pushed the doody/development_docker branch from d95c712 to 99e87de Compare November 23, 2015 17:25
@doodyparizada doodyparizada force-pushed the doody/development_docker branch from 99e87de to 2bb1e11 Compare November 23, 2015 17:29
Comment thread Dockerfile

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • db should be in /opt/knesset - so users can change it
  • download of dev.db should be done only if it doesn't already exist
  • should be done in entrypoint

@habeanf

habeanf commented Nov 25, 2015

Copy link
Copy Markdown
Member

@oryband While we're here, can we get the docker environment to use postgres instead of sqlite? We've been wanting to be pg-only for a while, its a bit of a headache to support both. I can help with the pg setup next week.

@noamelf

noamelf commented Nov 25, 2015

Copy link
Copy Markdown

Did you encounter any problems with sqlite?

On Wed, Nov 25, 2015 at 12:01 PM, Amir More notifications@github.com
wrote:

@oryband https://github.com/oryband While we're here, can we get the
docker environment to use postgres instead of sqlite? We've been wanting to
be pg-only for a while, its a bit of a headache to support both. I can help
with the pg setup next week.


Reply to this email directly or view it on GitHub
#424 (comment).

,Noam Elfanbaum
972-54-555-1680+

@habeanf

habeanf commented Nov 25, 2015

Copy link
Copy Markdown
Member

It's not that I encountered problems, as much as it requires some code to be written twice, so for some parts of oknesset the developer already needs to install postgres anyhow.
Eventually, we'll want to rely on more of postgres' capabilities for performance/efficiency (e.g. analytic/window functions, non-trivial indexes, partitioning, etc). Historically we enabled sqlite for ease of development and environment setup. If we have a docker setup, we might as well have it run on postgres and save the extra headache.

@noamelf

noamelf commented Nov 25, 2015

Copy link
Copy Markdown

That's a good example you sent!
Cool, I like the idea.

On Wed, Nov 25, 2015 at 12:40 PM, Amir More notifications@github.com
wrote:

It's not that I encountered problems, as much as it requires some code to
be written twice
https://github.com/hasadna/Open-Knesset/blob/master/agendas/models.py#L51,
so for some parts of the oknesset the developer already needs to install
postgres anyhow.
Eventually, we'll want to rely on more of postgres' capabilities for
performance/efficiency (e.g. analytic/window functions, non-trivial
indexes, partitioning, etc). Historically we enabled sqlite for ease of
development and environment setup. If we have a docker setup, we might as
well have it run on postgres and save the extra headache.


Reply to this email directly or view it on GitHub
#424 (comment).

,Noam Elfanbaum
972-54-555-1680+

@oryband

oryband commented Nov 25, 2015

Copy link
Copy Markdown

@habeanf

@oryband While we're here, can we get the docker environment to use postgres instead of sqlite? We've been wanting to be pg-only for a while, its a bit of a headache to support both. I can help with the pg setup next week.

you should probably use a stub postgres docker image, and docker-compose with fixtures. this will allow to connect an ok and postgres images together easily. @doodyparizada can help, i guess.

Comment thread Dockerfile

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not vivid?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants