Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doc improvement for docker-compose #1380

Closed
wants to merge 0 commits into from
Closed

Doc improvement for docker-compose #1380

wants to merge 0 commits into from

Conversation

antgel
Copy link

@antgel antgel commented Nov 9, 2016

No description provided.

Copy link
Member

@arikfr arikfr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Docs improvements are always appreciated.

Please see my comments & please apply them to https://github.com/getredash/website/blob/master/onpremise/setup/setting-up-redash-instance.md as the docs moved there... (you submitted the pull request right before me deleting the docs folder).

(``$REDASH_DIR`` refers to the top-level directory of your Redash git repository clone.)

#. Install docker and docker-compose.
#. ``cd $REDASH_DIR``.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not keep the original instruction (#2 above)? I find it much more understandable than this. You don't use $REDASH_DIR anywhere else anyway.


First ssh to your instance and change directory to ``/opt/redash``. If
you're using the GCE image, switch to root (``sudo su``).
First connect to your instance using ssh, and switch to root (``sudo su``).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the change?

#. ``cd $REDASH_DIR``.
#. ``cp docker-compose-example.yml docker-compose.yml``
#. ``docker-compose up postgres``.
#. Change to another terminal.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why?

you're using the GCE image, switch to root (``sudo su``).
First connect to your instance using ssh, and switch to root (``sudo su``).

If you're using the Docker image, ``docker exec -i -t redash_redash_1 /bin/bash``, will put you in ``/opt/redash/current`` as root.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. They should use Compose's exec. This way no need to assume that the name will be redash_redash_1.
  2. I'm not sure this is needed. Is there a change they can'tdo via the env variables?

Most of the settings you need to edit are in the ``/opt/redash/.env``
file.
Most of the settings you need to edit are in the ``/opt/redash/current/.env``
file. If it doesn't exist, ``cp /opt/redash/current/.env.example /opt/redash/current/.env``.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instructions assume you either use one of the provided images or the bootstrap script. The .env File will always be there and /opt/redash/current/.env is a symlink to /opt/redash/.env (so it's not lost when upgrading).

Note that for Docker you should not use the .env file but rather Docker's env variables.

@antgel antgel closed this Nov 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants