-
Clone https://github.com/SassMeister/sass33.sassmeister.git (the app that handles compiling against Sass 3.3)
-
(optional) Clone https://github.com/SassMeister/sassmeister/sass32.sassmeister.git (the app that handles compiling against Sass 3.2)
-
(optional) Clone https://github.com/SassMeister/sassmeister/libsass.sassmeister.git (the app that handles compiling against LibSass)
-
Run
bundle installin each Ruby app -
Install Pow if you don't already have it a.
curl get.pow.cx | sh -
Symlink the apps to Pow: a.
ln -s /path/to/sassmeister ~/.pow/sassmeisterb.ln -s /path/to/sass33.sassmeister ~/.pow/sass33.sassmeisterc. (optional)ln -s /path/to/sass32.sassmeister ~/.pow/sass32.sassmeisterd. (optional)echo 1337 > ~/.pow/lib.sassmeisterPow will now serve the apps at http://sassmeister.dev, http://sass33.sassmeister.dev, etc. Pow will run the Ruby apps automatically;
touch tmp/restart.txtto restart an app. The Node.js app must be run and restarted manually (node app.js -p), all Pow does is act as a port proxy. -
Create
tmp/restart.txtin each Ruby app. (I should probably add that to the repo…) a.mkdir tmp && touch tmp/restart.txt -
If you want to use the gist features, follow the instructions in the main app's README
Last active
July 16, 2017 17:23
-
-
Save jedfoster/8361593 to your computer and use it in GitHub Desktop.
Steps to run SassMeister locally
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment