New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Best practices #1

Open

jeff-h opened this issue Jun 12, 2014 · 0 comments

Member

jeff-h commented Jun 12, 2014

Since this is a public example of a MacGap 2 app, we should try to use best-practices wherever we can.

This immediately raises the question of directory structures. What is best-practice for the structure of code in a MG2 app?

Ideas:

clone MG2 repo into this one, and clone the documentation repo as a submodule into the public folder where we will also put any app-specific HTML/CSS/JS

— feels messy
— bad for anyone with write permission to the public MG2 or documentation repos as app code could accidentally get pushed into them

both the MG2 repo and the documentation repo cloned as submodules into this app repo

what does the folder structure look like for this?
where does the app code go (i.e. the public folder) — do we put it beside the MG2 repo and symlink? Change the path MG2 looks for /public?

@rawcreative, @perifer — interested in your opinions here.

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