# Update in browser vs Terminal

**URL:** <https://meta.discourse.org/t/update-in-browser-vs-terminal/358717>\
**Category:** Product Support\
**Created:** [March 25, 2025, 7:55am UTC](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717 "2025-03-25T07:55:28Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [March 25, 2025, 11:38pm UTC](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717/21 "2025-03-25T23:38:30Z")

</div>

Rebuild from the command line takes less ram.

With a two container install, you can build a new container while the old one continues to work (if you have enough ram). That gives you little downtime.

You have to do a command line rebuild sometimes because underlying libraries need to be updated and those can’t be done from the ux.

You can

```plaintext
cd /var/discourse
grep swap discourse-setup

```

to see the commands that it does to create the swap. If you run `swapoff` (so that the file is no longer busy) you can then run the commands that create the file `(fsallocate)` making it bigger, if desired, and format it as swap `(mkswap)` and then `swapon -a` to turn it back on.

If you’ve got many plugins you likely need a total of 5 or 6gb.

---

_[View the full topic](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717)._