On Wed, 14 Nov 2001 11:12, Mircea Toma wrote: > > I can come up are: > > > > a) "app-name", "app-name~", "app-name~~"..... > > > > b) "app-name", "app-name-1", "app-name-3"..... > > > > I prefer a) but, maybe there is a better one?! > > Ahh, I don't think this is right. If we change the name of the deployed > application will make things more complicated. Let's suppose we have two > applications having the same name "foo". When deploying the applications > the result will be: first application (1) will be deployed in "apps/foo" > directory and the second one (2) in "apps/foo~". Now if we reboot Phoenix > and re-deploy only the application (2) the Deployer will deploy application > (2) in application's (1) directory "apps/foo"!!!! Things get worse if we > would use PersistentDeploymentRecorder (as you said already). > So the simple solution would be to just print a message saying that an > application with the same name is already deployed. We could also have an > "--application-name" parameter passed at CLI.
urk. Starting to get complicated here. Couldn't we just use the full URI to application. ie the name would be file:/some/file/location/phoenix/apps/blah.sar file:/some/file/location/phoenix/another/apps/blah.sar ? > Another problem is about "--application" parameter which I think is > redundant. Its functionality could be achieved by starting Phoenix with a > different deployment path using "--apps-path" (and having the .sar in that > path). hmm - I hadn't thought about that. -- Cheers, Pete "The perfect way is only difficult for those who pick and choose. Do not like, do not dislike; all will then be clear. Make a hairbreadth difference and heaven and earth are set apart; if you want the truth to stand clear before you, never be for or against." - Bruce Lee -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
