multiple apps mixed in different webs / projects

[hinnack]

Hi,

I have the following app(s):
myapp.first
myapp.second
myapp.third
myapp.fourth

and I have the following projects (websites), where the apps are
registered:
project1
myapp.first
myapp.second

project2
myapp.first
myapp.third

project3
myapp.first
myapp.third
myapp.fourth

and so on..

So no every app is in every project. But some are in more then one
project.
They ALL use the same DB!! So no multi db until now...

What is the best practise now to use south?
build up one pseudo project with all modules in?
Any other suggestions?

regards

-- Hinnack

[Andrew Godwin]

If they use the same database, then presumably the schemas will match,
so South will Just Work in this case (since myapp.first is the same app,
just in three projects).

South tracks which apps' migrations are applied in the database, not in
the project, so when you run migrate from one project it will know about
migrations applied to its apps from another project.

You'd have problems if you had two different apps called "first" sharing
the same database (i.e. with different codebases but the same name), but
that's not very common, and doesn't just break South, but a lot of other
stuff.

Andrew

> --
>
> You received this message because you are subscribed to the Google Groups "South Users" group.
> To post to this group, send email to south...@googlegroups.com.
> To unsubscribe from this group, send email to south-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/south-users?hl=en.
>
>