Brick Wall time.
Last question - If I create a new server and migrate from the old - do I have to make sure the new is 4.4.x or can it go straight to 4.5.x?
There does seem to a db transform in the upgrade so I'm assuming it is not possible.
Brick Wall time.
Last question - If I create a new server and migrate from the old - do I have to make sure the new is 4.4.x or can it go straight to 4.5.x?
There does seem to a db transform in the upgrade so I'm assuming it is not possible.
I've been re-trying. One thing I notice is yarn install --immutable produces warnings:
➤ YN0060: │ react is listed by your project with version 18.3.1 (p68bdc1), which doesn't satisfy what emoji-mart-lazyload and other dependencies request (but they have non-overlapping ranges!).
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide postcss (pfe5f4d), requested by postcss-preset-env and other dependencies.
/ctd
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide redux (p7bebfc), requested by react-redux-loading-bar and other dependencies.
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide rollup (p04c650), requested by @optimize-lodash/rollup-plugin and other dependencies.
➤ YN0002: │ @mastodon/mastodon@workspace:. doesn't provide terser (pf7324a), requested by @vitejs/plugin-legacy and other dependencies.
/ctd
➤ YN0002: │ @mastodon/streaming@workspace:streaming doesn't provide eslint (p627553), requested by typescript-eslint.
I updated from yarn 4.10.3 to 4.11.0 but same result. Is this relevant?
Node 20.19
Ruby 3.3.7
Redis 7.4.1
Postgresql 15.2
Which should be ok.
Sorry typo Ruby 3.4.7
Using your RAILs command I get a lot of writing css & svg lines. Then :
.................
Building with Vite ⚡
pid 2060 exit 1
Build with Vite failed! ❌
.....................
This is what the end of my.env.production file looks like with the log level additions. Is there a semantic error?
ES_ENABLED=true
ES_HOST=localhost
ES_PORT=9200
MASTODON_USE_LIBVIPS=false
RAILS_LOG_LEVEL=info
LOG_LEVEL=info
This is still all I get:
RAILS_ENV=production bundle exec rails assets:precompile
I, [2025-11-20T18:21:38.544602 #1798] INFO -- : [dotenv] Loaded .env.production
WARNING: Mastodon support for ImageMagick is deprecated and will be removed in future versions. Please consider using libvips instead.
Building with Vite ⚡
pid 1819 exit 1
Build with Vite failed! ❌
Added:
RAILS_LOG_LEVEL=info
LOG_LEVEL=info
Nothing appeared in the live/log directory.
Thank you for helping
Help! Issue with 4.4.8 to 4.5.0 upgrade. The RAILS precompile command results in:
....................
Building with Vite ⚡
pid 1593 exit 1
Build with Vite failed!
.................
Not very informative. Repeated, rebooted closed all other services. The new requirements met. Debian Bullseye.
Any suggestions?
Updating 4.4.2 my post limit reverted to the default 500.
I followed the instructions here: https://yawnbox.is/blog/change-mastodon-post-and-bio-max-count/
However when I came to precompile it skipped saying no watch files had changed. Limit is still shown as 500
How do I force a precompile or should I wait for 4.4.3?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.