# Update in browser vs Terminal
**URL:** https://meta.discourse.org/t/update-in-browser-vs-terminal/358717
**Category:** 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:** 5
**Page:** 2
### Author:  [@alltiagocom](https://meta.discourse.org/u/alltiagocom)
#### Post date: [March 26, 2025, 7:39pm UTC](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717/22 "2025-03-26T19:39:27Z")
I appreciate the info… unfortunately, I’m not on a level of expertise where any of that makes sense to me 😕
I will save this in my notes, though. Maybe one day all of it will make sense.
Thanks!
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [March 27, 2025, 5:35pm UTC](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717/23 "2025-03-27T17:35:30Z")
It’s always possible that an in-browser update will unexpectedly fail, so you should always choose a time when you can suffer the downtime you might need, and you can then fall back to a command line rebuild. (And you should take a backup and download it before you do anything.)
Sometimes, rarely, it can help to reboot the machine, especially if it has been running for a long time - a year or more - since reboot. You should also be applying package updates for security reasons, often they will advise a reboot.
I wouldn’t expect any great advantage in doing the swapoff/swapon but maybe it does no harm. Any space that you’ve apparently reclaimed can only have come from RAM, will probably have just cleared some caches, and they should have been managed automatically.
The real problem is that your 1G RAM + 2G swap was not enough. There’s a current thread about whether requirements have recently changed:
[Have Discourse’s requirements changed recently?](https://meta.discourse.org/t/have-discourses-requirements-changed-recently/358732)
---
### Author:  [@alltiagocom](https://meta.discourse.org/u/alltiagocom)
#### Post date: [March 27, 2025, 5:56pm UTC](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717/24 "2025-03-27T17:56:28Z")
Thank you for the extra info!
A lot of those are way above my level of expertise, but I saved your post in my notes to do some research eventually.
Right now I’m trying to deal with the basic configuration, trying to have the forum up and running, and with time I will be doing my research when it comes to more advanced stuff for sure.
Appreciate it! 🙌
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [April 4, 2025, 12:56pm UTC](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717/25 "2025-04-04T12:56:21Z")
This should help with future rebuilds:
> [@High rebuild memory requirements: April 2025 edition](https://meta.discourse.org/t/high-rebuild-memory-requirements-april-2025-edition/360419/10):
>
> We just landed [this commit](https://github.com/discourse/discourse/commit/ae2bc240af434168aeebe73d550b1c979ca3a29b) which should hopefully improve the situation. Please let us know how you get on! (it’ll hit tests-passed in the next ~30 mins) When testing with a memory-constrained docker container locally, I can now get a successful build with -m 1600m. Before this change, the minimum I could achieve was -m 3000m.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [May 4, 2025, 12:57pm UTC](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717/26 "2025-05-04T12:57:22Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
[Previous page](https://meta.discourse.org/t/update-in-browser-vs-terminal/358717.md?page=1)