Incomplete Instructions

[daddydrac]

After you go thru the instructions it stops at cookie cutter install vars. What do you do next?

[csajedi]

Once you get a cookiecutted project the Readme is actually different from the readme on this repo. You can see the basic command docker-compose up -d and other useful help info in the root README.md. If you're not sure how to view locally, I can recommend grip

[daddydrac]

I figured it out but the build breaks and nginx returns a 500.

On Tue, Feb 25, 2020 at 12:47 PM Cameron Sajedi notifications@github.com wrote:

Once you get a cookiecutted project the Readme is actually different from the readme on this repo. You can see the basic command docker-compose up -d and other useful help info in the root README.md. If you're not sure how to view locally, I can recommend grip https://github.com/joeyespo/grip

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tiangolo/full-stack-fastapi-couchbase/issues/25?email_source=notifications&email_token=ABHVQHGQXM5CBWUILMCK6WDREVRT3A5CNFSM4KWFSST2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM5A3MI#issuecomment-591007153, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHVQHD2FTYMHBM7VBAOEP3REVRT3ANCNFSM4KWFSSTQ .

[csajedi]

weird, are you doing it all at the top level with docker-compose?

[daddydrac]

Mine is still breaking and yes.

[tiangolo]

Thanks for the help @csajedi ! :cake:

@joehoeller you should probably check your logs to see your internal errors. Without more info we can't really help you.

[csutera]

I can successfully start the containers with docker-compose up -d but the backend container keeps choking on ensure_couchbase_username_password. Once I created the couchbase cluster and bucket from the couchbase UI, the logs show the backend retrying and failing on INFO:app.db.couchbase_utils:before ensure_couchbase_username_password ERROR:__main__:

300 times then

ERROR:__main__:
WARNING:__main__:Finished call to '__main__.init' after 314.936(s), this was the 300th time calling it.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/tenacity/__init__.py", line 394, in call
    result = fn(*args, **kwargs)
  File "/app/app/backend_pre_start.py", line 25, in init
    raise e
  File "/app/app/backend_pre_start.py", line 22, in init
    init_db()
  File "/app/app/db/init_db.py", line 30, in init_db
    port=config.COUCHBASE_PORT,
  File "/app/app/db/couchbase_utils.py", line 277, in config_couchbase
    cluster_url=cluster_url, username=username, password=password
AssertionError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/app/backend_pre_start.py", line 35, in <module>
    main()
  File "/app/app/backend_pre_start.py", line 30, in main
    init()
  File "/usr/local/lib/python3.7/site-packages/tenacity/__init__.py", line 311, in wrapped_f
    return self.call(f, *args, **kw)
  File "/usr/local/lib/python3.7/site-packages/tenacity/__init__.py", line 391, in call
    do = self.iter(retry_state=retry_state)
  File "/usr/local/lib/python3.7/site-packages/tenacity/__init__.py", line 351, in iter
    six.raise_from(retry_exc, fut.exception())
  File "<string>", line 3, in raise_from
tenacity.RetryError: RetryError[<Future at 0x7ff92b7e41d0 state=finished raised AssertionError>]

I left the username, password, host, port (8091) at their defaults. Thanks for all of the logging :). Any ideas on where to go from here?

[csutera]

I put this here because I suppose i'm missing some key step that I didn't see in the documentation.

[csutera]

I got it running. The couchbase user I created through the cb UI had a different password than the one the for sync-gateway created when I first ran the cookiecutter init.

[tiangolo]

If you are still having issues with a new project, you might try to remove everything with:

$ docker-compose down -v

...the -v removes the volumes, so you start with an empty DB, without a password set up.

[github-actions[bot]]

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.