Topic: [NEW HOWTO] Rocket.Chat

[guest22]

Edit: At first glance, though, it seems to work with that property deleted as well.

Looking at the source code of smesever-webapps-common it seems that the priority evaluation order of db properties is:
1. ProxyPass
2. Rewrite
3. Redirect

So basically, next to the default command line arguments, only setting the ProxyPassTarget property would do the job in case of a ProxyPass situation.

ps. Need to add this to the wiki.

[guest22]

Somewhat surprisingly, the ProxyPass setup didn't interfere with getting a Let's Encrypt cert for that hostname either.

That may have to do with http://gitweb.firewall-services.com/?p=smeserver-webapps-common;a=patch;h=c200387012776f811e0b06408332add8535712eb

[ReetP]

Having a fiddle with this today.

As far as building a RPM the tricky bit is handling nodejs

For the moment I am looking at a manual install of node first, followed my the rpm which will take care of most of the rest and add some configurability.

Couple of things.

First is I cannot modify the installer.js as per the wiki. The forever service seems to install happily but......

And then this happens:

Code: [Select]

sed -i -e 's/(Oracle Linux)/(Oracle Linux)|(SME Server)/' \
/opt/rh/nodejs010/root/usr/lib/node_modules/forever-service/templates/sysvinit/installer.js
sed: can't read /opt/rh/nodejs010/root/usr/lib/node_modules/forever-service/templates/sysvinit/installer.js: No such file or directory

As a result I cannot see the startup script that it generates - I was wondering if it would be simpler to use our own (the forever service may not then be required) which could also then be modified as a template.

Any hints or tips ?

[guest22]

Something must have gone wrong in the previous step installing forever and forever-service, for those commands install the target file 'installer.js'

[guest22]

ps. from within a script you may have to use the following:


scl enable nodejs010 bash
npm install -g forever
npm install -g forever-service
exit 0

[ReetP]

ps. from within a script you may have to use the following:


scl enable nodejs010 bash
npm install -g forever
npm install -g forever-service
exit 0

Thanks. That seemed to work on the CLI - for some reason it failed before. Will re test.

[guest22]

Appears to me that you did not reboot where the wiki said you should

[guest22]

Thanks. That seemed to work on the CLI - for some reason it failed before. Will re test.

From within an RPM, I guess a 'reboot' is not the preferred way So we need to make all boot scripts executable and execute them opposed to a reboot.


See Dan35 suggestion.

[ReetP]

Ok I am making a little progress.

I am not exactly sure how to get round the node js things so am tackling it a little differently by installing the node js bit first and then add the rpm to enable you to reconfigure stuff.

Basic code is here but I really wouldn't try it just yet

https://github.com/reetp/smeserver-rocketchat

As soon as I have something workable I'll post a link for those who like to break things 

[guest22]

Koozali SME Server has been added to the PAAS deployment list by the Rocket.Chat team.

@Rocket.Chat team, Thanks!

https://rocket.chat/docs/master/installation/paas-deployments/koozali/

[ReetP]

Koozali SME Server has been added to the PAAS deployment list by the Rocket.Chat team.

@Rocket.Chat team, Thanks!

https://rocket.chat/docs/master/installation/paas-deployments/koozali/

Yes I saw that - nice one !

OK, I have a modifiable init script now. Need to sort some variables though.

[CharlieBrady]

ps. from within a script you may have to use the following:


scl enable nodejs010 bash
npm install -g forever
npm install -g forever-service
exit 0

Using npm should be avoided if possible. It means that you have software installed which isn't controlled and managed by rpm.

I know that npm is the 'standard' way that nodejs packages are installed, but it is problematic. See:

http://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/

[guest22]

Using npm should be avoided if possible. It means that you have software installed which isn't controlled and managed by rpm.

I know that npm is the 'standard' way that nodejs packages are installed, but it is problematic. See:

http://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/

Isn't this why we use Software Collections and all dependencies etc go into /opt/rh or other specific Software Collections directories?

[ReetP]

I've gotten rid of the forever-service module. and templated the initscript it generated

The forever module seems to be some sort of init wrappery type of thing. If I can figure how to dispense with it at some point I will, but I have spent my time on templating the other stuff so far.

Still working on it and will come back to this later.

[Daniel B.]

Isn't this why we use Software Collections and all dependencies etc go into /opt/rh or other specific Software Collections directories?

Nop, SCL are "just" rpms repo, and are fine (doesn't matter if they install in /usr or in /opt as long as they are managed by yum). Npm is NodeJS "package manager", just like cpan is to perl. When possible, it's best to install only RPM and not rely on this kind of package management. But with NodeJS, it's hard, most of the time, you have to use npm.