Skip to content

Conversation

@mihai
Copy link

@mihai mihai commented Mar 16, 2014

Thought of adding some details on setting local development for the project and also updated the CONTRIBUTORS file to link to GitHub profile pages.

Let me know if it looks good.

@cameron
Copy link
Owner

cameron commented Mar 16, 2014

This looks great, with one little thorn: it breaks my development workflow for www.squirt.io. That repo is setup to serve squirt from a folder called bm. The easiest solution for me would be to put squirt.js back into a folder called bm, but that feels a little silly for everyone else. git subtree split looks promising (I'm already using git subtree to manage the relationship between squirt.io and squirt) because it would allow me to commingle the squirt repo files alongside squirt.io files without isolating them in a sub directory, but if you have any other bright ideas, holler!

@mihai
Copy link
Author

mihai commented Mar 16, 2014

git subtree does seem like a solution for this case.

@cameron
Copy link
Owner

cameron commented Mar 16, 2014

AFAICT, subtree only operates on subdirectories. I need to setup a non gh-pages host to add SSL anyway, so I'll be able to configure nginx to redirect requests for /squirt to /bm/squirt. Will merge as soon as I have my development workflow ironed out (today).

@mihai
Copy link
Author

mihai commented Mar 16, 2014

Sounds great, thanks @cameron!

@cameron
Copy link
Owner

cameron commented Mar 18, 2014

Apologies for the delay here. My attention for the past few days has been primarily on my job, and figuring out how to move http://squirt.io towards a sustainable business. Oh! Just had an idea to fix the dev workflow and merge this!

@dsernst
Copy link

dsernst commented Mar 26, 2014

Thanks for the local dev tips, @mihai 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants