Use development ID for independent Rails

NoSQL has many advantages,

Just

1. store any objects, images, files, and so on.

2. The same object storage is not restricted.

That's enough for me to hug.

So, go to ruby and check that there is a feeling that the consumer ID will gradually replace the consumer Mapper. Next I will use the consumer ID to make a record independently:

For yml configuration, if you want to use the rails project, you can also:

1. Development:
2. Host: localhost
3. Database: personal_center_development
5. Test:
6. Host: localhost
7. Database: personal_center_test 
8.  
9. # Set these environment variables on your prod server
10. Production:
11. Host: <% = ENV ['Upload ID _ host'] %>
12. Port: <% = ENV ['Upload ID _ port'] %>
13. Username: <% = ENV ['Upload ID _ username'] %>
14. Password: <% = ENV ['Your ID _ password'] %>
15. Database: <% = ENV ['Upload ID _ database'] %>

The following describes how to load:

1. Require'Upload id'
3. ENV ['Upload ID _ env'] ='Development'
5. # Replace it with the producer ID. yml directory you just created
6. Upload ID. load! ("../Config/consumer ID. yml")
8. # Optional. You can directly load the model if you want to reuse it.
9. Dir. Glob ("# {File. dirname (_ FILE _)}/../app/models/*. rb")Do| Lib |
10. Require lib
11. End
13. # Try to output OK
14. Puts User. all. size

Note that the above is hard to understand: MONGOID_ENV. In fact, it is added to support rails, sinatra, and so on. We can only do this when using it independently. You can try to see.

Note that the consumer ID must be at least 2.4.3 or above. There are many problems with the previous versions, and various exceptions may occur.

The good thing is that the consumer ID team is awesome, and the issues mentioned quickly responds.

At this point, the problem has been solved. If you have the problem, try again.

The official homepage of consumer ID is: http://mongoid.org/