Starting up…

Failed a second time, apparently it now works _without_ that option set.

It used to be it'd fail to build unless I did set the "max old space size". This is a VM with 8GB of RAM… it did get an upgrade when the Atom C2000 issue was resolved on a couple of old boards meant I gained some extra […]

Trying again with `--max-old-space-size=512`.

```

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0xe38a0e node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0x120a5a0 v8::Utils::ReportOOMFailure(v8::internal::Isolate* […]

```
root@mastodon:~# nodejs --version
v22.21.0
```

…let's try that assets compile step again!

So the issue was `liburing1` not being available on Debian 12… and also `/etc/apt/sources.list.d/postgresql.list` still referencing Debian 11 repositories.

Not so much I'm "holding" broken packages, just the distribution has moved on. Now PostgreSQL v18 is installed and it'll attempt an update […]

```
root@mastodon:~# apt-get install -y postgresql
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution […]

In the midst of picking apart NodeSource's `setup_22.x` script so I can manually apply the changes without running a script as `root`… I see this:

```
The following packages have been kept back:
postgresql
```

I hate it when Debian does things without explaining what's going on.

```
Building with Vite ⚡
You are using Node.js 20.5.1. Vite requires Node.js version 20.19+ or 22.12+. Please upgrade your Node.js version.
failed to load config from /home/mastodon/live/vite.config.mts
error during build:
TypeError: crypto.hash is not a function
at file […]

`NODE_OPTIONS="--max-old-space-size=768" RAILS_ENV=production bundle exec rails assets:precompile`

The `--max-old-space-size=768` is needed here because `nodejs`' heap management sucks, it just `malloc`s until it hits `ENOMEM` then dies.

Oookay… onto the next step. `bundle install && yarn install --immutable`

To be fair, I saw the `rbenv install` and missed the other bit, due to the way the text wrapped.

Crap, forgot `RUBY_CONFIGURE_OPTS=--with-jemalloc`…

```
mastodon@mastodon:~/live$ rbenv install
==> Downloading ruby-3.4.7.tar.gz...
-> curl -q -fL -o ruby-3.4.7.tar.gz https://cache.ruby-lang.org/pub/ruby/3.4/ruby-3.4.7.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 22.1M 100 22.1M […]

There are times I wonder why I run Debian for a Mastodon host… I compile that much of it from source I might as well be running Gentoo.

Ahh, `rbenv` my nemesis, we meet again… time to pull v3.4.7 (from v3.2.3).

Migrations done… let's see if she'll start up.

```
==> Installed ruby-3.4.4 to /home/mastodon/.rbenv/versions/3.4.4

```

First hurdle cleared. Now for the next steps…

```
env NODE_OPTIONS="--max-old-space-size=768" RAILS_ENV=production sh -c 'bundle install && yarn install --immutable && bundle exec rails assets:precompile' && […]