Keenan, Thanks for your comments: they somewhat repeat suggestions I've received from others.
As a newcomer to web app development, I keep hoping there's a way to get collaborators working together but where valuable models don't need to be guaranteed by NDA's. In other words, yes, trusting the ability of my collaborators, but, no, nothing else. The only firm way I can see of doing this is to mock the models, but I wanted to avoid that work in my present case, as I've already built them. WRT Liquid, it would appear that I can simply make available model objects (and maybe some associated 'filters' or functions) that designers then manipulate in the context of their html. I guess in this way development can proceed without direct access to the app structure, and maybe just to blank or otherwise preliminary app pages that designers access only as clients. In any case, it seems from the comments here and Heroku docs that Heroku has no special way of accomplishing what I've been seeking, so, unless anyone sees a silver bullet, I'll consider this matter closed. On Jan 6, 7:04 am, Keenan Brock <[email protected]> wrote: > It may be hard for the dev to develop haml/erb without the models to populate > it. > > 1. Have them dev in pure html using a scratch directory in public. Create a > separate git repo that only has your public in it > > You can go have public as a submodule route or you can just have 2 different > projects and do duffs. Since you are going to need to translate back into > haml/erb at some point anyway. > > Second idea is to keep models innocuous and put truely proprietary logic in > external modules. Have them as a gem or plugin and don't include it in your > main repo. > > One thought: > > Many designers I know are quite comfortable with haml/sass or erb/css. Or > atleast they can tweak and improve it if not author it. > > Why work with people you don't trust? > > Why handicap them just to make more work for yourself? > > Rhetorical questions for you only. But I wanted to put out there. > > Keenan > On Jan 5, 2011, at 9:10 AM, Lille <[email protected]> wrote: > > > Hi, > > > I developed a Rails app, now hosted on Heroku, and I would like to > > make it available to HTML and javascript contractors for further > > development in sort of a Rails-agnostic way, while keeping private > > certain parts of the app directory structure, viz., my models, which I > > consider proprietary. > > > By 'Rails-agnostic', I hoped someone out there could confirm that > > development can proceed with front-end collaborators on Heroku relying > > solely on the collaborators' knowledge of Git, not the app platform, > > which is Rails. > > > With regard to keeping certain parts of my app structure private, I > > understand this is possible on some source control systems. What about > > in the case of collaborating via Heroku? > > > Thanks, > > > Lille > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
