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

from huginn.

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

from huginn.

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

from huginn.

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.

from huginn.

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
[email protected]:

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
.

from huginn.

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

from huginn.

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

from huginn.

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=[email protected]

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 \

from huginn.

Fixed in c91cd12

from huginn.