ng a subject in my first email.
> >
> > Of course this is Bet365's decision. The purpose of this message
> > thread is to let people know that the RabbitMQ team is willing to
> > maintain cuttlefish. I also found the following more-up-to-date fork
> > and wil
point in time. Once the legal processes have concluded
> and people have the facility to manage the repository configurations, anyone
> interested in contributing and maintaining can be added - enabling the
> RabbitMQ team to work on Cuttlefish without the upheaval of moving
> reposito
anage the repository configurations, anyone interested in
contributing and maintaining can be added - enabling the RabbitMQ team to work
on Cuttlefish without the upheaval of moving repositories around. When the dust
has settled, then revisit the question of spinning the project out into its own
et365's decision. The purpose of this message
> thread is to let people know that the RabbitMQ team is willing to
> maintain cuttlefish. I also found the following more-up-to-date fork
> and will be looking at the changes there -
>
> https://github.com/Kyorai/cuttlefish
>
> Th
Hi again everyone -
Apologies for not setting a subject in my first email.
Of course this is Bet365's decision. The purpose of this message
thread is to let people know that the RabbitMQ team is willing to
maintain cuttlefish. I also found the following more-up-to-date fork
and will be lo
Thanks! I will look at this sometime this week, when I get a chance.
On 11/08/2015 08:49 PM, Drew Kerrigan wrote:
Hi Michael/Luke,
This thread is old, but after fighting through similar issues with
cuttlefish, clique, and node package, I put together a simple skeleton
app using all of
Hi Michael/Luke,
This thread is old, but after fighting through similar issues with
cuttlefish, clique, and node package, I put together a simple skeleton app
using all of those for myself and others:
https://github.com/drewkerrigan/erlang-app-skeleton
Hopefully someone weekday finds it useful
sion.
I am assuming that the important part, for Riak, is here:
https://github.com/basho/riak/blob/develop/rel/vars.config#L55-L59
Is your application open-source? I would be interested in getting relx
support into cuttlefish.
https://github.com/basho/cuttlefish/wiki/Cuttlefish-for-non-node_pa
pport into cuttlefish.
https://github.com/basho/cuttlefish/wiki/Cuttlefish-for-non-node_package-users
--
Luke Bakken
Engineer
lbak...@basho.com
On Thu, Oct 29, 2015 at 9:32 AM, Michael Martin wrote:
> Hi Luke,
>
> I understand now how to create a new .conf file. But, I still don
e
generated at build time, via this code:
https://github.com/basho/cuttlefish/blob/develop/src/cuttlefish_rebar_plugin.erl
--
Luke Bakken
Engineer
lbak...@basho.com
On Thu, Oct 29, 2015 at 8:12 AM, Michael Martin wrote:
> Hi Luke,
>
> Thanks for the quick reply.
>
> I
Hi Michael,
This wiki page may be of interest:
https://github.com/basho/cuttlefish/wiki/Cuttlefish-for-Erlang-Developers
After cuttlefish loads and processes your schemas, the variables and
values are available via Erlang's standard application:get_env()
function as though they were loaded
Hi folks,
Sorry if this is the wrong venue for cuttlefish questions - please 302
me to the right place if need be.
I would like to use cuttlefish in my application, but can't see how to
hook it in. Doing the schemas is
quite obvious - I have a small set of mappings ready to go. I just
12 matches
Mail list logo
