and of course you need to setup a discovery method, which simply should be just dns https://github.com/wzrdtales/seneca-generators-service/blob/master/generators/app/templates/index.js#L15-L40
which you point to the name of your base node services
And yeah the support is low. I talked to rodger a good month ago and he told me that they want to start work again, but seems like it did not yet happen. But this is open source, if you want something to be better, then help making it better. You give back to the community for all the things you gain, which is just fair.
And sometimes that means figuring out stuff on your own. Which of course means you need a deep understanding and knowledge about all the tools you use and about computers in general and the rest should come at ease :)
The best I got so far is to set all services as base
That way it works
Of course I use to give back to the community what it gives to me
And of course I make an effort understanding the technologies I use and the code that supprots them
But I can not get as deep as I want on all of them
And I'm just starting with seneca
hi @danielo515 if I understood your problem, let write the new one logger like this
https://github.com/rjrodger/seneca-demo-logger/blob/master/demo-logger.js#L24
https://github.com/rjrodger/seneca-demo-logger/blob/master/demo-logger.js#L24
Is this supposed to work ?
seneca.ready (() =>
{
const app = Connect ();
app.use (Connect_query ());
app.use (Body_parser.json ());
app.use (seneca.export ('web'));
app.listen (3000);
// seneca.use ('data-editor');
// seneca.use ('admin', { server: app, local: true });
});because it is not working for me at all
I need a service written in some other language to be able to be brought into the seneca pool.
Is it possible? If yes, how?
I have some nodes that initially see the entire mesh, but after a while they got isolated
And it is very easy to get isolated
And there is no way to re-join the mesh or re-discover the bases
Is there any way to reduce this problem ? To increase the timeout ?
You provide to the remote command a pin to "call you back" when the job is done
then the remote process just calls the pin you have provided with the answer
this is called async communication
You can find my code files are here: https://gist.github.com/ohmtrivedi/5a94841d25714f3cfd6aee260add97bb
I have a basic architectural answer and I could not find any good information about it..
I have one microservice and several worker that generate a file based on the parameters they get
how to transfer the files the worker create
Hi, I am a newbie in Seneca and also not much experienced with Javascript. Can someone please help me with this issue I am facing? senecajs/seneca#706
