Paul Chambers on Nostr: Last fall when I installed Mastodon I did so with 'yarn set version stable' but ...
Last fall when I installed Mastodon I did so with
'yarn set version stable' but Mastodon calls for classic.
Recently had conflict errors running RAILS_ENV=production bundle exec rails assets:precompile.
My current yarn version is 3.3.0.
Will I have any issues with my existing instance if I run
corepack enable
yarn set version classic
now? Also, I run that under root user not Mastodon user, correct.
My VPS is only used for Mastodon. Advice welcomed. Thanks.
#MastoAdmin #MastoDev #dev
Published at
2023-06-23 09:30:12Event JSON
{
"id": "0bc92239150562b457379582e082f6afe31dc9d971375a9371829c5f91f21c34",
"pubkey": "ff2fb9318e8d0ed9abf2c2deae3cd98be7a9177ff83051737bc032a0db02b7b6",
"created_at": 1687512612,
"kind": 1,
"tags": [
[
"t",
"mastoadmin"
],
[
"t",
"mastodev"
],
[
"t",
"dev"
],
[
"mostr",
"https://oldfriends.live/users/paul/statuses/110592826561470629"
]
],
"content": "Last fall when I installed Mastodon I did so with \n'yarn set version stable' but Mastodon calls for classic. \n\nRecently had conflict errors running RAILS_ENV=production bundle exec rails assets:precompile. \n\nMy current yarn version is 3.3.0.\n\nWill I have any issues with my existing instance if I run\n\ncorepack enable\nyarn set version classic\n\nnow? Also, I run that under root user not Mastodon user, correct.\n\nMy VPS is only used for Mastodon. Advice welcomed. Thanks.\n#MastoAdmin #MastoDev #dev",
"sig": "21a778cf02c807fd1df8533102f8c877546aff239264ea094ace5aee641c45b09e9b498bb844c3e0efebeba2abd338d1b4d1636552dc4a74b4661526a8de3182"
}