Could I use one redis-oplog docker container for multi meteor app?
See original GitHub issueI am a newbie for Redis-Oplog
.
Could I use one redis-oplog
docker container for multi meteor app?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
RFC: No oplog vs. oplog vs. redis-oplog when self-hosting
Seems like it should be easy to self-host, right? So far, I've been using Docker to set up Meteor and Mongo on this...
Read more >Support for redis oplog · Issue #1 · zodern/mup-redis - GitHub
Currently, this plugin only supports the Meteor app running on one server. After Meteor Up 1.5, I will add support for using mup-redis...
Read more >How to deploy a Meteor app which uses Redis? - Stack Overflow
I stumbled upon this package recently redis-oplog which seems to be a very good package. Given that I do not have any experience...
Read more >How to deploy a Meteor app which uses Redis?-node.js
If you cannot afford to have servers for Redis you can run it on server where you have installed your mongodb instance if...
Read more >mup - UNPKG
Mup can be configured to use a private docker registry, which allows it to deploy to multiple servers much faster. Instead of uploading...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, so you have multiple instances of the same app. You’ll probably need to get into doing some custom namespacing beyond the default channel names that are used when you just use the default Meteor publication code. Otherwise the publications’ channels would end up cross-contaminating with each other on the same redis server.
So if you could somehow insert per-instance naming into the channel names - maybe using environment variables or something from the
settings.json
that is set per instance, they would then not stomp on each other. Otherwise they would probably each need their own redis server.Oh, that’s awesomw!