-
Notifications
You must be signed in to change notification settings - Fork 2k
Deploy to openshift #477
Comments
@mpescarmona you should first try cloning this repository and having MongoDB accessible and adding in the environment variables. It should work at that point, but if you have any other questions, feel free to come back with more info so we can help more. |
@ilanbiala thanks a lot for your help, but I couldn't get deployed the meanjs demo application on OpenShift.
Any other idea or suggestion ? |
Can you put these in code blocks? It's much easier to read code and errors that way. |
Sorry, I have updated my comment with the code blocks. |
Maybe it timed out? I would submit a support issue to Openshift. It would be great if you could post the solution here so others will know and we can add it to the docs. |
Here is my production.js file. Hope it helps 'use strict';
var dbCon = 'mongodb://localhost/mean-dev';
if(process.env.OPENSHIFT_MONGODB_DB_USERNAME)
{
dbCon = 'mongodb://' +
process.env.OPENSHIFT_MONGODB_DB_USERNAME + ':' +
process.env.OPENSHIFT_MONGODB_DB_PASSWORD + '@' +
process.env.OPENSHIFT_MONGODB_DB_HOST + ':' +
process.env.OPENSHIFT_MONGODB_DB_PORT + '/' +
process.env.OPENSHIFT_APP_NAME;
}
module.exports = {
db: dbCon,
port: process.env.PORT || process.env.OPENSHIFT_NODEJS_PORT || 3000,
ip: process.env.OPENSHIFT_NODEJS_IP || process.env.IP || 'localhost',
facebook: {
clientID: process.env.FACEBOOK_ID || 'zzzzzzzz',
clientSecret: process.env.FACEBOOK_SECRET || 'zzzzzzz',
callbackURL: '/auth/facebook/callback'
},
twitter: {
clientID: process.env.TWITTER_KEY || 'CONSUMER_KEY',
clientSecret: process.env.TWITTER_SECRET || 'CONSUMER_SECRET',
callbackURL: '/auth/twitter/callback'
},
google: {
clientID: process.env.GOOGLE_ID || 'APP_ID',
clientSecret: process.env.GOOGLE_SECRET || 'APP_SECRET',
callbackURL: '/auth/google/callback'
},
linkedin: {
clientID: process.env.LINKEDIN_ID || 'APP_ID',
clientSecret: process.env.LINKEDIN_SECRET || 'APP_SECRET',
callbackURL: '/auth/linkedin/callback'
},
github: {
clientID: process.env.GITHUB_ID || 'APP_ID',
clientSecret: process.env.GITHUB_SECRET || 'APP_SECRET',
callbackURL: '/auth/github/callback'
},
mailer: {
from: process.env.MAILER_FROM || 'MAILER_FROM',
options: {
service: process.env.MAILER_SERVICE_PROVIDER || 'MAILER_SERVICE_PROVIDER',
auth: {
user: process.env.MAILER_EMAIL_ID || 'MAILER_EMAIL_ID',
pass: process.env.MAILER_PASSWORD || 'MAILER_PASSWORD'
}
}
}
}; |
Seems as not a timeout issue. Did you see the --timeout 600 (seconds) on the executed command ?. |
@mpescarmona When I asked Openshift about it, they said that cloning from a Git repo has a timeout of 2 minutes, but that could have changed. |
I'm also looking to do the same thing. Any success yet ? On Mon, Mar 16, 2015 at 9:25 AM, Ilan Biala notifications@github.com
|
Sorry @karan-kapoor90, I couldn't test and apply the suggestion made by @puttyman, but I will apply soon and share here my findings. |
Hi guys, I'm tested the production environment suggested by @puttyman but without success. Below is the command executed and its stacktrace:
This is the log of the executed command
|
@karan-kapoor90 did you get success for your side ? |
Haven't had the opportunity to look into it yet . Been busy making a On Saturday, March 21, 2015, mpescarmona notifications@github.com wrote:
|
@karan-kapoor90 you can open a PR and we'll get some feedback going if you already have something just to start looking at. Some feedback and reflection on the implementation would be good, too. |
Cool. It's integration interface is an angular service naked by some server On Saturday, March 21, 2015, Ilan Biala notifications@github.com wrote:
|
0.4 would be better, but we'll probably have to update/rebase it later if we decide to merge it in. |
@karan-kapoor90 Are you still interested in submitting a PR for this? |
@karan-kapoor90 haven't heard anything, so I'm going to close. Feel free to comment if you open a PR. |
My question is about the feasibility to add support for deployment of mean boilerplate into openshift.
The text was updated successfully, but these errors were encountered: