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

OpenShift support. #30

Closed
ghelleks opened this issue Mar 31, 2013 · 9 comments
Closed

OpenShift support. #30

ghelleks opened this issue Mar 31, 2013 · 9 comments

Comments

@ghelleks
Copy link

I added support for OpenShift on the "openshift" branch here:

http://github.com/ghelleks/huginn

It's kind of intrusive, so not ready for a formal pull request yet. In the meantime, using the branch is documented here:

https://github.com/cantino/huginn/wiki/Deployment-on-OpenShift

@cantino
Copy link
Member

cantino commented Mar 31, 2013

Thanks @ghelleks! The wiki is a great start for people who want to deploy to OpenShift.

@cantino
Copy link
Member

cantino commented Apr 1, 2013

Hey @ghelleks, would you mind taking a look at #35 and letting me know if it all looks good for your upcoming OpenShift PRs?

@ghelleks
Copy link
Author

ghelleks commented Apr 1, 2013

Yup, those are exactly the changes I was hoping for!

@ghelleks
Copy link
Author

ghelleks commented Apr 3, 2013

Two questions:

  1. Looks like the deployment fixes dropped support for TCP connections to mysql. Was that intentional?
  2. Would you prefer an .env.example for openshift, or use OpenShift env vars as a fallback default, eg:

database: <%= ENV['DATABASE_NAME'] || ENV['OPENSHIFT_MYSQL_DB_NAME'] || "huginn_production" %>

Using .env.example would make use of OpenShift explicit, the latter would mean Huginn runs out of the box.

@cantino
Copy link
Member

cantino commented Apr 3, 2013

  1. That was unintentional. Can you send a pull request?
  2. I think example configuration for OpenShift in the wiki would make
    sense, or .env.example.openshift if you think that would be much better.

On Wed, Apr 3, 2013 at 7:50 AM, Gunnar Hellekson
notifications@github.comwrote:

Two questions:

  1. Looks like the deployment fixes dropped support for TCP connections
    to mysql. Was that intentional?
    2.

    Would you prefer an .env.example for openshift, or use OpenShift env
    vars as a fallback default, eg:

    database: <%= ENV['DATABASE_NAME'] || ENV['OPENSHIFT_MYSQL_DB_NAME']
    || "huginn_production" %>


Reply to this email directly or view it on GitHubhttps://github.com//issues/30#issuecomment-15841118
.

@cantino
Copy link
Member

cantino commented Apr 7, 2013

@ghelleks Would you consider this finished? Is the Wiki article complete at this point?

@ghelleks
Copy link
Author

ghelleks commented Apr 8, 2013

Yeah, I think we're in good shape. Anything further can be covered in a separate, more specific issue. Thanks!

@ghelleks ghelleks closed this as completed Apr 8, 2013
@emorisse
Copy link

INVITATION_CODE is not exported in .env.openshift

see attached diff

git diff 7cede9a .env.openshift
diff --git a/.env.openshift b/.env.openshift
index 46dd38e..4652585 100644
--- a/.env.openshift
+++ b/.env.openshift
@@ -46,7 +46,7 @@ EMAIL_FROM_ADDRESS=from_address@gmail.com

This invitation code will be required for users to signup with your Huginn installation.

You can see its use in user.rb.

-INVITATION_CODE=try-huginn
+INVITATION_CODE=try-huginn-yo!

export
APP_SECRET_TOKEN
@@ -61,6 +61,7 @@ export
DATABASE_HOST
DATABASE_PORT
DATABASE_SOCKET \

  •   INVITATION_CODE \
    
    SMTP_DOMAIN
    SMTP_USER_NAME
    SMTP_PASSWORD \

@ghelleks
Copy link
Author

Fixed in c91cd12

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

3 participants