3 ms·

The admin interface has a convenient “Setup” menu point that does all this for you :)

• eriknstr 10y ago
  Thank you both. I assumed that the messages indicated critical error which would mean that CouchDB was not in a running state but indeed the system is running and the admin interface is reachable at 127.0.0.1:5984/_utils/ where the setup can be completed.
  • janl 10y ago
    It didn't make the cut for 2.0.0, but we definitely should have a nice message there on the command line. Sorry about that! :)
    • eriknstr 10y ago
      No worries. Deciding it was time to play with CouchDB once again, I just spent the last few hours moving a little side-project I'm working on over from PostgreSQL to CouchDB 2.0. I liked CouchDB last time I tried it but then forgot about it for a while, and aside from that little bit of confusion, CouchDB 2.0 has held up to your motto -- "time to relax!". Well, "moving over" might be a slight exaggeration seeing as how my little project is in such early inception that all I had prior to switching it over to CouchDB 2.0 was a few SQL-files defining the schema of various tables, as well as a couple of other SQL-files with queries to run and a bit of sample data. But anyway, the point still stands that said little project is now using CouchDB.
  • janl 10y ago
    It didn't make the cut for 2.0.0, but we definitely should have a nice message there on the command line. Sorry about that! :)