I'm revisiting paper_trail after a while, and the documentation seems to indicate that it is not recommended for use with rails_admin in production. Is this correct?
Related
I need to create authentication with reactjs and node/express. Previously I did that with redux and right now I am not up-to-date with react-hooks.I saw somewhere in article that this can replace redux.This is little confusing for me, so I need good suggestion about this, and if you can share some article or example of react(updated) node/express authentication,then please share.
Thanks for attention to my wired question))))))
It really depends on what you want to do with your app. When you deal with more complex logic or flows in your application, I personally prefer Redux for making the code cleaner and easier to manage. If it's a simpler flow application, you can definitely leverage on hooks and context to create your own state management as good as Redux.
However, if the application ever has the potential to grow into a complex app (like requires middleware, debugging tools, etc.) I'd recommend starting with Redux so you don't have to switch from hooks into Redux later.
First, understand what Redux offers (and how it helps in a complex app):
https://redux.js.org/
Some related good articles as requested, if you want to build your own redux-hooks:
https://blog.logrocket.com/use-hooks-and-context-not-react-and-redux/
https://gorillalogic.com/blog/how-to-build-your-own-redux-state-management-implementation-based-on-hooks/
I'm planing on having my database stored in Cloudant.
Is it safe to use local CouchDB during development, testing and staging of our application with knowledge that everything works locally should also work on Cloudant?
Certainly. Cloudant is API compatible with the Apache CouchDB API with a few subtle distinctions, all of which are documented at http://docs.cloudant.com. Some highlights are:
we disable temporary views (they would be expensive for you at scale!)
for our distributed system, we have extend the update_seq from an integer to a string
your re-reduce code will nearly always be called, so we recommend using exclusively built-in reduce methods
we have fully integrated lucence indexing/search
we have multi-stage mapreduce processing via "dbcopy"
I do a very similar process. You don't need the same versions, it will actually be very different no matter how you look at it. Cloudant is very cool, and have made a lot of alterations and additions to their system. So, if you are looking at developing views, attachments, etc, then you can develop those locally on your dev project. Once your dev project looks good, I would have those checked into the staging/qa server, which I like to use Cloudant for as well. Thats where you need to get everyones code working together. after that is done, you can fire off a replicator to replicate your staging to production.
No matter how you look at it though, or how you envision the process being, you are going to want to take a close look at the going from dev to QA. There are ways to go about it so that everyone can dev on their own, and merge up. I personally like to use github. I hope this helps you out in your tasks.
What are the node.js frameworks for real-time model synchronization?
I am aware of only racer (https://github.com/codeparty/racer).
You can look into:
node-object-sync https://github.com/jonashuckestein/node-object-sync ,
backbone.iobind https://github.com/logicalparadox/backbone.iobind or
backbone.io https://github.com/scttnlsn/backbone.io
but racer / derby is not bad either. These are just options, you should pick one whichever is most appropriate for you.
I suggest you continue using Racer, or, if you are interested in a more mature framework based on Racer, I strongly suggest you try out Derby.
If you are coming from Rails, I would totally suggest you go all in with Derby. If you are looking for a Rails Backbone alternative for Node, try Backbone.io
Adding for completeness: Meteor DDP: https://github.com/meteor/meteor/blob/master/packages/livedata/DDP.md
The best way to use it is to go all-in on Meteor; I doubt that the code is useful or usable outside of Meteor. The spec may be, though.
I wrote a set of libraries a little while back: http://github.com/Rekord/rekord
It also has all the features in a model library you would expect.
For real-time application development, currently, we have Derby and Tower.js
Just wanted to know if Linq to Nhibernate ready for production. I want to use it for a fairly large website and don't want it to blow up. Also, do I still have to setup XML or use fluent for the mappings?
You can use fluent for the mappings it is very reliable or you can make use of the automatic mappings but that tends to be a bit too much magic for a lot of people. The linq provider for NH2 is pretty sketchy but the provider for 3 is very good. I've been using it in production for some time and found only a couple of issues which where soon corrected.
I am looking at using a system with Cassandra as a backend, and I wanted to collect together common problems that people experience in production Cassandra environments with usual workarounds/solutions.
Could anyone tell me of their experiences, as I want to see what potential showstoppers/issues I need to think about.
http://www.riptano.com/docs/0.6/troubleshooting/index