start backend on a standalone node
It looks like we can’t allow a run configuration to run on “nohost”? Is this true or could it be added?
We do a lot of work with a local mnesia database, which puts the host name in the schema, we do not use a distributed environment via epmd.
When we run our ant builds and create the product for distribution to the field (auto repair bays with unknown network configurations) we use mnesia db schema Mnesia.nonode@nohost. However, in development using erlide we can’t use this because it always sets the host name, so we have to recreate the databases for each developer: Mnesia.nodename@WillsPC, Mnesia.nodename@SamsLaptop, Mnesia.nodename@Jackie, etc. etc.
Is there any way we can use the simple “nonode”, and maybe turn off epmd also?
We do a lot of work with a local mnesia database, which puts the host name in the schema, we do not use a distributed environment via epmd.
When we run our ant builds and create the product for distribution to the field (auto repair bays with unknown network configurations) we use mnesia db schema Mnesia.nonode@nohost. However, in development using erlide we can’t use this because it always sets the host name, so we have to recreate the databases for each developer: Mnesia.nodename@WillsPC, Mnesia.nodename@SamsLaptop, Mnesia.nodename@Jackie, etc. etc.
Is there any way we can use the simple “nonode”, and maybe turn off epmd also?
Leave a comment
on 2009-08-03 19:32 *
By Vlad Dumitrescu
Status changed from New to Accepted
Work remaining set to 8.0
Status changed from New to Accepted
Work remaining set to 8.0
the only functionality available for standalone nodes is
- starting the node
- opening a console
- keeping the code updated after editing [use ErlideCode.loadBeam]
More advanced interaction is a lot of work and we'll have to be convinced it's worth it.
- starting the node
- opening a console
- keeping the code updated after editing [use ErlideCode.loadBeam]
More advanced interaction is a lot of work and we'll have to be convinced it's worth it.
on 2009-10-21 20:01 *
By Vlad Dumitrescu
Status changed from Accepted to Test
Work remaining changed from 8.0 to -none-
Status changed from Accepted to Test
Work remaining changed from 8.0 to -none-
implemented since a while back