These are chat archives for jescalan/roots

27th
Sep 2016
John Peele
@johnpeele
Sep 27 2016 15:36
Morning all! Does anyone have a solid process for deploying the public directory to a Rackspace (or any other server for that matter) via ssh?
Jeff Escalante
@jescalan
Sep 27 2016 16:11
it should be no different than deploying any other folder of static files! i don't have one off the top though, we typically use netlify for deployment
John Peele
@johnpeele
Sep 27 2016 16:12
@jescalan Right, the prob is that I am not committing my public directory to my repo
Kyle MacDonald
@kylemac
Sep 27 2016 16:12
@johnpeele we tend to use a host that will run our build command for us on their server
a blank rackspace server won't do that (without a bunch of configuration) so i might suggest you run a roots compile and then rsync your public directory to the server
John Peele
@johnpeele
Sep 27 2016 16:14
@kylemac I am using a Rackspace cloud server, so I guess I could config it and install node and roots
Kyle MacDonald
@kylemac
Sep 27 2016 16:14
you could - but its a bit overkill for just static files imo
John Peele
@johnpeele
Sep 27 2016 16:14
I have never used rsync before
true
Kyle MacDonald
@kylemac
Sep 27 2016 16:15
its quite simple. a unix utility that takes files/dirs from one place and puts them in another
you can pass your ssh creds to it
John Peele
@johnpeele
Sep 27 2016 16:15
i'll look into that
Carl Morlock
@gin93r
Sep 27 2016 16:21
Has anyone had any luck loading bourbon-neat? I've changed my preprocessor to node-sass, but I cannot seem to get it to recognize the import: File to import not found or unreadable
Tom Kraak
@tkraak
Sep 27 2016 16:27
@gin93r ... you got sass itself running?
Carl Morlock
@gin93r
Sep 27 2016 16:28
@tkraak I do.
Carl Morlock
@gin93r
Sep 27 2016 19:38
@tkraak To elaborate, I have node-sass installed and added to app.coffee. I also removed all of the stylus stuff. I'm able to process the .scss files and whatnot. The problem arises when trying to use @import "neat". I'm just not having any luck with the includeFiles option of node-sass. Or at least that's my guess. I'm sure I could reference it using the full path, but I shouldn't have to.
Tom Kraak
@tkraak
Sep 27 2016 19:44
so the sass compiles fine?
it's bootstrap instead of neat, but that should not matter for @import
Carl Morlock
@gin93r
Sep 27 2016 21:15
Yes it compiles fine. I'll look at that more closely, but it appears bootstraps' files are in in assets/css/vendor in that repo whereas bourbon-neat is in node_modules. One thing I didn't try was adding node_modules to the includedPaths so that might be something to look into. I could always move the files as a last resort but I was trying to do the whole npm package thing.