Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker instructions #1

Open
pjebs opened this issue Jul 6, 2016 · 2 comments
Open

Docker instructions #1

pjebs opened this issue Jul 6, 2016 · 2 comments

Comments

@pjebs
Copy link

pjebs commented Jul 6, 2016

Hi @jekil
I'm really impressed by your product and I'm excited to use it.
I do have some questions/requests however:

  • Can you put docker instructions/ configuration information on the documentation page? ( I intend to use docker)
  • I saw that ghiro uses ( MySQL, PostgreSQL and SQLite3) and MongoDB for different purposes.
    I was wondering what the different purposes were and why 2 different types of databases were definitely required?
  • My use case is to use ghiro as a queue worker. i.e. put some images in queue, get ghiro to process them, store results somewhere and set a flag saying it's done.
    I was going to use beanstalkd for the queue. I noticed that ghiro has a queue built in. What does it use and how can I interact with it?

*For my use case, can I get rid of the "web interface"?

  • In the documentation there is a section called: "Running Ghiro as service". That shows how to set up ghiro as a (presumably) REST API service???
    Is there a way to get a docker container to run Ghiro as a service. I don't necessarily require a "full web service" since it's not meant for the public to use. I really only want to put images and some data into a queue, get ghiro to process it and then save the results somewhere and then repeat process. Obviously you can do it as a web service, but since it's only going to be used by my other backend components, it seems "overkill"
@pjebs
Copy link
Author

pjebs commented Sep 16, 2016

@jekil Can you please address this?

@jekil
Copy link
Member

jekil commented Sep 20, 2016

Sorry for the late reply.

The docker container is still under development, this is why it isn't documented yet.
The choice about DB is expleined in the documentation.
To understand how the queue works you should look at the code, in the next release it will be improved.
To get rid of it just don't run it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants