Omega sub theme for BOA sites using o1.ftp user

Posted by nitin.sareen.mca on March 20, 2014 at 1:53pm

Hi,
Since o1.ftp is extremely restricted, has anybody successfully implemented omega sub-theme that requires ruby and all its related commands?

Is there a process guide that one can follow?

Thanks

Comments

Omega does not require Ruby

Posted by rpsu on March 21, 2014 at 6:24am

Omega does not require Ruby on server side.

You can develop your Omega sub-theme locally and move theme to the server. On the server it is just regular PHP, CSS and JS -files that matter, Ruby etc. files are ignored.

--
Perttu Ehn

This was a dev box requirement

Posted by nitin.sareen.mca on March 21, 2014 at 6:32am

Thanks for your response but I was referring to a development box that I use with BOA stack. Since its a common box and is used by different developers, I needed a solution where we can develop a sub-theme in this environment.

Hopefully somebody got a solution :)

I did the same, just follow

Posted by attiks on March 21, 2014 at 7:57am

I did the same, just follow the installation instructions at https://drupal.org/node/2172619, but make sure to read the comments

Thanks but what about o1.ftp user?

Posted by nitin.sareen.mca on March 21, 2014 at 8:57am

Thanks attiks for the link. I however managed to get everything up & running via root but I was wonder how to allow the ruby ecosystem for o1.ftp user?

Any clues?

what is the problem if you

Posted by attiks on March 21, 2014 at 9:07am

what is the problem if you try running bundle install as o1.ftp?

Environment variables....loads of them

Posted by nitin.sareen.mca on March 21, 2014 at 9:24am

I can't get them loaded for o1.ftp user. As lshell.conf (ghantoos limited shell) doesn't support loading any!

I can get past the executable and paths, etc. but the environment variables are getting the better of me as of now.

i disabled the lshell on my

Posted by attiks on March 21, 2014 at 9:28am

i disabled the lshell on my system, so no idea how to fix it

Thats the solution workaround I did myself

Posted by nitin.sareen.mca on March 21, 2014 at 9:40am

Was hoping if we can initialize environment variables inside the limited shell, we can get it to work.

Thanks for your help attiks :)

Ability to override env

Posted by omega8cc on March 21, 2014 at 4:08pm

Ability to override env variables would present a giant security hole. But maybe we could add some sane defaults to support custom local gems?

Can this be done within the limits of restricted shell?

Posted by nitin.sareen.mca on March 24, 2014 at 4:47am

If yes, it would add another badge in the current functionality. Hoping it'll come soon.