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

Add Dynflow development and production mode #3422

Merged
merged 0 commits into from
Dec 9, 2013

Conversation

pitr-ch
Copy link
Member

@pitr-ch pitr-ch commented Nov 22, 2013

If Katello.config.dynflow.remote is set to true Dynflow runs in
Delayed::Worker (rake jobs:work) communicating over socket with Katello’s
web server(s).

If Katello.config.dynflow.remote is set to false Dynflow runs inside
Katello’s web server.

By default remote is set to true in production and to false in
development.

@@ -139,7 +139,8 @@ def database_configuration
app.routes.append{match '/api*a', :to => 'api/v1/errors#render_404'}
app.routes.append{match '*a', :to => 'errors#routing'}

Orchestrate.eager_load!
Orchestrate::DelayedParasite.load
Copy link
Member

Choose a reason for hiding this comment

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

I don't like the Parasite name: it's sounds way to negative to me, what about DelayedWorkerInjector?

Copy link
Member Author

Choose a reason for hiding this comment

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

It supposed to be funny. It's temporary code anyway :) But ok if it's too negative I'll change it, np.

@iNecas
Copy link
Member

iNecas commented Nov 22, 2013

ACK except the parasite thing :)

@pitr-ch
Copy link
Member Author

pitr-ch commented Nov 27, 2013

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