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
Fully expand single cards in the sidebar #919
Comments
That's a part of the "focused annotation" concept, as described at #800. Closing this duplicate. |
8 tasks
nickstenning
added a commit
that referenced
this issue
Mar 11, 2015
This adds a docker-compose.yml, used (unsurprisingly) by docker-compose[1] to assemble an application out of multiple pieces. This configuration sets up a basic development environment for h, with the following services: - web (the application) - elasticsearch - nsqd At the moment postgres is not configured, and the application will default to using an SQLite database within the container. The simplest way to run this all at the moment is probably to start the services in the background first: docker-compose up -d elasticsearch nsqd And then start the web application without recreating the dependency containers. This is to work around docker-compose issue #919[2]. docker-compose up --no-deps --no-recreate web This will install development dependencies and start the web application. You can then visit the application at port 8000 on the docker host. [1]: https://docs.docker.com/compose/ [2]: docker/compose#919
nickstenning
added a commit
that referenced
this issue
Mar 12, 2015
This adds a docker-compose.yml, used (unsurprisingly) by docker-compose[1] to assemble an application out of multiple pieces. This configuration sets up a basic development environment for h, with the following services: - web (the application) - elasticsearch - nsqd At the moment postgres is not configured, and the application will default to using an SQLite database within the container. The simplest way to run this all at the moment is probably to start the services in the background first: docker-compose up -d elasticsearch nsqd And then start the web application without recreating the dependency containers. This is to work around docker-compose issue #919[2]. docker-compose up --no-deps --no-recreate web This will install development dependencies and start the web application. You can then visit the application at port 8000 on the docker host. [1]: https://docs.docker.com/compose/ [2]: docker/compose#919
nickstenning
added a commit
that referenced
this issue
Mar 12, 2015
This adds a docker-compose.yml, used (unsurprisingly) by docker-compose[1] to assemble an application out of multiple pieces. This configuration sets up a basic development environment for h, with the following services: - web (the application) - elasticsearch - nsqd At the moment postgres is not configured, and the application will default to using an SQLite database within the container. The simplest way to run this all at the moment is probably to start the services in the background first: docker-compose up -d elasticsearch nsqd And then start the web application without recreating the dependency containers. This is to work around docker-compose issue #919[2]. docker-compose up --no-deps --no-recreate web This will install development dependencies and start the web application. You can then visit the application at port 8000 on the docker host. [1]: https://docs.docker.com/compose/ [2]: docker/compose#919
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It strikes me that when when there's only a single card shown in the sidebar, because:
That we should go ahead and fully expand it, instead of forcing the second click.
Thoughts?
The text was updated successfully, but these errors were encountered: