# What's the different between rebuild and bootstrap

**URL:** <https://meta.discourse.org/t/whats-the-different-between-rebuild-and-bootstrap/60315>\
**Category:** Self-hosting\
**Created:** [02.Апрель.2017 10:42:51 UTC](https://meta.discourse.org/t/whats-the-different-between-rebuild-and-bootstrap/60315 "2017-04-02T10:42:51Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [03.Апрель.2017 13:19:43 UTC](https://meta.discourse.org/t/whats-the-different-between-rebuild-and-bootstrap/60315/9 "2017-04-03T13:19:43Z")

</div>

> [@mpalmer](#):
>
> “stuff that gets configured on container start”.

Just a minor point for other people reading, not for @mpalmer who knows all this stuff 🙂 . Nothing gets configured on container “start”, only on container “create”.

So, for example,

```plaintext
./launcher stop app
./launcher start app

```

Will **not change** anything in the environment.

Stuff gets configured on container creation, which means that there needs to be **no pre-existing container** on the machine when you run `start`

There are indeed ways of using ENV to bootstrap bits of hardcoded data in the container image. However we really should prefer `params` here.

I always found this distinction to be just way to subtle for people to comprehend which is why I always ask people to do `./launcher rebuild` and forget about all the nuance and edge caseyness here.

---

_[View the full topic](https://meta.discourse.org/t/whats-the-different-between-rebuild-and-bootstrap/60315)._