Skip to content
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.

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

pake task operation modes #4

Open
bergie opened this issue Dec 20, 2010 · 3 comments
Open

pake task operation modes #4

bergie opened this issue Dec 20, 2010 · 3 comments
Labels

Comments

@bergie
Copy link
Member

bergie commented Dec 20, 2010

we have basically 3 modes for midgard to run in

  1. global (/etc/midgard/conf.d/), default MySQL db
  2. user (~/.midgard/conf.d/), default sqlite db
  3. self-contained (any dir, needs separate custom php.ini for each case), probably should not default (at least not silently) sqlite

the pake tasks should take these scenarios into account and have flags and/or heuristics to determine which case to use.

(moved from https://github.com/midgardproject/midgardmvc_core/issues/issue/28)

@bergie
Copy link
Member Author

bergie commented Dec 20, 2010

Flags is probably the right thing here. So the installer could either accept a --deployment-model parameter with values global, user and directory or ask it when installing.

@indeyets
Copy link
Member

does anyone really need "user" mode for mvc applications?

@rambo
Copy link
Member

rambo commented Dec 20, 2010

probably not for MVC apps, I'm not 100% sure though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants