Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 18:44:14
Mastodon 4.3.0 BETA 1 is finally here! https://github.com/mastodon/mastodon/releases/tag/v4.3.0-beta.1
Danny (@danny@strangeminds.social)
Föderation EN Fr 23.08.2024 19:02:03
@vmstan now it's in beta, I'm tempted to give it a go.
Currently on v4.2.12, is there anything that might catch me out?
Have wine to keep the stress levels down 🍷
Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 19:12:52
@danny it should be mostly painless coming from 4.2.12 so long as you are meticulous about following the upgrade steps in the release notes.
Danny (@danny@strangeminds.social)
Föderation EN Fr 23.08.2024 19:42:20
@vmstan ok, sorry to lean on you, but I *think* I have a problem
Upgrade to Yarn 4 doesn't appear to be doing anything when I do corepack enable / corepack prepare
mastodon@strangeminds:~/live$ corepack enable
mastodon@strangeminds:~/live$
mastodon@strangeminds:~/live$ corepack prepare
Preparing yarn@1.22.22...
Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 19:43:44
@danny what version of Node do you have installed and how did you install it?
Danny (@danny@strangeminds.social)
Föderation EN Fr 23.08.2024 19:45:57
@vmstan mastodon@strangeminds:~/live$ node -v
v20.17.0
I think the only reason it would've been installed is as part of the Mastodon install
Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 19:54:37
@danny is that with the 4.3 code checked out in that directory?
Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 19:58:27
@danny What do you get for corepack yarn --version
Danny (@danny@strangeminds.social)
Föderation EN Fr 23.08.2024 20:00:09
@vmstan mastodon@strangeminds:~/live$ corepack yarn --version
1.22.22
Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 20:00:31
@danny try and run corepack prepare yarn@4.4.0 --activate
Danny (@danny@strangeminds.social)
Föderation EN Fr 23.08.2024 20:02:05
@vmstan ok, now showing
mastodon@strangeminds:~/live$ corepack yarn --version
4.4.0
Does that look right?
Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 20:02:29
@danny yeah that should be correct.
Föderation EN Fr 23.08.2024 19:11:58
@vmstan Cool! Will there be updated helm charts for 4.3 as well? We're currently kind of stuck in an interim state with a hacked version of the old chart.
Michael Stanclift (@vmstan@vmst.io)
Föderation EN Fr 23.08.2024 19:13:15
@b2c I believe @renchap is/was working on those.
Föderation EN Fr 23.08.2024 19:16:38
Renaud Chaput (@renchap@oisaur.com)
Föderation EN Fr 23.08.2024 22:48:07
@b2c Do you have a specific issue with the current chart? This is the one we use for mastodon.social, and it support having a separate image for streaming.
There are plans (and work) to create a new (simpler) chart, but the current one can be used (and is used).
Föderation EN So 25.08.2024 18:50:39
@renchap@oisaur.com @renchap@mastodon.social : Took another look at the chart, and I have a quick question. With the hook "assetsPrecompile" I can disable the JS asset precompilation job I'd recon?
This would help us, since we run with self-built images that deliver all JS already compiled, since we apply some code customizations ourselves and ship our own images.
However, in e.g. https://github.com/mastodon/chart/blob/main/templates/deployment-sidekiq.yaml#L196 the assets get mounted, and there is no check for "assetsPrecompile". (Why do the sidekiqs even have the assets mounted btw?).
This would leave us with an empty assets folder, since we have the assets already compiled in our pod, and the mountpoint would be empty.
We also can't compile the assets at runtime since we run rootless with random UIDs on Openshift, so we would need a way for the chart to just ignore the whole asset part of the chart completely.
Can I configure the chart somehow to do that, or is this not possible?
CC: @vmstan
Michael Stanclift (@vmstan@vmst.io)
Föderation EN So 25.08.2024 18:56:30
@b2c @renchap@oisaur.com @renchap@mastodon.social the 4.3 Docker images don’t have the ability to do an asset recompile because Node has been removed. If you have something that requires it you’ll need to roll your own image ahead of time.
Föderation EN Mo 26.08.2024 13:47:20
Ok, thanks again for your insights.
My exact problem however is:
- I have no S3, but network storage (NFS)
- therefore I need the "system" volume
- however, I don't want the "assets" volume
I can't see how I can achieve that with the current chart. It's either "assets"+"system", or no storage at all.
Renaud Chaput (@renchap@oisaur.com)
Föderation EN Mo 26.08.2024 13:49:59
@b2c Yes, the current chart does not support it :(
I dont like that both of those volumes are tied to S3. If you want to improve this and open a PR, we will definitely consider it!
Pinging @timetinytim as he is maintaining the chart now.