Upload, Store and Download small and huge files to/from file system (FS) via DDP and HTTP
protected
hook โ https://github.com/VeliovGroup/Meteor-Files/blob/master/docs/constructor.md
Hello @kakadais ,
Thank you for your proposal, we are looking forward to release major release for Meteor-Files package, with idea of pluggable adapters for 3rd party storage, we will take your suggestions into consideration.
To be honest upload re-tries should be managed by adapter/3rd party storage implementation
what I need to do is:
From all I read about this component I think I would be able to do all that with it - Is that correct??
Can anyone give me any instructions on how I should proceed in order to do that?
-= Thanks in advance =-
webapp
module
.addFile
, then fileURL
to get downloadable URL
.link()
method documentation, hope now this method usage will be more straightforward. Also answered on your veliovgroup/Meteor-Files#769
FilesCollection#unlink(fileObj, 'version')
Hello guys-
Meteor-Files is great to integrate file server as a single one, so server scales are much easier than before, but using multi-core would be good to go from the scratch.
Have you any idea for clustering for Meteor?
I'm expecting none Node or System level something like pm2/passenger , but something higher level integration such as kadira:clustering, but seems like not maintained.
Any idea?
@dr-dimitru Oh I think I made a misunderstanding, that's why I said None System Level something cause I have a knowledge about the field and used it.
I've seen the below video recently for cluster package and realized Microservices for Meteor were already concerned from 2015,
and thought that this model is super great.
https://www.youtube.com/watch?v=oudsAQZkvzQ&feature=youtu.be&t=15m27s
I think the reason why people are not implemented there system as a microservice is 'Annoying'. If we handle whole system level to salce up/out then the configuration and flexibility will hold us even a single changes, so some people uses NetflixOSS stuff to build their DevOps efficiently.
But after I've looked up the NetflixOSS things, it is still complex enough because of too much options and almost of it is not required at the small/middle system so we couldn't start on the same line.
The metreorhacks/cluster package is simple enough and especially Multi-Core Support strategy by node worker is so cool and works good still, I got a curiosity 'Isn't there any movement about this' things.
I should dig some more for this movement in Meteor or Node- ;)
So Need and Interesting part-
@dr-dimitru Oh I just asked your opinion for cluster. Because I could feel good your inspection for Meteor on your Iron-router / Flow-router fork repos.
My final goal is 'Use & Teach a Meteor as a small/middle size project'.
I've already done for a lot projects include a bit big size than middle one.
Meteor is great to go from the scratch, Meteor-Files make the file control super good, so now I just want to check how capacity could we make the system and stable.
So, it was just a pure question for Easy Clustering(actually forking the process whatever to use single multi-core server enough).
Sorry if it was departed too much from the purpose of this place- ;)