[umami] Guide is broken

[kimdiallo]

The yarn build process cannot get past nextjs - every time the build script calls pnpm, the OOM-killer strikes - even when trying to build nextjs in advance in isolation and with garbage collection limitation.

We label the guide “broken” for the time being and remove it completely if nobody finds a workaround in time.

// @foxytocin

[cybacoffee]

Current workaround would only be, to build the app locally :/ https://github.com/umami-software/umami/issues/1539.

Or maybe uberspace is increasing the current memory limit for nodejs?

[amxmln]

I’ve been tinkering with a solution. I believe the issue is that Next sees about a bajillion available threads and the entire system RAM when building and so tries to access them all. This means that the max_old_space for Node is applied to each worker, not the entire process, causing it to go wildly beyond that limit.

I have been successful in building with the following settings added to next.config.js:

{
  experimental: {
    cpus: 1,
    workerThreads: false,
  }
}

It still seems a bit brittle and apparently v3 of Umami is in the works, which might change things up again, but for the time being you’re welcome to try this workaround.

[nikolasdas]

I can't even install the dependencies... I've tried npm, yarn and pnpm, without any success :/

[amxmln]

@nikolasdas I had trouble with that as well, pnpm kept getting killed because for some reason it uses tons of memory, perhaps for a similar reason, i.e. it sees the entire system memory and thinks it can use all that?

Restarting the installation process a couple times worked for me, eventually.