Installing the .boot file.

[Danie Schutte]

Since you are going the OTP route :) 

I would suggest stick to known directory structures as suggested in the 
documentation and some leading experts :) 

The basic structure we use looks as follows

project
	bin
	lib
		patch
		app
			ebin
			src
			include
	releases
		x.y
	misc

in misc we keep our startup scripts
and the app is started from within the project directory - using paths 
relative to that.

example:
troy.sh

erl +A 255 -name troy@REDACTED -boot releases/1.0/troy -config 
releases/1.0/sys -mnesia dir '"/troy/db_data/troy"'


This way everything is "neatly" placed in the right spot - which is easier and 
cleaner to maintain later on.


On Saturday 21 January 2006 16:01, Pupeno wrote:
> On Saturday 21 January 2006 07:49, Ulf Wiger (AL/EAB) wrote:
> > Pupeno wrote:
> > > where can I install my .boot file to be found ?
> > >
> > > $ erl -boot myapp
> > > {"init terminating in do_boot",{'cannot get bootfile','myapp.boot'}}
> >
> > Give the full path name (without the .boot extension),
> > e.g.:
> >
> > erl -boot /usr/lib/erlang/lib/myapp-0.0.0/priv/boot/myapp
>
> That is what I was trying to avoid, I could also specify the path to -pa
> and it works. But all that is going to end up in a script to run my
> application and if I put any path in the script, the script would be system
> dependent (paths changes from system to system) and I'd have to make my
> build system capable of modifying a script, which doesn't seem easy nor
> straightforward. Thank you.