search

shawnlawson / The_Force

webGL live coding performance IDE
https://shawnlawson.github.io/The_Force/
MIT License
274 stars 52 forks source link

updated readme.md, added help directory for helpful files #6

Closed wabkia closed 8 years ago

wabkia commented 8 years ago

Just some quick notes from my setup today.

could save people some time in initial setup so they can get to playing with this software!

shawnlawson commented 8 years ago

AH, nice! I'll roll this in to get people started.

I have mine configured slightly differently though. Here's roughly how and why. Wondering what you think about it?

I have the repo sitting at ~/Sites/The_Force with a .conf file in /etc/apache2/users that gives access to that Sites folder. Getting to that in the browser is admit-ably a pain. Then I have virtual hosts running so that I can type local.The_Force into the browser and access the site. That config is in /etc/apache2/extra . I also added 127.0.0.1 local.The_Force to my hosts file at /etc/hosts not sure if I needed it or not, was a long time ago.

The biggie... Chrome has been getting stricter on security, so using getusermedia() (accessing the microphone) I think was going to need to be on an https instead of http connection. The soundcloud api (I had cross-domain issues) is also https. Then, the Open Sound Control stuff, is sent out through a wss secure websocket instead of ws unsecure websocket. To get all of these to work together, I needed to serve up The_Force locally by https. That required enabling all the SSL stuff, keygen, and more configuration. Here's the GIST I followed https://gist.github.com/jonathantneal/774e4b0b3d4d739cbc53

wabkia commented 8 years ago

Really I was just upset apple had their own way when the sites-enabled/sites-available paradigm is so easy. I ran into issues with the ~/Sites setup and when I did it my way (closer to the old debian style) it worked fine. No permissions to change, no worrying about enabling new mods... just add the directory directive (which can be wrapped in a vhost), copy in the directory and go. I am not sure if the ~/Sites method is more secure than my method, though I am not sure it matters too much when were talking about apple's custom apache2 build.

I'd like to write a setup script eventually that takes some user input and fixes everything up (non-destructively of course) so I will keep working on the sites method because that's obviously the way apple wants things done and I doubt telling people to go grab the F/OSS apache2 is going to foster the use of The_Force. I left out any vhost setup because the /Library/WebServer/Documents I didn't need to specify a web framework or interpreter and it's easy to go to localhost/the_force.

I'll keep working on this aspect of documentation as I keep playing with The_Force! Glad I can help!