[LRUG] resolving JS dependencies on deploy

[Riccardo Cambiassi]

Hi Tom,
I'm not sure it applies to your case, given your problem is with licensing,
but would it make sense to fetch the said gemified library from a git(hub)
clone repo?

  R

On Thu, Nov 19, 2015 at 2:34 PM, Tom Armitage <tom at infovore.org> wrote:

> I have a Rails project with dependencies on a single external JS library
> that for reasons - primarily, licensing - I don’t want to include in my
> vendored libraries.
>
> Currently, I’ve been referencing it via Rails-Assets (
> https://github.com/rails-assets/rails-assets) which makes it available as
> a gem, and thus it’s bundled by the end-user at deployment time.
>
> Except: Rails-Assets is down, again, and the future of the project is
> feeling a tad suspect. So I’m asking for myself: what are my alternatives
> here?
>
> I am loathe to tear out my basic usage of asset-pipeline to replace it
> with some onerous npm-derived asset preprocessing (gulp, grunt, etc, etc,
> etc); I also really can’t include the library within my codebase, so need
> to find a way for it to be pulled down, both locally (for development) and
> on deployment via Capistrano.
>
> Any thoughts? How do you tend to do this?
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> Archives: http://lists.lrug.org/pipermail/chat-lrug.org
> Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org
> List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>


-- 
Riccardo CAMBIASSI
http://twitter.com/bru
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20151119/089ec479/attachment-0002.html>