Hi, i am trying to do this on my project, but unfortunately I can't get the
new app to compile.
Its code is under my_boss_app/src/apps/utils/my_util/src
I added the path to the boss.config
but when I launch rebar to do the build, it does not get compiled.
A previous post mentioned the clear need to 'hook the new app to the
compile process', but how can I do that?
A bit of extra info:
in my project, when I run the build via rebar, for each dependency in
deps/, I have a couple of lines like
<dep1> (pre_compile)
<dep1> (compile)
but for the 'main' my_boss_app project, I only have one
<my_boss_app> (pre_compile)
Any hints?
Thanks in advance.
On Sunday, November 18, 2012 at 9:15:46 PM UTC+1, Alex Gounares wrote:
>
> excellent, thanks Chan and Evan--this is working out well for us so far.
>
> for future readers of this thread, you need to include the app path
> boss.config in a separate stanza...e.g...
> [{boss, [....<existing boss config>]}, { my_boss_app, [...]},
> {new_sub_app, [{path, "../my_boss_app/src/apps/new_sub_app"}].
>
> cheers,
> alex
>
> On Nov 17, 2012, at 6:36 PM, Chan <[email protected] <javascript:>>
> wrote:
>
> Yes separate dir, and you can add dependency in the app.src doing this
> your app start automatically and no need to start it from your script.
> erlang magic
>
> Envoyé de mon iPhone
>
> Le 18 Nov 2012 à 04:58, Evan Miller <[email protected] <javascript:>> a
> écrit :
>
> Others might have better advice, but the standard way to include other OTP
> apps at this point is to put them in separate directories, and then start
> and stop them in your application's init scripts.
>
> Evan
>
>
> On Sat, Nov 17, 2012 at 10:00 AM, Alexander Gounares <[email protected]
> <javascript:>> wrote:
>
>> Hi everybody...
>>
>> Is there a recommended design pattern for adding a separate OTP app to a
>> ChicagoBoss app? In our case, for example, we'd like to have a portion of
>> our web site performing long running jobs, and those jobs occasionally feed
>> data back through a boss_mq queue. In another case we have some transient
>> 'global' state to keep track of that we don't want to persist through
>> boss_db.
>>
>> It looks like there are a few different ways to do this:
>>
>> 1. make a completely separate OTP app and git repo and include it via
>> rebar.config in the deps section and in in foo.app.src in the
>> applications
>> section.
>> 2. make a subdirectory under the main src directory (say
>> src/apps/our_otp_app) and hook it into the compile process.
>> 3. just build a gen_server and hook into the existing ChicagoBoss
>> app/supervisory tree (and in this case, what is the recommended way to do
>> this?)
>>
>>
>> Is there a best practice we should be following here?
>>
>> thanks everyone!
>> alex
>>
>>
>> --
>>
>>
>>
>
>
>
> --
> Evan Miller
> http://www.evanmiller.org/
>
> --
>
>
>
>
> --
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"ChicagoBoss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at http://groups.google.com/group/chicagoboss.
To view this discussion on the web visit
https://groups.google.com/d/msgid/chicagoboss/7cd5d97c-1fcb-46a7-a3d5-cb2e64a476ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
