# Making launcher a bit more versatile

**URL:** https://meta.discourse.org/t/making-launcher-a-bit-more-versatile/56851
**Category:** Feature
**Created:** [3 فبراير 2017، 9:15ص UTC](https://meta.discourse.org/t/making-launcher-a-bit-more-versatile/56851 "2017-02-03T09:15:49Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [3 فبراير 2017، 9:15ص UTC](https://meta.discourse.org/t/making-launcher-a-bit-more-versatile/56851/1 "2017-02-03T09:15:49Z")

</div>

launcher logs shows the whole log for the container, which can take a while to finish. How about changing the launcher logs command to take --tail the way that docker logs does?

---

<div class="post-metadata">

### Author: ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [3 فبراير 2017، 1:45م UTC](https://meta.discourse.org/t/making-launcher-a-bit-more-versatile/56851/2 "2017-02-03T13:45:29Z")

</div>

While I’m at it:

./launcher status app

returning:

Postgres: Up and running, unreachable.  
Version: Up to date, behind, updating.  
Web: Up, down, starting.  
Sidekick; Up, down  
Email:Up, Down  
Last error: Date/time of last Major error

The idea being that ./launcher becomes a one stop, “What is going on?” tool. Just enough to give a quick health check.

---

<div class="post-metadata">

### Author: ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [4 فبراير 2017، 9:35ص UTC](https://meta.discourse.org/t/making-launcher-a-bit-more-versatile/56851/3 "2017-02-04T09:35:03Z")

</div>

And another thing…

How about presenting the same sort of status information via the web, similar to the way that admin/upgrade#/processes

Again, a single point of reference giving “What is going on?” type of information.

---

<div class="post-metadata">

### Author: ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [22 فبراير 2017، 12:19م UTC](https://meta.discourse.org/t/making-launcher-a-bit-more-versatile/56851/4 "2017-02-22T12:19:14Z")

</div>

And another thing…

I’m just walking through removing the plugins one after the other to try and isolate [this problem](https://meta.discourse.org/t/strange-problem-with-data-explorer/57751).

It just occurred to me, there is no way to do ./launcher rebuild app without pulling the latest image from docker, right?

I’m trying to narrow in on a local problem, making local changes, but I am also pulling remote changes at the same time.

Any way to do something like ./launcher rebuild app --local\_only ?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [23 فبراير 2017، 1:04ص UTC](https://meta.discourse.org/t/making-launcher-a-bit-more-versatile/56851/5 "2017-02-23T01:04:02Z")

</div>

No, and nothing like this is planned for the forseeable future.
