# Bootstrap && destroy && start

**URL:** <https://meta.discourse.org/t/bootstrap-destroy-start/351354>\
**Category:** Self-hosting\
**Tags:** two-container\
**Created:** [February 9, 2025, 6:55pm UTC](https://meta.discourse.org/t/bootstrap-destroy-start/351354 "2025-02-09T18:55:14Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\
**Post date:** [February 9, 2025, 6:55pm UTC](https://meta.discourse.org/t/bootstrap-destroy-start/351354/1 "2025-02-09T18:55:14Z")

</div>

This is very 101-level question.

I have two container setup waiting for some peaceful moment to fire it up.

But why this is always guided:

```plaintext
./launcher bootstrap .. && ./launcher destroy .. && ./launcher start ..

```

I kind of understand that when it is done like first time — ok, let’s be honest: I don’t understand the differences between bootstrap and rebuild at all, but the all mighty AI told me I should do bootstrapping when there is the first time, because it is some weird dev-staff, and after that, everytime, rebuild is just fine.

So… why not `./launcher rebuild web_only` and that’s it? Because if I do destroying first I don’t have nothing to re-start if rebuilding fails, right?

I understand if I update everything, I have to stop web\_only first, then do data and the last one is web\_only

---

_[View the full topic](https://meta.discourse.org/t/bootstrap-destroy-start/351354)._