Compare commits

...
149 Commits
Author SHA1 Message Date
github-actions[bot] f1f6fecf44 Bump versions for v9.89 2026-07-13 16:25:58 +00:00
Lauri Ojansivu 6cb4ae2d64 Updated ChangeLog. 2026-07-13 19:24:47 +03:00
Lauri Ojansivu 3ecb90fc04 package-lock.json: record hasInstallScript for yargs postinstall patch
The postinstall script (scripts/patch-yargs-dirname.cjs) added in 6b409c5da
to fix the Meteor/Mocha test boot crash makes npm mark the root package with
hasInstallScript: true. Sync the lockfile to match package.json.
2026-07-13 19:19:10 +03:00
Lauri Ojansivu dc135f6e7d SortBleed (GHSA-xm8x-c8wg-jhmf): board sort allow rule privilege escalation
A low-privilege (comment-only / read-only) board member could escalate to
board admin and take over a private board via the board 'sort' collection
allow rule. To support drag-to-reorder, a second Boards.allow({ update })
rule returned true for any board member whenever the update touched the
'sort' field. Meteor applies the WHOLE modifier once any allow rule approves
and no deny rule rejects, and does not scope the approving rule to the field
that satisfied it. Because canUpdateBoardSort only checked that 'sort' was
AMONG the modified fields, a restricted member could smuggle arbitrary board
mutations (members, permission, title) into the same $set as 'sort' in one
DDP Boards.update call, making themselves admin, flipping the private board
to public, and evicting the legitimate owner. The last-admin deny rule only
inspected $pull, so a wholesale $set of the members array bypassed it.

Fix: restrict canUpdateBoardSort so the sort-reorder rule approves an update
only when 'sort' is the sole modified field. Defense in depth: the last-admin
deny rule now also rejects a $set rewrite of the members array that would
drop the last active admin. Regression test covers the multi-field smuggling
case. The legitimate All Boards drag-reorder is unaffected: it persists order
per-user in profile.boardSortIndex, not in the board document.

CVSS:3.1 8.8 High (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), CWE-863, CWE-269.
Thanks to 5ud0 / Tarmo Technologies and xet7.
2026-07-13 19:08:29 +03:00
Lauri Ojansivu 5b8e47649e Updated translations. 2026-07-13 18:34:58 +03:00
Lauri Ojansivu fb1df544dd Updated translations. 2026-07-13 18:29:09 +03:00
Lauri Ojansivu f031b885d7 CI: add meteor-spk.yml (build the meteor-spk bundle) and sandstorm-store.yml (publish .spk)
- .github/workflows/meteor-spk.yml: assembles WeKan's modernized meteor-spk (the
  packaging tool + its meteor-spk.deps: Node 24, FerretDB, Mongo 3.x CLIs, modern
  sandstorm-http-bridge) via sandstorm-src/build-deps.sh — reusing sandstorm.yml's
  setup — and zips it as meteor-spk-YYYY-MM-DD_HH_MM_SS.zip, the same kind of
  self-contained bundle sandstorm-io/meteor-spk releases but with WeKan's deps baked in.
  Uploaded as an artifact and to the newest GitHub Release. Needs no keyring (it does
  not pack/sign a .spk).

- .github/workflows/sandstorm-store.yml: publishes an already-built .spk to the
  Sandstorm App Market. Installs Sandstorm + assembles meteor-spk and restores
  SANDSTORM_KEYRING like sandstorm.yml, downloads the newest .spk from the WeKan release
  (built and attached by sandstorm.yml), renames it to wekan-<VERSION>.spk (VERSION from
  the release tag, e.g. 9.88, overridable via inputs), and runs 'spk publish
  wekan-<VERSION>.spk' exactly like releases/release-sandstorm.sh. Does not rebuild the
  .spk.

Thanks to xet7.
2026-07-13 14:53:57 +03:00
Lauri Ojansivu a4c1ce3d41 meteor test: patch ALL yargs files' import.meta, not just esm.mjs
The crash moved from yargs/lib/platform-shims/esm.mjs to yargs/build/lib/utils/
apply-extends.js (import.meta.resolve(config.extends)) — yargs' ESM build has more than
one file using import.meta. Rewrite the workaround to scan the whole node_modules/yargs
tree and rewrite every ESM-only construct (import.meta.url/.resolve/.dirname/.filename,
const require = createRequire(...), and yargs' own const __dirname) to the CommonJS
wrapper equivalents in one pass, so a new yargs file can't reintroduce the boot crash.
yargs is never executed at runtime here, so only valid CommonJS parsing matters.

Thanks to xet7.
2026-07-13 14:46:01 +03:00
Lauri Ojansivu 5b0ad4d334 meteor test: also rewrite yargs esm.mjs import.meta / require for the CommonJS wrapper
Renaming only __dirname was not enough: yargs' esm.mjs also uses import.meta.url (invalid
in Meteor's CommonJS module wrapper -> 'Cannot use import.meta outside a module') and
redeclares require via createRequire(import.meta.url) (collides with the wrapper's
require). reify rewrites the file's import statements but not import.meta. Rewrite all
three to use the wrapper's __filename / __dirname / require, which yargs never actually
exercises here (it is only bundled, never called). Idempotent; also patches a file left
half-rewritten by the previous version of this script.

Thanks to xet7.
2026-07-13 14:39:17 +03:00
Lauri Ojansivu 6b409c5dad meteor test: postinstall patch renames yargs esm.mjs __dirname (fixes Mocha boot crash)
.meteorignore does not apply to node_modules under Meteor 3 / rspack (verified: the
rebuilt Mocha bundle still contained node_modules/yargs), so revert that no-op rule and
fix the actual crash instead.

Root cause (pre-existing, unrelated to app code): the whole yargs package gets pulled
into the server bundle as a transitive devDependency, and its ESM shim
node_modules/yargs/lib/platform-shims/esm.mjs declares a top-level
'const __dirname = fileURLToPath(import.meta.url)'. Meteor wraps that .mjs in a CommonJS
module function that already provides __dirname, so it collides —
'SyntaxError: Identifier __dirname has already been declared' — crashing the server
bundle at boot, which is why Mocha reported 0 tests.

Add scripts/patch-yargs-dirname.cjs, run from a package.json postinstall, which renames
yargs' local __dirname (and its .substring/.lastIndexOf uses) to __dirnameYargs so it can
no longer collide with the wrapper's. Idempotent and best-effort (never fails install);
yargs is not used at runtime here so the rename is inert for the app.

Thanks to xet7.
2026-07-13 14:14:32 +03:00
Lauri Ojansivu 298ffcfd3b meteor test: exclude i18next-sprintf-postprocessor/rollup.config.js so yargs is not bundled
'meteor test' (Mocha) crashed at boot with 'Identifier __dirname has already been
declared'. Root cause is unrelated to app code: node_modules/yargs/lib/platform-shims/
esm.mjs declares a top-level 'const __dirname = fileURLToPath(import.meta.url)', which
collides with the __dirname that Meteor's CommonJS module wrapper already provides. yargs
gets pulled into the bundle only because i18next-sprintf-postprocessor (imported by
imports/i18n/tap.js) ships a stray rollup.config.js that does require('yargs'), and a
devDependency (mongodb) has since installed yargs 18 into node_modules so that require now
resolves. That build config is not part of the package's runtime entry
(index.js -> dist/commonjs), so exclude it from Meteor's bundle via .meteorignore.

Pre-existing (the same boot crash happened before this branch's test work) and independent
of the avatar/import-export feature.

Thanks to xet7.
2026-07-13 09:16:33 +03:00
Lauri Ojansivu cf217784d1 Fix Mocha boot crash (test __dirname) and load the new avatar/import-export server files
Two build/load fixes surfaced by running the full test suite:

- server/imports.js: import the new server-only files so they actually load. In
  mainModule mode a file not imported here never loads, so Accounts.onLogin avatar
  localization (server/avatarLocalizationOnLogin.js) and the imported-user reconciliation
  Meteor methods (server/importedUserReconciliation.js) would silently never register.

- Test __dirname collision: 'meteor test' crashed at boot with 'Identifier __dirname has
  already been declared'. The client test index (client/lib/tests/index.js) loads
  boardTriggersClass.tests.js, which referenced the bare __dirname global; under
  meteor test that makes Meteor inject a  colliding with its CommonJS
  wrapper's, aborting the whole server bundle (the same failure already fixed once in
  dependencies.openapi.tests.js — this was the next file to trip it). Replace __dirname
  with a process.cwd()/PWD walk-up in boardTriggersClass.tests.js, and defensively in the
  node-run tests/rtl.test.js, tests/stickers.test.js and tests/stickers.packs.test.js too.

Thanks to xet7.
2026-07-13 09:16:33 +03:00
Lauri Ojansivu bb7fe88bd5 Tests: unit + negative tests for the avatar/import-export feature; extract pure logic
Split the testable, security- and correctness-critical logic of the new avatars +
original-members feature into pure Node modules (module.exports, no Meteor) and cover them
with plain-Node tests/*.test.cjs (positive AND negative), matching the repo's existing
unit-test style. Wired into the test:unit:node script.

- models/lib/avatarUrlSafety.js  (from server/lib/localizeAvatar.js): isExternalAvatarUrl,
  isBlockedIp (SSRF ranges), decodeDataUri, checkUrlHostSync. Tests assert external vs
  local/relative/non-http URLs, that private/loopback/link-local/CGNAT/metadata/multicast
  IPv4+IPv6 (incl. IPv4-mapped) are blocked while genuine public addresses and near-miss
  ranges are allowed, data: decoding, and that non-http(s) schemes, localhost and
  metadata hosts are rejected.
- models/lib/importedUserReconciliationPlan.js (from server/importedUserReconciliation.js):
  planReconciliation. Tests: matches merge, non-matches deactivate, never match another
  placeholder or self or a username-less placeholder.
- packages/wekan-ldap/server/ldapPhoto.js (from sync.js): getLdapPhotoBuffer. Tests the
  Buffer / array / {type:'Buffer'} / base64 shapes and jpegPhoto>thumbnailPhoto, and that
  missing/empty/short values yield null (never throw).
- models/lib/importedBoardMemberPlan.js (from wekanCreator.js): planImportedBoardMember.
  Tests: unmapped member kept by original id but inactive+non-admin, mapped role preserved,
  importer and id-less members dropped.

The extractions are behaviour-preserving; the app modules now import these helpers.

Thanks to xet7.
2026-07-13 09:16:33 +03:00
Lauri Ojansivu ffc6652be0 Changelog: avatars + original members travel with a board across export/import and identity sources
Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu db90fb9e61 Members: distinguish imported placeholders and inactive members on the avatar + sidebar (Increment 5)
Make it obvious which board members are backed by a real account and which are not,
both on card avatars and in the right sidebar member list.

- userAvatar (js/jade/css): the avatar gets an 'imported-member' class (dashed grey ring
  + amber '?' corner badge) for un-reconciled board-import placeholders
  (authenticationMethod:'imported'), and an 'inactive-member' class (greyscale + dim +
  grey badge) for members deactivated on the board (e.g. a person not in LDAP after
  reconciliation). A placeholder is usually both; a real active account gets neither. The
  tooltip explains the state.
- boards.js membersForSidebar(): active members first (as before) then the inactive /
  imported ones appended, and sidebar.jade uses it, so the member list shows EVERYONE and
  which are active vs not instead of hiding inactive members.
- i18n: imported-member-no-account, inactive-member.

Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu 6784726bac Imported users: reconcile placeholders with valid accounts, admin merge (Increment 4)
server/importedUserReconciliation.js turns the inert import placeholders into the right
real members deliberately, after import — never auto-mapped during import.

- reconcileImportedUsers(): for each authenticationMethod:'imported' placeholder, find a
  real account with the same username (not another placeholder) — the valid accounts are
  whatever real WeKan accounts exist, typically provisioned by LDAP/OIDC at login — and
  merge the placeholder into it; if none exists (e.g. the person is not in LDAP) leave the
  placeholder and its board memberships inactive (isActive:false).
- mergeImportedUserInto(placeholderId, targetId): reassign every reference (board.members,
  card.members, card.assignees, activities.userId, cardComments.userId) from the
  placeholder to the target, reusing the target's membership if it already is a member,
  then remove the placeholder.
- Admin-only Meteor methods reconcileImportedUsers and mergeImportedUser(placeholderId,
  targetId) for the automatic sweep and for one-off deliberate mapping.

Because reconciliation matches against existing real accounts (which LDAP populates on
login) it needs no direct LDAP query and is provider-agnostic. Merges reassign by the
preserved original _id, so nothing is lost.

Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu 0c4b8f4d93 Board import: preserve original members as inert placeholder users, no mapping (Increment 3)
Importing a WeKan board no longer collapses unmapped members onto the importing user (a
wrong mapping attaches the wrong person and can leak board permissions). Instead each
original member carried in board.users becomes an inert placeholder user:

- createPlaceholderUsers() reuses the ORIGINAL _id, so every card/comment/activity
  member reference resolves to the right person with no remapping, and populates
  this.members as an identity map (id -> id) so _user() keeps the original member.
- Placeholders are created with Users.direct.insertAsync (bypassing the after.insert
  hooks — Sandstorm identity sync and the disableRegistration/invitation-code gate that
  would otherwise reject a non-account user), marked authenticationMethod:'imported',
  loginDisabled:true, isActive:false, and carry NO password or email. Username collisions
  suffix the placeholder's name so an existing account is never renamed/stolen.
- The member's avatar (embedded as base64 by the exporter) is restored into files/avatars
  via the localizer, so the original picture shows and is exportable again (Sandstorm too).
- Board membership adds imported members inactive and non-admin, so they are visible but
  hold no permissions until deliberately reconciled later; the importer stays sole admin.

Also guard the Sandstorm Users.after.insert hook to no-op on users without
services.sandstorm (placeholders), which otherwise threw reading preferredHandle.
Mapping/merging to real accounts and LDAP reconciliation are a later, deliberate step.

Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu b98abe7b00 Board export: embed each member's local avatar file as base64 (Increment 2)
Board export already carried the original members' username, fullname and initials (the
field whitelist excludes passwords, emails and services). Now, for each member whose
avatar is a local WeKan file, embed the file itself as base64 (profile.avatarFile +
avatarFileName + avatarFileType) alongside the existing avatarUrl reference, in both the
in-memory build() and the streaming buildStream() paths.

Because this reads a local avatars file (no outbound fetch), it works inside a Sandstorm
grain too: a board that already has many stored avatars can be exported with every
member's picture intact, ready to re-import elsewhere. External, not-yet-localized
avatars are still exported as their URL only (Increment 1 localizes those into files
first, on board open / at login).

Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu e0c76099f0 Avatars: import LDAP jpegPhoto and OIDC picture at login, localize on every login
Second set of triggers so external avatars from identity providers become local WeKan
avatars (files/avatars), shown in WeKan and carried by board export/import.

- LDAP (packages/wekan-ldap/server/sync.js): syncUserData now reads the binary
  jpegPhoto / thumbnailPhoto (tolerating Buffer / array / {type:'Buffer',data} / base64
  shapes) and, unless the user already has a locally-stored avatar, stores it as a
  self-contained data: URI in profile.avatarUrl. That displays immediately and needs no
  coupling from this package to app code; the app then materialises it to a real file.

- OIDC (packages/wekan-oidc/oidc_server.js): capture the standard  claim (with
  an OAUTH2_AVATAR_MAP override) into serviceData and set profile.avatarUrl for new users.

- App (server/avatarLocalizationOnLogin.js): Accounts.onLogin localizes the logging-in
  user's external avatar immediately (provider-agnostic), complementing the board-open
  trigger. Fire-and-forget, idempotent, never blocks login. (Inside a Sandstorm grain
  outbound fetch is sandboxed, so a Sandstorm profile picture is a best-effort no-op here
  and needs client-assisted capture — a later step.)

Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu b4bfc75947 Avatars: localize board members' external avatars when a board is opened
First trigger for external-avatar localization: the single-board publication
(publishComposite('board')) now fires a best-effort, fire-and-forget
localizeBoardMemberAvatars(boardId). For every member whose profile.avatarUrl points
outside WeKan, it copies the image into WeKan's own files/avatars (via the SSRF-guarded
helper) and repoints avatarUrl at the local copy. Idempotent (already-local avatars are
skipped) and it never blocks or delays the publication.

This is the universal catch-all: no matter how a member's avatar became external
(OAuth2/OIDC picture URL, gravatar, a pasted URL), opening the board makes it a local,
exportable WeKan avatar. (Note: inside a Sandstorm grain outbound fetch is sandboxed, so
Sandstorm profile pictures need the provider-side capture added next; LDAP jpegPhoto is
binary and is imported at login, also next.)

Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu dcd5f8fdd5 Avatars: add SSRF-guarded external-avatar localization helper (foundation)
First piece of making external avatars (Sandstorm profile pictures, LDAP jpegPhoto,
OAuth2/OIDC picture claims, gravatar, any URL/data-URI) into local WeKan avatar files
under WRITABLE_PATH/files/avatars, so they display without the identity provider and are
carried by board export/import.

server/lib/localizeAvatar.js:
- isExternalAvatarUrl(url): true unless already a local /cdn/storage/avatars/ (or legacy
  /cfs/files/avatars/) URL.
- localizeAvatarFromBuffer(userId, buffer, {type,name}): write bytes into the Avatars
  FilesCollection (onAfterUpload sets the user's local profile.avatarUrl).
- localizeAvatarFromUrl(userId, url): fetch (or decode a data: URI) then store.
- localizeUserAvatarIfExternal(user): idempotent no-op when already local.

Every network fetch is SSRF-guarded: http/https only; the host is resolved and any
private, loopback, link-local, CGNAT, multicast or cloud-metadata (169.254.169.254)
address is refused; 8s timeout; 5 MB cap; image content-type only. Not wired to any
trigger yet (board-open / export / login flows come next).

Thanks to xet7.
2026-07-13 09:16:32 +03:00
Lauri Ojansivu 7273220780 Updated ChangeLog. 2026-07-13 06:05:29 +03:00
Lauri Ojansivu 0d90011aff Update Sandstorm WeKan info.
Thanks to xet7 !
2026-07-13 06:04:50 +03:00
Lauri Ojansivu 2df6a77072 Updated ChangeLog. 2026-07-13 05:58:50 +03:00
Lauri Ojansivu ade9f16db4 Update Sandstorm WeKan info.
Thanks to xet7 !
2026-07-13 05:57:00 +03:00
Lauri Ojansivu 8cbfe3daee Updated ChangeLog. 2026-07-13 05:47:57 +03:00
Lauri Ojansivu 1bf68f54b2 Update Sandstorm WeKan info.
Thanks to xet7 !
2026-07-13 05:46:24 +03:00
github-actions[bot] 619eda0a9d Bump versions for v9.88 2026-07-13 02:12:35 +00:00
Lauri Ojansivu 3d2ab08294 Updated ChangeLog. 2026-07-13 05:10:47 +03:00
Lauri Ojansivu 6a12d968e0 Updated ChangeLog. 2026-07-13 05:05:53 +03:00
Lauri Ojansivu 9f23e6384b Added docs about new Sandstorm WeKan.
Thanks to xet7 !
2026-07-13 05:03:36 +03:00
Lauri Ojansivu 5d44e0b98b Sandstorm: remove the temporary MongoDB-3->FerretDB debugging diagnostics
Now that the grain boots, logs in, lists/opens boards, uploads/downloads attachments,
and migrates an old MongoDB 3 grain end to end, drop the two temporary diagnostics:

- models/attachments.js: revert the Meteor-Files debug flag to false (it was enabled on
  Sandstorm to trace the upload 'session expired [408]' issue and was spamming the grain
  log with the full FilesCollection dump and every find()).
- server/ferretdbQueryDebug.js: remove the mongodb Collection.find wrapper that logged
  FerretDB-rejected selectors (used to find the $elemMatch 'unknown operator: userId'
  issue, since fixed in wekan/FerretDB).

Thanks to xet7.
2026-07-13 04:11:22 +03:00
Lauri Ojansivu e65e06865a Changelog: Sandstorm/Snap migration modern driver, Meteor-Files GridFS + v1 binary, auto-open All Boards
Thanks to xet7.
2026-07-13 03:57:47 +03:00
Lauri Ojansivu b8bdbcd2d7 Sandstorm/Snap migration: auto-open All Boards after migration; WeKan-themed dashboard
Two UX requests once the migration itself works end to end:

- Auto-open All Boards. Previously the dashboard sat on the grain URL for 60s after
  completion and the admin had to reload to reach WeKan. On success the importer now
  exits after ~5s (long enough for the browser to fetch the done page), and the done
  page runs a JS poller that fetches '/' until WeKan's app shell answers (tolerating the
  brief importer->WeKan port hand-off gap) and then location.replace('/') opens All
  Boards. The spinner keeps spinning through the hand-off so it is clear the grain is
  still working; no meta-refresh on the done page (a refresh mid-hand-off would hit a
  dead port). On failure it still stays up a minute with the errors.

- WeKan colours. Recolour the dashboard from the dark scheme to WeKan's blue/white/grey
  (belize blue #2980b9 headings and spinner, white card on light-grey background, grey
  borders, system font).

Thanks to xet7.
2026-07-13 03:57:11 +03:00
Lauri Ojansivu 3476cd17c7 Sandstorm/Snap migration: extract Meteor-Files GridFS attachments + parse legacy v1 binary
With text collections migrating, the 3 attachments still produced 0 extracted files and
errors like 'parse attachments.chunks: Unexpected Binary Extended JSON format
{"$binary":"iVBOR..."}'. Two causes, both fixed:

1. Legacy Extended JSON v1 binary. mongo 3.x mongoexport writes binary as
   {"$binary":"<b64>","$type":"00"} (v1), but modern bson EJSON.parse only
   accepts v2 {"$binary":{"base64":...,"subType":...}}. Rewrite v1 -> v2 per line
   before parsing, so chunk data (and any binary in text collections) parses.

2. Meteor-Files native GridFS buckets were unhandled. The grain stores attachments in
   attachments.files + attachments.chunks (FilesCollection record in the attachments
   collection), not CollectionFS's cfs_gridfs.*. Reassemble those buckets to disk,
   linking each GridFS file to its record via metadata.fileId/versionName, then repoint
   the migrated record's versions.<v> at the file and DROP versions.<v>.meta.gridFsFileId
   — otherwise WeKan's getFileStrategy keeps choosing the (now-empty) GridFS backend and
   the image 404s. Also exclude <bucket>.files/.chunks (and tempstores) from the text
   migration so binary chunks are no longer run through EJSON as documents.

Thanks to xet7.
2026-07-13 03:28:13 +03:00
Lauri Ojansivu cab231ee3a Sandstorm/Snap migration: use the modern mongodb driver (OP_MSG) for FerretDB inserts
Text collections exported and 'inserted N/N' was logged, but every document actually
failed with 'Unsupported OP_QUERY command: update' — nothing reached FerretDB. Cause:
requireAny('mongodb') resolved the ANCIENT meteor-spk base driver (v2.x, at the deps
root) because the modern driver is not directly under programs/server/npm/node_modules
— Meteor nests it at .../meteor/npm-mongo/node_modules/mongodb (v6.16). The 2.x driver
speaks legacy OP_QUERY, which FerretDB rejects; the 6.x driver speaks OP_MSG (the same
driver the WeKan app uses against FerretDB). Add the npm-mongo path as the first
resolver anchor, and log the resolved driver version.

(Separately, GridFS attachment/avatar extraction still finds 0 files for this grain —
its attachments appear to be in Meteor-Files buckets (attachments.files/.chunks) rather
than the CollectionFS cfs_gridfs.* the importer currently handles; to be addressed once
the modern driver confirms text migration and the real attachment collection counts.)

Thanks to xet7.
2026-07-13 02:56:35 +03:00
Lauri Ojansivu d693ae8d7d Changelog: add individual commit links for the folded migration sub-fixes
Link the mongodb default-import, mongoexport --quiet removal, diagnostic/dashboard, and
createRequire commits inline within their parent migration bullets.

Thanks to xet7.
2026-07-13 02:44:17 +03:00
Lauri Ojansivu 5054dab8b6 Changelog: link the wiredTigerCacheSizeGB integer-value fix commit
Thanks to xet7.
2026-07-13 02:41:38 +03:00
Lauri Ojansivu 9c06bd5772 Changelog: update the migration EJSON bullet to the modern-bundle resolution fix
Thanks to xet7.
2026-07-13 02:41:01 +03:00
Lauri Ojansivu beefe441d7 Sandstorm/Snap migration: resolve bson/mongodb from the modern server bundle, not the old base
The EJSON diagnostic was conclusive: require('bson') returned an object with no EJSON,
mongodb.EJSON was undefined, and mongodb/lib/bson* were MODULE_NOT_FOUND. Cause: the
importer sits at the deps root next to the OLD meteor-spk 0.6.0 base node_modules
(bson 1.x with no EJSON at all, plus an ancient mongodb that has MongoClient but no
EJSON re-export), kept there only for the niscu->3.0 stage — so a bare require resolved
those adjacent copies. WeKan's current bson/mongodb (with EJSON) live under
programs/server/npm/node_modules. Anchor createRequire inside that modern bundle first
(falling back to the deps root), and load both mongodb and bson through it. This also
switches the importer to the modern mongodb driver — the same one the WeKan app uses
against FerretDB.

Thanks to xet7.
2026-07-13 02:36:09 +03:00
Lauri Ojansivu 0e0a8bbb33 Sandstorm/Snap migration: load mongodb/bson via createRequire; resolve EJSON robustly
The mongodb default import exposed MongoClient but NOT EJSON (mongodbPkg.EJSON was
undefined), so the previous 'take EJSON from mongodb' attempt still hit the FATAL
guard. Node 24's ESM default-interop for these CommonJS packages drops the
getter/re-export used for EJSON. Switch to createRequire (CJS require returns the real
module.exports with getters intact and honors NODE_PATH), and resolve EJSON by trying,
in order: mongodb.EJSON, mongodb/lib/bson.js, mongodb/lib/bson, bare bson's .EJSON,
and bare bson itself — falling back with a diagnostic list of what each attempt
returned so a remaining failure names the cause instead of just 'undefined'.

Thanks to xet7.
2026-07-13 02:20:23 +03:00
Lauri Ojansivu 5f40f612f5 Changelog: Sandstorm/Snap migration EJSON-from-mongodb-driver fix
Thanks to xet7.
2026-07-13 02:07:45 +03:00
Lauri Ojansivu b0703befd7 Sandstorm/Snap migration: get EJSON from the mongodb driver, not a bare bson import
With mongoexport connecting, every collection then failed with 'parse <coll>: Cannot
read properties of undefined (reading parse)' — EJSON was undefined. The importer runs
with NODE_PATH=programs/server/node_modules, but the EJSON-bearing bson (7.3.0) lives
under programs/server/npm/node_modules, so a bare 'import bson' did not resolve to it
and EJSON came out undefined. The mongodb driver (which resolves fine — MongoClient
works) bundles bson and re-exports EJSON from lib/bson.js, so take EJSON from the same
default import and drop the separate bson dependency. Add an upfront guard that fails
loudly if EJSON.parse is ever missing instead of spamming one error per collection.

Thanks to xet7.
2026-07-13 02:07:24 +03:00
Lauri Ojansivu 7f42db4670 Changelog: Sandstorm/Snap migration mongoexport IPv4 host fix + live dashboard
Thanks to xet7.
2026-07-13 01:49:45 +03:00
Lauri Ojansivu 6142396ae9 Sandstorm/Snap migration: connect mongoexport to 127.0.0.1 (IPv6 localhost broke it)
The real reason every mongoexport failed (revealed once --quiet was dropped):
'error connecting to db server: no reachable servers'. mongoexport is a Go tool
whose --host defaults to 'localhost', which resolves to ::1 (IPv6) first, but the
migration mongod listens only on --bind_ip 127.0.0.1 (IPv4) — so mongoexport could
never reach it, while the mongo shell (whose host defaults to 127.0.0.1) connected
fine and listed all 42 collections. Pass --host 127.0.0.1 explicitly.

Also fill the dashboard Activity panel from the first moment (mongoexport-ready line,
and one line per collection including empty ones) so progress is visible live instead
of the panel sitting on '(waiting…)' while only red connection errors accumulated.

Thanks to xet7.
2026-07-13 01:49:21 +03:00
Lauri Ojansivu 3076f2317e Sandstorm/Snap migration: drop mongoexport --quiet (it hid the error) + live activity log
The --version probe confirmed the bundled mongoexport runs fine (r3.2.22), yet every
per-collection export exited status=1 with empty stderr AND stdout. The empty stderr
was mongoexport's own --quiet flag suppressing its failure message. Drop --quiet so
the real reason (e.g. 'Failed: <reason>') prints to stderr; mongoexport's normal
progress lines also go to stderr, so stdout stays clean Extended JSON either way.

Also surface progress on the dashboard as the user asked: a rolling Activity log
(last ~15 lines: collections found, per-collection export/insert counts, GridFS file
extraction counts) rendered in a panel and mirrored to the grain log, so it is clear
what the migration is doing rather than only red errors appearing later.

Thanks to xet7.
2026-07-13 01:23:38 +03:00
Lauri Ojansivu 62df991532 Sandstorm/Snap migration: diagnose mongoexport failures + live progress dashboard
Every per-collection mongoexport failed with 'failed: undefined' because the error
only logged (r.stderr || r.error): an empty stderr with a non-zero/killed status
(e.g. a SIGSEGV, where spawnSync reports status=null, signal='SIGSEGV', stderr='')
printed as 'undefined', hiding the real cause. Log a full describe(r) instead
(status, signal, error code, stderr AND stdout snippets), and probe
'mongoexport --version' / '--help' once at startup so the next run shows whether the
bundled mongoexport binary itself is broken (dies on --version too → an ABI/bundling
problem) or only the export invocation is. The mongo shell on the same libs works
(listCollections succeeds), so this narrows it precisely.

Also make the progress dashboard obviously live: a CSS spinner while running (✅/❌
when done), a server 'updated' timestamp that changes on every 2s auto-refresh, and
an error counter — the previous page refreshed but showed no sign of activity.

Thanks to xet7.
2026-07-13 00:58:54 +03:00
Lauri Ojansivu 50abd8f95a Sandstorm/Snap migration: import mongodb as default (CommonJS) under Node 24 too
Same CommonJS/ESM interop issue as the bson import: with { EJSON } fixed, the
importer next threw 'Named export MongoClient not found. The requested module
mongodb is a CommonJS module'. The bundled mongodb driver is CommonJS under Node
24's ESM loader, so import the default and destructure MongoClient. These are the
only two third-party imports; the rest are node: builtins.

Thanks to xet7.
2026-07-13 00:33:32 +03:00
Lauri Ojansivu cafbb1761b Changelog: Sandstorm/Snap migration bson default-import fix for Node 24 ESM
Thanks to xet7.
2026-07-13 00:18:50 +03:00
Lauri Ojansivu a5bcb2e27c Sandstorm/Snap migration: import bson as default (CommonJS) under Node 24 ESM
With the WiredTiger cache fixed, mongod 3.0 now starts and the migration importer
runs, but it crashed immediately: 'import { EJSON } from "bson"' threw
"SyntaxError: Named export 'EJSON' not found. The requested module 'bson' is a
CommonJS module". bson (as bundled in WeKan's server node_modules) is CommonJS, so
Node 24's ESM loader exposes no named exports on it. Import the default and
destructure EJSON from it, as Node's own error message advises. Shared by the Snap
migration too (same Node 24).

Thanks to xet7.
2026-07-13 00:18:33 +03:00
Lauri Ojansivu 0804cd19e8 Sandstorm .spk: mongod 3.0 wiredTigerCacheSizeGB must be an integer (1, not 0.25)
mongod 3.0.7 parses --wiredTigerCacheSizeGB as an integer number of GB, so the
0.25 from the previous commit failed at startup with 'Error parsing option
wiredTigerCacheSizeGB as int: Bad digit "." while parsing 0.25' and the migration
still crash-looped. Use 1 (GB). It is a cache cap, not a preallocation, so a short
migration of a normal-sized grain never actually uses that much.

Thanks to xet7.
2026-07-12 23:57:43 +03:00
Lauri Ojansivu 3b109d14e8 Changelog: Sandstorm MongoDB 3 -> FerretDB migration fix (WiredTiger cache + source DB)
Thanks to xet7.
2026-07-12 23:39:09 +03:00
Lauri Ojansivu 3f5c70e643 Sandstorm .spk: fix MongoDB 3 -> FerretDB migration (WiredTiger cache=0G, wrong source DB)
Importing an existing WeKan grain crash-looped in the one-time MongoDB 3 -> FerretDB
migration: mongod 3.0 forked and its child aborted with exit code 14. Two bugs:

1. WiredTiger cache_size=0G. mongod 3.0 sizes the WiredTiger cache from detected
   RAM (RAM/2 - 1GB), but inside a Sandstorm grain sandbox RAM detection returns 0,
   so it computes cache_size=0G and WiredTiger refuses to open (minimum is 1MB),
   logging 'Value too small for key cache_size' and 'Fatal Assertion 28561' to
   /var/migration-mongod.log before aborting. Pass an explicit
   --wiredTigerCacheSizeGB 0.25 (256MB) to both mongod invocations (the niscu ->
   3.0 stage, which writes new WiredTiger data, and the 3.0 -> FerretDB stage) so
   the cache size never depends on RAM detection. The data itself is fine (turtle
   file: WiredTiger 2.5.3, i.e. written by mongod 3.0; the 'unclean shutdown'
   notice is harmless, WiredTiger recovers from the last checkpoint).

2. Wrong source database. Sandstorm WeKan grains store their data in the
   Meteor-default database 'meteor' (the niscu stage reads/writes 'meteor', and a
   real grain's WiredTiger catalog shows meteor.* collections), but the importer
   was told SRC_DB 'wekan', so even once mongod started it would have exported zero
   collections. Only the FerretDB target database is 'wekan'.

Thanks to xet7.
2026-07-12 23:38:52 +03:00
Lauri Ojansivu 455e498482 Changelog: Sandstorm open All Boards + grain URL sync fix
Thanks to xet7.
2026-07-12 23:12:45 +03:00
Lauri Ojansivu 3ab2b9dccb Sandstorm .spk: open All Boards (not sign-in) and keep the grain URL in sync
Two grain-navigation regressions vs the last working Sandstorm build (v6.15):

1. Opening a grain showed 'Must be logged in' instead of the All Boards page.
   On Sandstorm the platform authenticates the user asynchronously over DDP via
   connection.setUserId(), which (unlike a password login) does not set
   Meteor.loggingIn(), so Meteor.userId() is null for the first moments after the
   grain opens. useraccounts' ensureSignedIn route trigger and renderBoardList()
   both bounced that brief null window to the atSignIn route — a sign-in page that
   does not exist inside a grain. config/router.js now uses a Sandstorm-aware
   ensureSignedInUnlessSandstorm wrapper (a no-op on Sandstorm) and renderBoardList()
   no longer redirects on Sandstorm; the All Boards list renders and reactively
   fills in once the platform login lands.

2. The Sandstorm shell's outer grain URL did not update when switching boards. The
   shell rewrites /grain/<id><path> when the app posts a { setPath } message
   (sandstorm shell/imports/client/grain-client.js). The sync was a bare top-level
   Tracker.autorun that could run before flow-router-extra's reactive path tracking
   was initialised and then never re-run. Restore v6.15's event-driven
   FlowRouter.triggers.enter (fresh entering path, no dependency on init order) and
   additionally keep a watchPathChange() autorun wrapped in Meteor.startup as a
   backup. setTitle now also re-runs on route change.

Thanks to xet7.
2026-07-12 23:12:07 +03:00
Lauri Ojansivu d79f90fdfe Changelog: Sandstorm attachment/avatar download authorization via X-Sandstorm-User-Id
Thanks to xet7.
2026-07-12 22:55:11 +03:00
Lauri Ojansivu 1ca7bd3bb6 Sandstorm .spk: authorize attachment/avatar downloads via X-Sandstorm-User-Id
On Sandstorm the grain download route returned 403 for private boards, so
attachment thumbnails, minicard covers and the slideshow all showed broken
images even though the upload succeeded and the file was on disk. The download
handler (server/routes/universalFileServer.js) authorizes private-board files
via a Meteor login token (Authorization / X-Auth-Token / authToken query /
meteor_login_token cookie), but Sandstorm has none of these: authentication is
via connection.setUserId() and the sandstorm-http-bridge X-Sandstorm-* request
headers, so extractLoginToken() returned null and isAuthorizedForBoard() denied
every request. Sandstorm already gates grain access at the platform level, so any
request reaching WeKan is an authenticated grain user; trust it. Both
isAuthorizedForBoard() and isAuthorizedForAvatar() now short-circuit to allow
when Meteor.settings.public.sandstorm is set and the request carries the
bridge-injected X-Sandstorm-User-Id header. Gating on the setting means a spoofed
header cannot bypass auth on non-Sandstorm deployments.

Thanks to xet7.
2026-07-12 22:54:52 +03:00
Lauri Ojansivu 525cd07eee Changelog: add the Sandstorm DDP attachment-upload fix to Upcoming
Link the fix that switches attachment uploads to DDP transport on Sandstorm, since
the bridge strips Meteor-Files' custom x-* HTTP upload headers.

Thanks to xet7.
2026-07-12 22:29:06 +03:00
Lauri Ojansivu dc8ff6e6ca Sandstorm .spk: upload attachments over DDP (bridge strips Meteor-Files' HTTP headers)
Adding a file to a card in the grain failed with HTTP 400 "Can't continue upload,
session expired [408]" and the file silently disappeared. The Meteor-Files HTTP
upload protocol signals the first chunk with an x-start header and tracks the
session with x-mtok / x-chunkid / x-fileid / x-eof, but Sandstorm's request-header
whitelist (web-session.capnp) does not include those, so the sandstorm-http-bridge
strips them: the server never sees x-start, treats every request as a chunk
continuation, cannot find the per-fileId session and returns 408. Use
transport: 'ddp' on Sandstorm (detected via Meteor.settings.public.sandstorm) so
uploads go over DDP method calls instead of custom HTTP headers; HTTP transport is
kept everywhere else (it avoids the Safari DDP-reconnect stall).

Thanks to xet7.
2026-07-12 22:28:28 +03:00
Lauri Ojansivu c671a7fc8c Sandstorm .spk: temporarily enable Meteor-Files debug logging on Sandstorm
Attachment uploads in the grain fail with HTTP 400 "Can't continue upload, session
expired [408]": the upload start succeeds but the per-fileId session is gone by the
time a chunk arrives (both the in-memory _currentUploads entry and the
__pre_attachments pre-collection doc are missing), which points at the polling
observe (FerretDB has no oplog) firing a spurious removed event and aborting the
upload. The Attachments FilesCollection had debug: false, so nothing about the
upload path is logged. Enable Meteor-Files debug on Sandstorm only (gated on
Meteor.settings.public.sandstorm) so the grain debug log shows the start /
createStream / observer / continueUpload steps and pinpoints where the session is
lost. TEMPORARY: revert to debug: false once the upload is fixed.
2026-07-12 22:09:57 +03:00
Lauri Ojansivu d5092c9b2d Changelog: add the Sandstorm grain-URL sync fix to Upcoming
Link the fix that keeps the Sandstorm shell's grain URL in sync with the in-app
route via a reactive autorun.

Thanks to xet7.
2026-07-12 21:38:07 +03:00
Lauri Ojansivu 68e59ab66f Sandstorm .spk: keep the grain URL in sync with the in-app route
Navigating between boards worked but the Sandstorm shell's grain URL never updated
(it stayed on the grain root), unlike standalone WeKan. The path was synced via a
global FlowRouter.triggers.enter callback, which does not fire reliably on client
navigation in this flow-router-extra / Meteor 3 setup. Sync it from a reactive
Tracker.autorun on FlowRouter.watchPathChange() instead (the same mechanism the
setTitle sync already uses), so every route change posts setPath to the shell and
the grain URL becomes /grain/<id><path>.

Thanks to xet7.
2026-07-12 21:37:37 +03:00
Lauri Ojansivu 11f87c2115 Sandstorm .spk: temporary diagnostic to log the exact FerretDB-rejected query
Opening a board in the grain fails with "MongoServerError: unknown operator: userId"
(BadValue) - FerretDB rejecting a query MongoDB accepts - but the driver stack trace
has no WeKan call site, so the offending selector is unknown. This wraps the raw
mongodb Collection.find() to log the collection name and exact selector whenever a
cursor iteration throws, to pinpoint the query. TEMPORARY: to be removed once the
query is rewritten FerretDB-compatibly.

Thanks to xet7.
2026-07-12 19:57:16 +03:00
Lauri Ojansivu 21644652e2 Changelog: add the Sandstorm sign-in bounce fix to Upcoming
Link the fix that redirects from the sign-in page to the boards list once the
asynchronous Sandstorm auto-login sets Meteor.userId().

Thanks to xet7.
2026-07-12 18:47:30 +03:00
Lauri Ojansivu 6f3174b23d Sandstorm .spk: bounce from sign-in to the boards list once auto-login lands
The Sandstorm login was actually succeeding - Meteor.userId() gets set (confirmed:
Meteor.connection._userId held a valid id, Meteor.loggingIn() false) - but the grain
stayed on the sign-in page. WeKan's home route (renderBoardList) checks
Meteor.userId() once and, because the Sandstorm header login is asynchronous and
uses connection.setUserId() (bypassing accounts-base, so no Accounts.onLogin fires),
finds it still null on first render and redirects to 'atSignIn' - where the user is
stranded even after login completes moments later. Add a Sandstorm-only reactive
autorun that sends the user from 'atSignIn' back to 'home' as soon as
Meteor.userId() is set, so the grain lands on the All Boards page.

Thanks to xet7.
2026-07-12 18:47:01 +03:00
Lauri Ojansivu fb0c7f7f60 Changelog: add the ROOT_URL-per-request Sandstorm login/CORS fix to Upcoming
Link the fix that rewrites ROOT_URL to the grain's real URL so DDP, dynamic
imports and the Sandstorm auto-login stop failing cross-origin.

Thanks to xet7.
2026-07-12 18:15:37 +03:00
Lauri Ojansivu d5f707fd37 Sandstorm .spk: rewrite ROOT_URL per request to the grain URL (fixes login + CORS)
WeKan loaded but stayed on "Must be logged in", and the console showed
"Cross-Origin Request Blocked ... http://127.0.0.1:4000/__meteor__/dynamic-import/fetch".
The launcher sets a fixed ROOT_URL (http://127.0.0.1:4000, the internal bridge
target), but Sandstorm serves each grain at a per-session host (ui-<hash>.<host>)
via sandstorm-http-bridge, so the client sent its DDP connection and dynamic-import
fetches to 127.0.0.1:4000 - cross-origin and unreachable from the browser - and the
header-based login handshake (a DDP method call) never completed. Add a
WebApp.addRuntimeConfigHook that rewrites ROOT_URL to the grain's real base URL
(X-Sandstorm-Base-Path) per request, and re-asserts the SANDSTORM flag, so the
client talks to the same origin it loaded from. DDP, dynamic imports and the
Sandstorm auto-login now work.

Thanks to xet7.
2026-07-12 18:15:15 +03:00
Lauri Ojansivu be8976ed8c Changelog: add the SANDSTORM=1 auto-login fix to Upcoming
Link the fix that sets process.env.SANDSTORM=1 in the launcher so the
Sandstorm header-based auto-login runs and pages stop showing "Must be logged in".

Thanks to xet7.
2026-07-12 17:57:43 +03:00
Lauri Ojansivu b0712e6656 Sandstorm .spk: set SANDSTORM=1 so the header-based auto-login runs
WeKan loads in the grain but every page showed "Must be logged in". The
wekan-accounts-sandstorm client only starts the automatic X-Sandstorm-* header
login when __meteor_runtime_config__.SANDSTORM is set, and the package only sets
that when process.env.SANDSTORM is present - which nothing did (start.js set
MONGO_URL/ROOT_URL/PORT/WRITABLE_PATH but not SANDSTORM, and the pkgdef env didn't
either). The launcher now sets process.env.SANDSTORM = '1' before loading the WeKan
bundle, so the package enables the runtime flag and the client auto-logs-in the
Sandstorm user from the X-Sandstorm-* headers. (App code detects Sandstorm via a
separate Meteor.settings.public.sandstorm flag from the pkgdef METEOR_SETTINGS,
which already worked.)

Thanks to xet7.
2026-07-12 17:57:21 +03:00
Lauri Ojansivu ad46cb6102 Changelog: add the no-auto-board + global-role Sandstorm change to Upcoming
Link the change that stops auto-creating a board on a new grain and maps the
grain's Sandstorm permissions to the user's global WeKan role.

Thanks to xet7.
2026-07-12 17:40:33 +03:00
Lauri Ojansivu 8f11e8ac66 Sandstorm .spk: don't auto-create a board; map grain permissions to global role
WeKan on Sandstorm is multi-board now, so a new grain/user no longer gets a
hard-coded 'sandstorm'/libreboard board auto-created - the user creates their own
boards from the All Boards page. The Users.after.insert hook no longer inserts that
board + Default swimlane. updateUserPermissions previously added the user as a
member of that single board (which would now crash, since the board no longer
exists); it now maps the grain's Sandstorm permissions to the user's GLOBAL WeKan
role instead - 'configure' (grain owner) becomes a WeKan admin, everyone else is a
regular user who can create and manage their own boards. Dropped the now-unused
Boards/Swimlanes imports.

Thanks to xet7.
2026-07-12 17:40:09 +03:00
Lauri Ojansivu bb8233655c Changelog: add the "open on All Boards" Sandstorm change to Upcoming
Link the change that removes the hard-coded single-board redirect so the grain
opens on the All Boards page.

Thanks to xet7.
2026-07-12 17:37:36 +03:00
Lauri Ojansivu b5945cf596 Sandstorm .spk: open the grain on the All Boards page, not a hard-coded board
WeKan on Sandstorm originally opened a single hard-coded board
(/b/sandstorm/libreboard) and redirected "/" to it. It now supports many boards and
that libreboard is no longer the right destination, so redirecting to it is wrong.
Remove the WebApp.handlers.get("/") redirect entirely: "/" now falls through to
WeKan's normal serving, whose client "home" route (config/router.js) renders the
All Boards list - the right landing page for a multi-board grain. This also removes
the server-side redirect that browsers rejected as a Corrupted Content Error
(FlowRouter.path does not resolve on the server + Content-Length mismatch).

Thanks to xet7.
2026-07-12 17:36:16 +03:00
Lauri Ojansivu 6e60644bdb Changelog: add the "/" redirect (corrupted content) fix to Upcoming
Link the fix that builds the Sandstorm board redirect path directly and sends a
body with a matching Content-Length, so the grain's "/" stops failing with a
browser Corrupted Content Error.

Thanks to xet7.
2026-07-12 17:33:21 +03:00
Lauri Ojansivu ccdd1a0846 Sandstorm .spk: fix the "/" redirect (malformed Location + Content-Length mismatch)
The grain's "/" served a broken 301: Location was ".../:6080board" because
FlowRouter.path() does not resolve on the server in Meteor 3.x (it returned the
bare route name "board"), and the response advertised Content-Length: 90 while
sending an empty body, which the browser rejected as a "Corrupted Content Error"
(NS_ERROR_NET_CORRUPTED_CONTENT). Build the board path directly (/b/:id/:slug, the
'board' route) and send a real HTML body (meta-refresh + link) with a matching
Content-Length, so the redirect to the hard-coded Sandstorm board works. Together
with the Accept-Encoding strip (keeps Content-Length valid) and the modern bridge.

Thanks to xet7.
2026-07-12 17:32:54 +03:00
Lauri Ojansivu 04737bd76e Changelog: add the modern sandstorm-http-bridge fix to Upcoming
Link the fix that bundles a modern sandstorm-http-bridge (from the Sandstorm
install) so the grain stops serving Corrupted Content on WeKan's "/" redirect.

Thanks to xet7.
2026-07-12 04:28:04 +03:00
Lauri Ojansivu 7f0706e45f Sandstorm .spk: bundle a modern sandstorm-http-bridge to fix "Corrupted Content"
The grain boots, but the page failed with a browser "Corrupted Content Error"
(NS_ERROR_NET_CORRUPTED_CONTENT) on WeKan's "/" redirect (0 bytes, ~8.5s, then
failed). The meteor-spk 0.6.0 base bundles an ancient (~2016) sandstorm-http-bridge
that mangles responses - it always advertises Accept-Encoding: gzip to the app and
mishandles redirect/encoding. build-deps.sh now overwrites the bundled
/sandstorm-http-bridge with the modern one from a Sandstorm install
(/opt/sandstorm/latest/bin/sandstorm-http-bridge; override with SANDSTORM_HTTP_BRIDGE).
Sandstorm is amd64-only so one binary covers it. The sandstorm.yml workflow now
installs Sandstorm before assembling the deps so the bridge is available on the CI
runner. Complements the app-side Accept-Encoding strip.

Thanks to xet7.
2026-07-12 04:27:40 +03:00
Lauri Ojansivu ab8da931cf Changelog: add the Sandstorm Accept-Encoding (corrupted content) fix to Upcoming
Link the fix that strips Accept-Encoding in the Sandstorm grain so Meteor serves
uncompressed responses and the browser stops showing a Corrupted Content Error.

Thanks to xet7.
2026-07-12 03:56:02 +03:00
Lauri Ojansivu 013b6b5266 Sandstorm .spk: strip Accept-Encoding so the grain doesn't serve corrupted (gzip) content
The grain now boots, but the page failed to load with a browser "Corrupted Content
Error" (NS_ERROR_NET_CORRUPTED_CONTENT). sandstorm-http-bridge advertises
"Accept-Encoding: gzip" to the app regardless of what the browser actually sent, so
Meteor served gzip/brotli-encoded responses the browser could not decode. Strip
Accept-Encoding in a WebApp.rawHandlers middleware (which runs before Meteor's
static/boilerplate serving) so responses go out uncompressed; bandwidth is a
non-issue behind the local bridge.

Thanks to xet7.
2026-07-12 03:55:37 +03:00
Lauri Ojansivu 0115622a9a Changelog: add the FerretDB boolean-index-option fix to Upcoming
Link the fix that makes the services.sandstorm.id unique index use boolean
options so FerretDB accepts it and the Sandstorm grain boots past index creation.

Thanks to xet7.
2026-07-12 03:39:35 +03:00
Lauri Ojansivu 975316f5cd Sandstorm .spk: use boolean index options so FerretDB accepts the users index
wekan-accounts-sandstorm created the unique index on services.sandstorm.id with
{unique: 1, sparse: 1}. Real MongoDB accepts the truthy 1, but FerretDB (used by
the Sandstorm .spk) is strict and rejects it with "The field 'unique' has value
unique: 1, which is not convertible to bool", crashing the grain at boot during
index creation. Use real booleans (unique: true, sparse: true).

Thanks to xet7.
2026-07-12 03:39:17 +03:00
Lauri Ojansivu 54aad554aa Changelog: add the sandstorm.js stale-globals boot fix to Upcoming
Link the fix that imports the Users/Boards/Swimlanes/Activities collections and
drops the removed-HTTP-package monkey patch, so the Sandstorm grain boots past
the capnp guard.

Thanks to xet7.
2026-07-12 03:27:25 +03:00
Lauri Ojansivu 60e40199c9 Sandstorm .spk: fix server-boot crashes from stale globals (Users, HTTP) in sandstorm.js
Once the capnp load was made non-fatal, the grain reached the rest of sandstorm.js
and hit two latent Meteor-2.x-isms the Meteor 3.x migration missed (this file only
runs on Sandstorm, so it was not exercised): (1) it referenced the Users, Boards,
Swimlanes and Activities collections as implicit globals, but those are now ES
module default exports, so `Users.after.insert` threw "Users is not defined" at
boot; and (2) it monkey-patched `HTTP.methods` from the meteor/http package, which
was removed in the Meteor 3.x migration, so `HTTP` was undefined. Import the
collections (and Accounts) explicitly, and remove the obsolete HTTP.methods patch
(WeKan's REST API no longer uses it - it uses WebApp/JsonRoutes with header auth).

Thanks to xet7.
2026-07-12 03:27:02 +03:00
Lauri Ojansivu ff3f35ac43 Changelog: add the split-snap-build (native amd64/arm64 + non-blocking Launchpad) to Upcoming
Link the release-workflow change that builds amd64/arm64 natively on GitHub and
moves the exotic arches to a non-blocking per-arch Launchpad matrix, so the
release no longer hangs hours on riscv64.

Thanks to xet7.
2026-07-12 03:21:30 +03:00
Lauri Ojansivu 8549a62c85 Snap release: build amd64+arm64 natively on GitHub, exotic arches non-blocking on Launchpad
The single snap job ran `snapcraft remote-build` for all 5 platforms on Launchpad
and blocked until the slowest resolved, so the release hung ~3.5h on riscv64's
Launchpad queue even though amd64+arm64 finished in minutes. Split it in two:
snap-native builds amd64 (ubuntu-24.04) and arm64 (ubuntu-24.04-arm) NATIVELY on
GitHub runners via snapcore/action-build; snap-launchpad builds s390x/ppc64el/
riscv64 on Launchpad in a NON-BLOCKING (continue-on-error), per-arch matrix
(remote-build --build-for <arch>) so a slow or failed exotic arch never delays the
release or the other arches. Each arch publishes to the Snap Store
(candidate,beta,edge) and attaches to the GitHub Release the moment it finishes.
All 5 arches still ship.

Thanks to xet7.
2026-07-12 03:21:03 +03:00
Lauri Ojansivu 8b9202d677 Changelog: add the Sandstorm capnp grain-boot fix to Upcoming
Link the fix that stops capnp.node's Node 24 ABI mismatch from crash-looping
the Sandstorm grain; the grain now boots and core WeKan works via the
sandstorm-http-bridge headers.

Thanks to xet7.
2026-07-12 03:08:53 +03:00
Lauri Ojansivu f4f22bbe24 Sandstorm .spk: don't crash the grain when capnp.node can't load on Node 24
WeKan on Sandstorm bundles Node 24, but capnp.node (node-capnp) is built for an
older Node ABI (NODE_MODULE_VERSION 83 = Node 14), so `Npm.require('capnp')` in
sandstorm.js failed with ERR_DLOPEN_FAILED and crash-looped the whole grain on
boot. Load Cap'n Proto lazily in a try/catch and degrade gracefully: the grain
boots and core WeKan works, because login and user identity come from the
sandstorm-http-bridge X-Sandstorm-* HTTP headers (wekan-accounts-sandstorm) and
need no Cap'n Proto. Only the two capnp-only features are skipped when the addon
cannot load - the Powerbox identity-claim method and the Sandstorm activity
notifications - and they log a clear warning. These can be restored by rebuilding
node-capnp for Node 24, or reimplemented over the bridge's HTTP/JSON API (see the
Sandstorm CHANGELOG: use Cap'n Proto APIs without Cap'n Proto).

Thanks to xet7.
2026-07-12 03:08:23 +03:00
Lauri Ojansivu 32b561cfbf Changelog: add the FerretDB state-dir Sandstorm fix to Upcoming
Link the fix that points FerretDB's --state-dir to writable /var so the
Sandstorm grain starts instead of crash-looping on a read-only /state.json.

Thanks to xet7.
2026-07-12 02:25:07 +03:00
Lauri Ojansivu 1c28b40fd4 Sandstorm .spk: point FerretDB state dir to writable /var so the grain starts
FerretDB persists a state.json (version/UUID) via its state provider even
when telemetry is disabled, and its --state-dir defaults to "." — which in a
Sandstorm grain is "/", read-only. So FerretDB failed with "Failed to create
state provider: failed to persist state: open /state.json: read-only file
system", exited (code 1), and the grain crash-looped. sandstorm-src/start.js
now creates /var/ferretdb and passes --state-dir=/var/ferretdb (plus the
FERRETDB_STATE_DIR env) in startFerret(), covering both the migration and the
steady-state FerretDB launches.

Thanks to xet7.
2026-07-12 02:24:27 +03:00
Lauri Ojansivu 7f5cc03ea9 Changelog: add the Sandstorm .spk and Meteor unit tests fixes to Upcoming
List the glibc-loader grain crash-loop fix, the Sandstorm build-workflow
userns/ref fix, and the Meteor unit tests __dirname server-boot fix in the
Upcoming release section, each linking to its commit.

Thanks to xet7.
2026-07-12 01:58:12 +03:00
Lauri Ojansivu 60116bc72f Meteor unit tests: fix server-boot crash from __dirname in an ESM test file
server/lib/tests/dependencies.openapi.tests.js is an ES module (top-level
import) that referenced the bare __dirname global. Under Node 24 / Meteor 3.5
the compiler injects "const __dirname = fileURLToPath(import.meta.url)" for
ESM files that use __dirname, which collides with the __dirname the CommonJS
module wrapper already provides, so the whole server bundle failed to boot
with "Identifier '__dirname' has already been declared" and the "Meteor unit
tests" CI job died before any test ran. Drop the __dirname seed
(process.env.PWD already reaches the repo root under `meteor test`, and the
suite skips gracefully otherwise).

Thanks to xet7.
2026-07-12 01:57:23 +03:00
Lauri Ojansivu 66d8706c4d Sandstorm build workflow: enable unprivileged user namespaces and build the dispatched branch
Ubuntu 24.04 defaults kernel.apparmor_restrict_unprivileged_userns=1, which
blocks the unprivileged user namespaces the Sandstorm install and the spk
supervisor rely on, so sandstorm.yml now relaxes it on the runner. Also added
a "ref" workflow_dispatch input and check out that ref instead of a hardcoded
main, so a fix branch can be built and tested before it is merged to main.

Thanks to xet7.
2026-07-12 01:57:23 +03:00
Lauri Ojansivu 143607ef22 Sandstorm .spk: bundle the matching glibc dynamic loader so grains start
The .spk bundled the host's new glibc libc.so.6 (Ubuntu 24.04, glibc 2.39)
but kept the old glibc 2.31 ld-linux from the meteor-spk 0.6.0 base, so node
failed at startup with "libc.so.6: undefined symbol: _dl_audit_symbind_alt,
version GLIBC_PRIVATE" (HTTP-BRIDGE exit 127) and the grain crash-looped.
sandstorm-src/build-deps.sh now also copies the host's ld-linux-x86-64.so.2
into the deps so the loader and libc are the same glibc, and adds a [verify]
gate that fails the build if the bundled libc and loader glibc versions
differ or the bundled node cannot run under them - turning a silent grain
crash-loop into a loud build failure.

Thanks to xet7.
2026-07-12 01:57:23 +03:00
Lauri Ojansivu 0f52b6a787 Merge pull request #6447 from wekan/dependabot/npm_and_yarn/mongodb-7.5.0
Bump mongodb from 7.3.0 to 7.5.0
2026-07-12 00:23:37 +03:00
Lauri Ojansivu 87f4536e9d Bump @aws-sdk/client-s3 to ^3.1085.0 to match @aws-sdk/lib-storage 3.1085.0
Dependabot #6451 bumped lib-storage to ~3.1085.0, whose peer requires
client-s3 ^3.1085.0, but client-s3 was left at ^3.1071.0 — breaking
meteor npm install / npm ci with an ERESOLVE peer conflict.
2026-07-12 00:21:55 +03:00
Lauri Ojansivu cdde52392b sandstorm: trim .spk toward Cloudflare's 100 MB upload limit
- Drop the ~300 MB of modern MongoDB Database Tools (wekan/mongo-tools) from the
  Sandstorm build: they are unused there (Sandstorm backs up/restores grains
  itself; the MongoDB 3 -> FerretDB migration uses the legacy migratemongo CLIs +
  the .mjs importer). They stay in the .zip bundle / Docker / Snap, which use them.
- Set PUPPETEER_SKIP_DOWNLOAD=1 for the Meteor build (puppeteer is a test-only
  devDependency; its ~150 MB Chromium must never end up in the .spk).
- Pack step prints the .spk size and warns when it exceeds 100 MB.
2026-07-12 00:02:07 +03:00
dependabot[bot] 62f93fa46c Bump mongodb from 7.3.0 to 7.5.0
Bumps [mongodb](https://github.com/mongodb/node-mongodb-native) from 7.3.0 to 7.5.0.
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md)
- [Commits](https://github.com/mongodb/node-mongodb-native/compare/v7.3.0...v7.5.0)

---
updated-dependencies:
- dependency-name: mongodb
  dependency-version: 7.5.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-07-11 20:47:29 +00:00
Lauri Ojansivu 5b3a3fb744 Merge pull request #6451 from wekan/dependabot/npm_and_yarn/aws-sdk/lib-storage-3.1085.0
Bump @aws-sdk/lib-storage from 3.1073.0 to 3.1085.0
2026-07-11 23:39:47 +03:00
Lauri Ojansivu 349f4aa046 Merge pull request #6452 from wekan/dependabot/npm_and_yarn/i18next-26.3.6
Bump i18next from 26.3.4 to 26.3.6
2026-07-11 23:39:10 +03:00
Lauri Ojansivu ae1f37658c Merge pull request #6449 from wekan/dependabot/npm_and_yarn/puppeteer-25.3.0
Bump puppeteer from 25.1.0 to 25.3.0
2026-07-11 23:38:24 +03:00
Lauri Ojansivu df94214798 Merge pull request #6448 from wekan/dependabot/npm_and_yarn/tests/playwright/mongodb-7.5.0
Bump mongodb from 7.4.0 to 7.5.0 in /tests/playwright
2026-07-11 23:37:56 +03:00
Lauri Ojansivu 6c22e43be8 Merge pull request #6450 from wekan/dependabot/npm_and_yarn/typescript-eslint/eslint-plugin-8.63.0
Bump @typescript-eslint/eslint-plugin from 8.61.1 to 8.63.0
2026-07-11 23:37:29 +03:00
dependabot[bot] 5e5baf5ed7 Bump i18next from 26.3.4 to 26.3.6
---
updated-dependencies:
- dependency-name: i18next
  dependency-version: 26.3.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-07-11 20:34:11 +00:00
dependabot[bot] 713c13831b Bump @aws-sdk/lib-storage from 3.1073.0 to 3.1085.0
Bumps [@aws-sdk/lib-storage](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/lib/lib-storage) from 3.1073.0 to 3.1085.0.
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/lib/lib-storage/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.1085.0/lib/lib-storage)

---
updated-dependencies:
- dependency-name: "@aws-sdk/lib-storage"
  dependency-version: 3.1085.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-07-11 20:33:55 +00:00
dependabot[bot] e400ecf548 Bump @typescript-eslint/eslint-plugin from 8.61.1 to 8.63.0
Bumps [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) from 8.61.1 to 8.63.0.
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.63.0/packages/eslint-plugin)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-version: 8.63.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-07-11 20:33:27 +00:00
dependabot[bot] e9db3a8c2f Bump puppeteer from 25.1.0 to 25.3.0
Bumps [puppeteer](https://github.com/puppeteer/puppeteer) from 25.1.0 to 25.3.0.
- [Release notes](https://github.com/puppeteer/puppeteer/releases)
- [Changelog](https://github.com/puppeteer/puppeteer/blob/main/CHANGELOG.md)
- [Commits](https://github.com/puppeteer/puppeteer/compare/puppeteer-v25.1.0...puppeteer-v25.3.0)

---
updated-dependencies:
- dependency-name: puppeteer
  dependency-version: 25.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-07-11 20:32:58 +00:00
dependabot[bot] 260a2afacc Bump mongodb from 7.4.0 to 7.5.0 in /tests/playwright
Bumps [mongodb](https://github.com/mongodb/node-mongodb-native) from 7.4.0 to 7.5.0.
- [Release notes](https://github.com/mongodb/node-mongodb-native/releases)
- [Changelog](https://github.com/mongodb/node-mongodb-native/blob/main/HISTORY.md)
- [Commits](https://github.com/mongodb/node-mongodb-native/compare/v7.4.0...v7.5.0)

---
updated-dependencies:
- dependency-name: mongodb
  dependency-version: 7.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-07-11 20:32:45 +00:00
Lauri Ojansivu a8cf44cfaa sandstorm.yml: write signing keyring to ~/.sandstorm-keyring (path meteor-spk reads)
meteor-spk pack crashed with 'open(/home/runner/.sandstorm-keyring): No such file
or directory' because the keyring restore step wrote the decoded SANDSTORM_KEYRING
secret to ~/.sandstorm/sandstorm-keyring, but spk reads the app private key from
~/.sandstorm-keyring (a file directly in $HOME). Write it to the correct path, and
fail early with an actionable message when the secret is missing (the .spk cannot
be signed without it) instead of the cryptic later crash.
2026-07-11 23:12:37 +03:00
Lauri Ojansivu d53e7cafbb sandstorm build-deps.sh: fix 'not writing through dangling symlink' at step 3/7
The meteor-spk 0.6.0 base ships some runtime libs in meteor-spk.deps/lib as
DANGLING symlinks (e.g. libstdc++.so.6 -> a lib that no longer exists). When step
[3/7] refreshed them with the host's newer libs, 'cp -fL' refused with 'not writing
through dangling symlink' and failed the Sandstorm build. Add --remove-destination
so cp deletes the existing destination (dangling symlink included) before copying
the host's real library. Verified: plain 'cp -fL' reproduces the error; with
--remove-destination it succeeds and writes a real file.
2026-07-11 22:59:28 +03:00
github-actions[bot] f278d9ae68 Bump versions for v9.87 2026-07-11 19:44:03 +00:00
Lauri Ojansivu a700152e58 Updated ChangeLog. 2026-07-11 22:42:47 +03:00
Lauri Ojansivu b5f9097681 Updated translations. 2026-07-11 22:42:29 +03:00
Lauri Ojansivu b227a93193 Fix #6446: let board members (not only admins) move cards between swimlanes
In the swimlanes view, boardBody.js disabled the .js-swimlanes sortable — which
also carries moving a card from one swimlane to another — with !isBoardAdmin(),
though its own comment said it should be disabled only for non-members. So a normal
board member could move a card within a swimlane but not between swimlanes (and
could not reorder swimlanes). Gate it on !Utils.canModifyCard() instead (the client
write-access predicate: board member, not comment-only/worker/read-only), matching
the server's allowIsBoardMemberWithWriteAccess.
2026-07-11 22:38:18 +03:00
Lauri Ojansivu 52c62021a9 Updated translations 2026-07-11 22:10:54 +03:00
Lauri Ojansivu 692a258758 Updated ChangeLog. 2026-07-11 22:08:40 +03:00
Lauri Ojansivu 8847798f3c Release: update official + unofficial Node.js download URL paths on wekan.fi install page
The install page (../w/wekan.fi/install/index.html) links to Node.js downloads for
each snap/bundle arch: the OFFICIAL nodejs.org build (amd64/arm64/s390x/ppc64le)
and the UNOFFICIAL unofficial-builds.nodejs.org build (riscv64, which nodejs.org
has no binary for). release-website.sh only updated the displayed Node.js version
number, and version.sh's local website block did not touch Node.js at all, so those
download URLs went stale (404) after a Node.js bump.

Both now rewrite the version in the nodejs.org/dist/vX.Y.Z and
unofficial-builds.nodejs.org/download/release/vX.Y.Z paths and the
node-vX.Y.Z-linux-<arch> filename to the current Dockerfile NODE_VERSION.
2026-07-11 22:08:40 +03:00
github-actions[bot] 087d9fd0d8 Bump versions for v9.86 2026-07-11 17:54:20 +00:00
Lauri Ojansivu da55f1c413 Updated ChangeLog. 2026-07-11 20:53:16 +03:00
Lauri Ojansivu 28b4c6687c gitignore: also ignore locally-cloned wekan/mongo-tools and wekan/mongosh
FerretDB/ and sandstorm/ were already ignored; add /mongo-tools/ and /mongosh/ so
that temporarily cloning those wekan repos under this repo for editing never risks
committing them (they are separate git repos).
2026-07-11 20:23:17 +03:00
Lauri Ojansivu 10db1c3e76 Snap: automated release publishes to candidate + beta + edge (core24), not stable
core24 allows the candidate channel (core26 does not), so the automated
release-all.yml snap job publishes to candidate + beta + edge. The stable channel
is not published by the workflow — it is done manually later once proven. Updated
the workflow, snapcraft.yaml header, CHANGELOG and CPU-platforms.md.
2026-07-11 20:18:19 +03:00
Lauri Ojansivu 1a376b5dde Snap: automated release publishes to edge + beta (stable is manual, core24)
The default snapcraft.yaml is base: core24 (grade: stable) so it CAN be published
to the Snap stable channel, but that is done manually once it is proven stable
enough (core26 cannot go to stable). Revert the automated release-all.yml snap job
to publish to edge + beta channels (was candidate + edge). Update the workflow
header, snapcraft.yaml header, CHANGELOG and CPU-platforms.md to match.
2026-07-11 20:15:57 +03:00
Lauri Ojansivu e20dd132c1 Bundle-centric snap; self-contained bundle launchers restart-loop FerretDB + WeKan
Bundle launchers (releases/ferretdb/start-wekan.sh/.bat): run the bundle's own
per-platform binaries — FerretDB (./ferretdb[.exe]) in the background and WeKan
(./main.js on the bundled ./node[.exe]) in the foreground — inside a restart loop,
so if WeKan exits the whole stack restarts. Ctrl-C / closing the window stops both.

Snap wekan part: the wekan-<arch>.zip bundle is now the single source of every
binary. Handle all snap arches (amd64, arm64, s390x, ppc64el->ppc64le, riscv64);
use the bundle's OWN arch-correct Node.js (fixes riscv64, which nodejs.org has no
build for) instead of re-downloading from nodejs.org; move the bundle's per-arch
MongoDB Database Tools into $SNAP/bin; keep the bundle's ferretdb. Drop the
separate mongotools part (the tools already ship in the bundle), so nothing is
downloaded twice.
2026-07-11 20:13:00 +03:00
Lauri Ojansivu 64da38b412 Embed MongoDB Database Tools (wekan/mongo-tools) in all WeKan builds
Previously the per-arch MongoDB Database Tools were only in the Snap and the
Windows bundle. Now every build embeds them from the wekan/mongo-tools fork's
newest release (per-arch <tool>-<arch>):

- Linux .zip bundles (amd64/arm64/s390x/ppc64le/riscv64) download their arch's 8
  tools; the win64 and macOS jobs drop the inherited Linux tools and add their own
  (win64 .exe, mac-arm64). The Docker image inherits them from the Linux bundle.
- Sandstorm build-deps.sh adds the amd64 tools (separate from the legacy MongoDB
  3.2 migratemongo CLIs used for the one-time migration).

All from wekan/mongo-tools, none from mongodb.com.
2026-07-11 20:02:57 +03:00
Lauri Ojansivu 2a6bdadc15 Drop mongosh, use bundled Node.js + mongodb driver; FerretDB/mongo-tools per-arch; snap FerretDB-only arches
Databases / MongoDB clients:
- Remove the mongosh binary everywhere (snap + bundles). All scripted DB access
  (readiness ping, replica-set initiate/status, v8.43 schema migration) now runs
  through the new snap-src/bin/db-eval (bundled Node.js 24 + the mongodb driver).
  Ports wekan-control, mongodb-control, migration-control, start-wekan.sh/.bat and
  migrate-schema-v843.js -> .mjs off mongosh. The legacy MongoDB 3.2 mongo shell
  (migratemongo, amd64) stays for migration-time reads only.
- MongoDB Database Tools now come from the wekan/mongo-tools fork (pure Go, every
  arch) instead of mongodb.com, in snapcraft and the Windows bundle. version.sh /
  test-download-urls.sh no longer probe mongodb.com for mongosh/tools. The MongoDB 7
  server (mongod) is still fetched from MongoDB (amd64/arm64 only).
- FerretDB v1 downloaded per-arch (ferretdb-<arch>) from wekan/FerretDB, no
  ferretdb.zip: release-all.yml bundle jobs, docker-compose.yml, sandstorm build.

Snap:
- Default snapcraft.yaml is now the core24 grade:stable build (core26 variant kept
  as snapcraft-core26.yaml); release publishes to candidate + edge.
- Add s390x, ppc64el, riscv64 platforms as FerretDB-only (mongod not built there);
  new installs default to FerretDB v1 (snap/hooks/install already guards existing
  MongoDB data), DDP_TRANSPORT=sockjs. Fix Caddy ppc64el->ppc64le mapping.

Docs: add docs/Platforms/FOSS/Snap/CPU-platforms.md; update CHANGELOG and the
Sandstorm migration doc.
2026-07-11 15:37:56 +03:00
Lauri Ojansivu 7598859a47 Updated ChangeLog. 2026-07-11 13:20:39 +03:00
Lauri Ojansivu 4a94793f68 At default docker-compose.yml, changed DDP_TRANSPORT from uws to sockjs, because uws does not work at s390x.
Thanks to xet7 !
2026-07-11 13:20:39 +03:00
github-actions[bot] d4b19389eb Bump versions for v9.85 2026-07-11 09:05:59 +00:00
Lauri Ojansivu b24bf69d6c Updated ChangeLog. 2026-07-11 11:56:16 +03:00
Lauri Ojansivu 5cc9b1dcbb Docker: add "Build from source & start" menu action; remove obsolete compose version: attribute
Add a "Build from source & start (up -d --build)" action to the Docker
menus in rebuild-wekan.sh and rebuild-wekan.bat. It builds the wekan-app
image from the local Dockerfile, tags it as the image the chosen compose
file references (ghcr.io/wekan/wekan:latest), and starts that freshly
built container instead of a possibly-stale prebuilt image pulled from
the registry - useful when a source change (e.g. the FerretDB
Version-page detection) is not in the pulled image yet.

Remove the obsolete top-level "version:" attribute from all docker
compose files, which Docker Compose v2 warns about and ignores:
docker-compose.yml, docker-compose-ferretdb-v2-postgresql.yml,
docker-compose-multitenancy.yml, .devcontainer/docker-compose.yml, and
docs/Databases/ToroDB-PostgreSQL/docker-compose.yml.

Thanks to xet7 !
2026-07-11 11:52:03 +03:00
Lauri Ojansivu 4dbf99010c Docker: make FerretDB v1 + SQLite the default docker-compose.yml
Rename docker-compose-ferretdb-v1-sqlite.yml -> docker-compose.yml (the
new default) and the old MongoDB docker-compose.yml ->
docker-compose-mongodb-v7.yml, so "docker compose up -d" uses the light,
self-contained FerretDB v1 + embedded SQLite from
https://github.com/wekan/FerretDB by default.

Update rebuild-wekan.sh and rebuild-wekan.bat Docker menus to list
FerretDB v1 SQLite first (default) and point at the new filenames.
Update the compose files' own header comments (self-identification and
cross-references), note the new default at the top of docker-compose.yml,
and update the Docker docs (main Docker.md gets a compose-file/database
map; FerretDB2-PostgreSQL.md points at the v2 postgresql compose file).

Thanks to xet7 !
2026-07-11 11:35:47 +03:00
Lauri Ojansivu 544e1b14b4 rebuild-wekan.sh/.bat: Dev server also frees rspack :8080 on restart; add "Kill all dev servers"
The Dev server options killed only the app port, but "meteor run" also
starts an rspack dev server on 8080 that can outlive the meteor parent.
A leftover one made restarting a dev server crash with
"Error: listen EADDRINUSE ... :8080". The kill now frees both the app
port and the rspack port 8080 (Meteor.devServerPort || 8080), matching
the rspack watcher by its devServerPort env.

Port detection now checks the listening socket directly (ss/lsof with a
bash /dev/tcp fallback that needs no external tools; netstat on .bat)
instead of an HTTP probe, so it also catches a server that is still
building and not yet serving. Fixes a hang where lsof did reverse-DNS
without -nP.

Add a new "Dev server -> Kill all dev servers" menu option that frees
every dev/test port the scripts use at once: dev app 3000 + Mongo 3001,
Mocha test server 3100 + Mongo 3101, Sandstorm standalone dev 4000 +
Mongo 4001, and rspack 8080. It kills meteor, the rspack watcher and
Meteor's bundled --replSet meteor Mongos, never a production/system
Mongo. Both scripts escalate to SIGKILL if a port does not free up.

Update CHANGELOG and Build-from-source.md docs.

Thanks to xet7 !
2026-07-11 11:30:25 +03:00
Lauri Ojansivu 5ef2adf6fb rebuild-wekan.sh/.bat: Dev server options kill existing Meteor on the port; docs for new menu
Every "Dev server" menu option now stops any Meteor dev server already
listening on its port before starting a fresh one, so re-running a dev
option no longer fails because the port is taken. .sh adds a reusable
kill_meteor_on_port helper called by all six dev options; .bat funnels
them through :runlog, which calls a new :kill_meteor_on_port (netstat +
taskkill). Both wait for the port to free up and escalate to SIGKILL.

Also update the build-from-source docs (README.md, Build-from-source.md,
Build-and-Create-Pull-Request.md, Emoji.md, and the two Sandstorm
developer docs) to the new two-level menu (Setup -> Install dependencies,
Setup -> Build WeKan, Dev server -> localhost:3000), fix a stale
dev-server port (localhost:4000 -> 3000), and fix the README anchor link
to the renamed heading. Add a CHANGELOG entry.

Thanks to xet7 !
2026-07-11 11:11:22 +03:00
Lauri Ojansivu ccc03913fc i18n(fi): translate Sandstorm 'grain' as 'jyva' (jyvassa/jyvan)
Use the Finnish term jyva for Sandstorm grain in the sandstorm-migration
strings: Sandstorm-jyvassa, jyvan hakemistoihin, kayttavat jyvassa, jyvan
levytilan.
2026-07-11 10:47:13 +03:00
Lauri Ojansivu af62ebd97a i18n: Finnish translations for the Sandstorm migration admin panel strings
Translate the 12 sandstorm-migration-* strings in fi.i18n.json, matching the
existing WeKan Finnish terminology (siirto, Liitetiedostot, Profiilikuvat,
tiedostojärjestelmä, Poista, Tallennustila). The proper noun Sandstorm and the
literal paths/DB names are kept as-is.
2026-07-11 10:43:54 +03:00
Lauri Ojansivu f25c6553bd Updated translations 2026-07-11 10:40:13 +03:00
Lauri Ojansivu c72ae4cf05 i18n: don't translate the project name 'Sandstorm' (hardcode it)
Remove the en.i18n.json key sandstorm-migration whose value was the bare
proper noun 'Sandstorm' (the https://sandstorm.org project name), and hardcode
'Sandstorm' in the Admin Panel / Attachments tab label and panel title instead.
The other sandstorm-migration-* keys are real translatable strings and stay.
2026-07-11 10:35:01 +03:00
Lauri Ojansivu 43dcf56a3b rebuild-wekan.sh/.bat: group menu into category submenus + two-stage Docker menu
Replace the long flat menu with a short top-level menu (Setup / Dev server /
Tests / Docker / Tools / Quit); each opens a small submenu with 0) Back, so
only a few items show at once and labels are shorter (category gives context).
Docker becomes a two-stage submenu: pick backend, then Start (up -d) / Follow
logs (logs -f) / Stop (down) -- removing 12 near-identical flat entries.

All action handlers are unchanged; only the front-end dispatch is regrouped:
.sh keeps every case handler and reaches them via a choose() 'short|full' map
(dispatch wrapped in 'for _once in 1'); .bat routes category submenus to the
existing :labels. Verified: .sh bash -n clean + all 23 menu labels map to a
handler; .bat has no orphan gotos.
2026-07-11 07:31:23 +03:00
Lauri Ojansivu 1778929869 rebuild-wekan.sh/.bat: add Follow logs / Stop docker menu options per compose file
Expands the docker-compose menu so each backend (MongoDB docker-compose.yml,
FerretDB v1 SQLite, FerretDB v2 PostgreSQL, MongoDB Multitenancy) has three
grouped entries -- Start (up -d), Follow logs (logs -f) and Stop (down) --
instead of just Start. The .sh uses a generalized wekan_docker helper that
auto-detects 'docker compose' vs legacy 'docker-compose'.
2026-07-11 07:04:14 +03:00
Lauri Ojansivu d50277721c rebuild-wekan.sh/.bat: add menu options to start WeKan Docker per compose file
New menu entries run 'docker compose -f <file> up -d' for each backend:
MongoDB (docker-compose.yml), FerretDB v1 SQLite, FerretDB v2 PostgreSQL,
and MongoDB Multitenancy. Each prints follow-logs + stop commands. The .sh
auto-detects 'docker compose' vs legacy 'docker-compose'.
2026-07-11 06:57:48 +03:00
Lauri Ojansivu f1749b2af7 docker-compose ferretdb v1-sqlite: drop leftover MONGODB_LOG_* debug env
The MONGODB_LOG_PATH/TOPOLOGY/SERVER_SELECTION/CONNECTION=debug vars were
temporary mongodb-driver diagnostics that got committed by accident; they
flood wekan-app logs with topology JSON. Remove them from the example compose.
2026-07-11 06:49:16 +03:00
Lauri Ojansivu d0d98bcadc FerretDB: --log-level=error to silence connection WARN spam; remove dead MongoDB-driver subsystem
Driver debug logs showed a 2nd, TLS-enabled Mongo monitor connection
retrying every ~0.5s against the plaintext FerretDB port; FerretDB logged
each rejection at WARN. Harmless (WeKan uses the real plaintext connection)
but noisy. Start FerretDB with --log-level=error everywhere it is launched
(Docker entrypoint, snap ferretdb-control, release start-wekan.sh, the
v1-sqlite compose example).

Also remove the dead, unused MongoDB Driver System (server/mongodb-driver-startup.js
and models/lib/{meteorMongoIntegration,mongodbConnectionManager,mongodbDriverManager}.js)
- an abandoned MongoDB 3.0-8.0 auto-detect/driver-select experiment whose
driver packages were never installed. WeKan uses the mongodb-7 driver via Meteor.

gitignore the local FerretDB/ reference clone.
2026-07-11 06:28:30 +03:00
Lauri Ojansivu 743a47c462 snap: install Caddy from GitHub release binary, not Cloudsmith apt repo
The caddy part fetched Caddy from the Cloudsmith apt repo
(curl dl.cloudsmith.io | gpg --dearmor), which fails on Launchpad remote
builders (restricted network via a fetch proxy): gpg got no key
('no valid OpenPGP data found') and override-build failed with code 2 on
both arches. Download the official prebuilt vanilla Caddy static binary from
GitHub releases instead (per-arch, latest stable + pinned fallback). WeKan
uses only built-in Caddy directives, so no apt repo, gpg, or xcaddy needed.
Applied to both snapcraft.yaml and snapcraft-core24.yaml.
2026-07-11 05:56:25 +03:00
Lauri Ojansivu cfa5707a40 Admin Panel / Version: detect FerretDB via top-level ferretdbVersion
The wekan/FerretDB v1 fork's buildInfo reports a top-level ferretdbVersion
string (e.g. v1.24.2-60-gb5523566) + ferretdbFeatures, and its commit in
gitVersion -- not a ferretdb sub-document. Detection only checked
buildInfo.ferretdb, so the Version page showed Database type: MongoDB and
hid the FerretDB rows. Handle both shapes: top-level ferretdbVersion/
ferretdbFeatures and the ferretdb sub-document. Also confirm in the Sandstorm
doc that FerretDB writes <dir>/wekan.sqlite (+ -shm/-wal).
2026-07-11 05:40:14 +03:00
Lauri Ojansivu b8a7a2e114 Sandstorm: keep niscu migration, build from upstream 0.6.0 (drop projects.7z/releases.wekan.team)
- start.js: chain niscu (2.x) -> MongoDB 3.0 -> FerretDB; keep niscud + old
  bundled driver for the niscu->3.0 stage. Migration from old versions is
  permanent (not dropped).
- build-deps.sh (new): assemble a modern meteor-spk.deps on top of upstream
  meteor-spk 0.6.0 from dl.sandstorm.io (already has mongod 3.0 + niscud);
  swap in Node 24, add FerretDB + Mongo 3.x CLIs + launcher/importer, keep
  niscud. Extra binaries from GitHub releases. Nothing needed from projects.7z.
- sandstorm.yml: replace the dead releases.wekan.team/projects.7z download with
  build-deps.sh.
- sandstorm-pkgdef.capnp: WRITABLE_PATH -> /var/files.
- docs: keep-niscu + build-source corrections; migration support is permanent.
2026-07-11 05:07:43 +03:00
Lauri Ojansivu 1237e4c2de Sandstorm: add grain launcher sandstorm-src/start.js (Node24 + FerretDB + migration)
CJS meteor-spk.deps launcher: on grain start, if old MongoDB 3.0 data exists and
migration is not yet done, start mongod 3.0 (wait for ready), start FerretDB v1
(SQLite), run migrate-mongo3-to-ferretdb (text -> FerretDB, GridFS attachments/
avatars -> /var/files), mark done (old data kept); then run WeKan (Node 24) on
FerretDB steady-state. Paths resolve from __dirname (grain mount root). Update
the design doc to point at the canonical file and mark the in-app panel done.
2026-07-11 04:50:36 +03:00
Lauri Ojansivu 61792f59c1 gitignore: ignore local projects/ and sandstorm/ build working copies
projects/ (unarchived meteor-spk fork binaries) and sandstorm/ (clone of
sandstorm-io/sandstorm) are large, machine-specific working copies used only
when building the Sandstorm .spk; never commit them.
2026-07-11 04:47:42 +03:00
Lauri Ojansivu 664c6e1943 Sandstorm: Admin Panel / Attachments / Sandstorm migration panel
When isSandstorm, show a new Sandstorm section in Admin Panel / Attachments:
one-time MongoDB 3 -> FerretDB migration status, disk space used by the raw
MongoDB 3 files / FerretDB SQLite / attachments / avatars in the grain, and a
guarded button to delete the redundant raw MongoDB files (only after a
confirmed-successful migration, behind a confirm) to free grain disk space.

- server/methods/sandstormMigration.js: admin-gated sandstormMigrationStatus
  + sandstormDeleteRawMongo (isSandstorm-gated, env-overridable grain paths).
- client Attachments: new Sandstorm tab (jade + js), shown only when isSandstorm.
- imports/i18n/data/en.i18n.json: sandstorm-* UI strings.
- migrate-mongo3-to-ferretdb.mjs: optional STATUS_FILE with the final migration
  state, which the panel reads (shared by snap + the Sandstorm spk).
2026-07-11 04:39:24 +03:00
Lauri Ojansivu 9d90b869cd docs: move Sandstorm Meteor3 migration doc under FOSS/Sandstorm
Existing Sandstorm docs live under docs/Platforms/FOSS/Sandstorm/; move the
new Meteor3/Migration.md there (was mistakenly at docs/Platforms/Sandstorm/),
fix its relative links (one level deeper) and the CHANGELOG path.
2026-07-11 04:39:01 +03:00
Lauri Ojansivu 453770ef98 docs: Sandstorm Meteor3/Node24 + MongoDB3->FerretDB migration design
Add docs/Platforms/Sandstorm/Meteor3/Migration.md: how to build a modern
Sandstorm .spk (Node 24, FerretDB v1 SQLite) migrating an existing grain's
MongoDB 3.0 data on first launch, reusing the snap's migrate-mongo3-to-ferretdb
logic. Includes seccomp compatibility analysis, rewritten start.js, and a new
isSandstorm-only Admin Panel / Attachments / Sandstorm section design.
2026-07-11 04:29:24 +03:00
250 changed files with 8773 additions and 3086 deletions

No files matched your search

-2
View File
@@ -1,5 +1,3 @@
version: '3.7'
services:
wekandb-dev:
+107
View File
@@ -0,0 +1,107 @@
name: Build meteor-spk bundle
# Manually triggered. Assembles WeKan's modernized meteor-spk (the Sandstorm packaging
# tool + its meteor-spk.deps: Node 24, FerretDB, the Mongo 3.x CLIs and the modern
# sandstorm-http-bridge) and zips it as meteor-spk-YYYY-MM-DD_HH_MM_SS.zip — the same kind
# of self-contained meteor-spk bundle that https://github.com/sandstorm-io/meteor-spk
# releases, but with WeKan's Node 24 / FerretDB deps baked in. Download it to `meteor-spk
# pack` WeKan (or any Meteor 3.x app) without re-running build-deps.sh each time.
#
# gh workflow run meteor-spk.yml
#
# This only assembles + zips the tool; it does NOT pack or sign a WeKan .spk, so it needs
# no SANDSTORM_KEYRING. The .spk itself is built by sandstorm.yml; the Sandstorm App
# Market publish is done by sandstorm-store.yml.
on:
workflow_dispatch:
inputs:
ref:
description: 'Branch, tag or SHA to build the meteor-spk deps from (default: main)'
required: false
default: 'main'
permissions:
contents: write
env:
NODE_VERSION: '24'
jobs:
meteor-spk:
runs-on: ubuntu-24.04
timeout-minutes: 120
steps:
- uses: actions/checkout@v7
with:
ref: ${{ github.event.inputs.ref || 'main' }}
- uses: actions/setup-node@v6
with:
node-version: ${{ env.NODE_VERSION }}
- name: Enable unprivileged user namespaces (Ubuntu 24.04 restricts them)
# Same as sandstorm.yml: Ubuntu 24.04's AppArmor blocks the unprivileged user
# namespaces the Sandstorm install relies on; relax it so the install (whose
# sandstorm-http-bridge build-deps.sh copies in) can run on the runner.
run: |
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 || true
sudo sysctl -w kernel.unprivileged_userns_clone=1 2>/dev/null || true
- name: Install system dependencies
run: |
sudo apt-get update
sudo apt-get install -y p7zip-full wget curl build-essential g++ make python3 unzip xz-utils git zip
- name: Install Sandstorm (dev, unattended)
# build-deps.sh's [bridge] step copies the modern
# /opt/sandstorm/latest/bin/sandstorm-http-bridge into the deps, so Sandstorm
# must be installed first — same ordering as sandstorm.yml.
run: curl https://install.sandstorm.io | sudo bash -s -- -d
- name: Assemble modern meteor-spk.deps (Node 24 + FerretDB + Mongo 3.x CLIs)
# Base = upstream meteor-spk 0.6.0 from dl.sandstorm.io; build-deps.sh swaps in
# Node 24, FerretDB, the Mongo 3.x CLIs, the migration launcher/importer, keeps
# niscud, and swaps in the modern sandstorm-http-bridge. Produces
# $HOME/projects/meteor-spk/meteor-spk-0.6.0 (the meteor-spk tool + deps).
run: bash sandstorm-src/build-deps.sh
- name: Zip the meteor-spk bundle
id: zip
run: |
set -euo pipefail
STAMP="$(date +'%Y-%m-%d_%H_%M_%S')"
ZIP="meteor-spk-${STAMP}.zip"
BUNDLE_DIR="$HOME/projects/meteor-spk"
if [ ! -d "$BUNDLE_DIR/meteor-spk-0.6.0" ]; then
echo "::error::Expected meteor-spk bundle at $BUNDLE_DIR/meteor-spk-0.6.0 was not produced by build-deps.sh."
exit 1
fi
# Zip so it extracts to a top-level meteor-spk-0.6.0/ directory, like the
# upstream meteor-spk release archives. Exclude the base tarball build-deps.sh
# downloaded next to it.
( cd "$BUNDLE_DIR" && zip -r -y -q "$GITHUB_WORKSPACE/$ZIP" meteor-spk-0.6.0 -x '*.tar.xz' )
ZIP_BYTES=$(stat -c%s "$GITHUB_WORKSPACE/$ZIP")
echo "Packed $ZIP: $((ZIP_BYTES/1024/1024)) MiB ($ZIP_BYTES bytes)"
ls -la "$GITHUB_WORKSPACE/$ZIP"
echo "zip=$ZIP" >> "$GITHUB_OUTPUT"
- uses: actions/upload-artifact@v7
with:
name: ${{ steps.zip.outputs.zip }}
path: ${{ steps.zip.outputs.zip }}
retention-days: 7
- name: Upload the meteor-spk bundle to the newest WeKan release
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GH_REPO: ${{ github.repository }}
run: |
set -euo pipefail
TAG="$(gh release list --limit 1 --json tagName --jq '.[0].tagName' 2>/dev/null || true)"
if [ -z "${TAG:-}" ] || [ "$TAG" = "null" ]; then
echo "::warning::No existing GitHub Release found; the meteor-spk bundle is available only as a workflow artifact."
exit 0
fi
echo "Uploading ${{ steps.zip.outputs.zip }} to the newest release: $TAG"
gh release upload "$TAG" "${{ steps.zip.outputs.zip }}" --clobber
+205 -182
View File
@@ -11,9 +11,11 @@ name: Release All Platforms
# and arm64 (+ the win64/mac bundles). On every OTHER architecture that has a
# Node.js 24 build — ppc64le, s390x, riscv64 — there is no MongoDB, so those
# bundles ship FerretDB v1 instead: the wekan/FerretDB fork with its embedded
# pure-Go SQLite backend, which speaks the MongoDB wire protocol. The FerretDB
# binary is cross-compiled once (build-ferretdb) and baked into EVERY bundle, so
# amd64/arm64 users can opt into it too (WEKAN_DB=ferretdb, `snap set wekan
# pure-Go SQLite backend, which speaks the MongoDB wire protocol. FerretDB is
# built + released SEPARATELY (wekan/FerretDB, its own build.sh) as individual
# per-arch binaries; each bundle job downloads ONLY the ferretdb-<arch> binary for
# the platform it targets and bakes it in, so amd64/arm64 users can opt into it
# too (WEKAN_DB=ferretdb, `snap set wekan
# database=ferretdb`, or Docker env). Whichever backend is chosen binds the same
# MongoDB port, so MONGO_URL is unchanged. ppc64le/s390x/riscv64 are now covered
# by the Docker image as well (self-contained, FerretDB auto-started). riscv64
@@ -30,11 +32,11 @@ name: Release All Platforms
# - charts: updates and publishes the wekan/charts Helm chart and pushes,
# only AFTER the `docker` job has published the image (skipped if
# docker fails)
# - build-ferretdb: downloads the newest prebuilt ferretdb.zip from the
# wekan/FerretDB releases (FerretDB is built + released separately by
# its own build.sh — not compiled here); every bundle embeds its own
# - build-*: builds the amd64 bundle (full Meteor 3 build), then rebuilds native
# modules for arm64 from that amd64 base (each embeds its FerretDB)
# modules for arm64 from that amd64 base. Each bundle job downloads
# only the ferretdb-<arch> binary it needs from the newest wekan/FerretDB
# release (FerretDB is built + released separately by its own build.sh —
# not compiled here) and embeds it
# - release: creates the GitHub Release with the newest CHANGELOG.md notes and
# uploads the core wekan-<version>-{amd64,arm64}.zip bundles
# - build-win64 / build-mac-arm64 / build-extra-arches: built AFTER release, each
@@ -45,9 +47,13 @@ name: Release All Platforms
# never blocks it
# - docker: builds and pushes the multi-arch image (amd64, arm64, ppc64le, s390x,
# riscv64) to Docker Hub, Quay.io, GHCR
# - snap: builds the snap on Launchpad (amd64 + arm64), pushes it to the Snap
# Store and attaches the .snap files to the GitHub Release. `snap set
# wekan database=ferretdb` switches the running backend to FerretDB v1
# - snap: builds the snap on Launchpad from the default core24 snapcraft.yaml
# (platforms: amd64, arm64, s390x, ppc64el, riscv64), pushes it to the
# Snap Store candidate + beta + edge channels and attaches the .snap
# files to the GitHub Release. core24 allows candidate (core26 does
# not); the stable channel is published MANUALLY later, not here.
# `snap set wekan database=ferretdb` switches the running backend to
# FerretDB v1 (snapcraft-core26.yaml is the core26 variant)
#
# Required GitHub Secrets:
# GHCR_AUTH - base64("username:token") for ghcr.io
@@ -269,7 +275,7 @@ jobs:
# The full Meteor build always runs here on x86_64; every other platform then
# only rebuilds the native npm modules from this bundle.
build-amd64:
needs: [prepare, build-ferretdb]
needs: [prepare]
runs-on: ubuntu-24.04
timeout-minutes: 180
env:
@@ -319,11 +325,6 @@ jobs:
cd .build/bundle/programs/server
npm install
- name: Download ferretdb.zip
uses: actions/download-artifact@v8
with:
name: ferretdb-zip
- name: Embed Node.js, FerretDB (amd64) and launcher into the bundle
# Make the release .zip self-contained (offline): bundle Node.js + FerretDB
# + a start-wekan.sh that runs WeKan on the bundled Node against the bundled
@@ -336,10 +337,19 @@ jobs:
# matching this base bundle's arch.
cp -L "$(command -v node)" .build/bundle/node
chmod +x .build/bundle/node
# Bundled FerretDB (amd64) from the single-source ferretdb.zip.
unzip -o -j ferretdb.zip "ferretdb/amd64/ferretdb-amd64" -d .build/bundle
mv .build/bundle/ferretdb-amd64 .build/bundle/ferretdb
# Bundled FerretDB (amd64): download only this arch's binary from the
# newest wekan/FerretDB release (per-arch assets, no ferretdb.zip).
curl -fSL --retry 5 --retry-delay 10 -o .build/bundle/ferretdb \
"https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-amd64"
chmod +x .build/bundle/ferretdb
# Bundled MongoDB Database Tools (amd64) from wekan/mongo-tools (per-arch,
# no mongodb.com). This base amd64 bundle is inherited by the other Linux
# arches, which overwrite these with their own arch's tools below.
MT="https://github.com/wekan/mongo-tools/releases/latest/download"
for t in bsondump mongodump mongoexport mongofiles mongoimport mongorestore mongostat mongotop; do
curl -fSL --retry 5 --retry-delay 10 -o ".build/bundle/$t" "$MT/$t-amd64"
chmod +x ".build/bundle/$t"
done
# Self-contained launcher (defaults to FerretDB SQLite + WRITABLE_PATH).
cp releases/ferretdb/start-wekan.sh .build/bundle/
chmod +x .build/bundle/start-wekan.sh
@@ -357,7 +367,7 @@ jobs:
# ─── 3. Build arm64 bundle (rebuild native modules natively) ─────────────────
build-arm64:
needs: [prepare, build-amd64, build-ferretdb]
needs: [prepare, build-amd64]
runs-on: ubuntu-24.04-arm
timeout-minutes: 60
env:
@@ -396,20 +406,22 @@ jobs:
node:${NODE_VERSION}-slim \
sh -c "apt-get update -qq && apt-get install -y -q build-essential python3 && npm install"
- name: Download ferretdb.zip
uses: actions/download-artifact@v8
with:
name: ferretdb-zip
- name: Embed Node.js + FerretDB (arm64) into the bundle
# The launcher (start-wekan.sh) is inherited from the amd64 base bundle;
# swap bundle/node (runner is arm64 -> linux-arm64 Node 24) and bundle/ferretdb.
run: |
cp -L "$(command -v node)" bundle/node
chmod +x bundle/node
unzip -o -j ferretdb.zip "ferretdb/arm64/ferretdb-arm64" -d bundle
mv bundle/ferretdb-arm64 bundle/ferretdb
# Download only the arm64 FerretDB binary from the newest wekan/FerretDB release.
curl -fSL --retry 5 --retry-delay 10 -o bundle/ferretdb \
"https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-arm64"
chmod +x bundle/ferretdb
# Overwrite the inherited amd64 MongoDB Database Tools with arm64 ones.
MT="https://github.com/wekan/mongo-tools/releases/latest/download"
for t in bsondump mongodump mongoexport mongofiles mongoimport mongorestore mongostat mongotop; do
curl -fSL --retry 5 --retry-delay 10 -o "bundle/$t" "$MT/$t-arm64"
chmod +x "bundle/$t"
done
- name: Create arm64 zip
run: |
@@ -427,7 +439,6 @@ jobs:
- prepare
- build-amd64
- build-arm64
- build-ferretdb
runs-on: ubuntu-latest
env:
VERSION: ${{ needs.prepare.outputs.version }}
@@ -444,10 +455,11 @@ jobs:
tag_name: v${{ needs.prepare.outputs.version }}
name: v${{ needs.prepare.outputs.version }}
body: ${{ needs.prepare.outputs.changelog }}
# ferretdb.zip is NOT attached here: it already lives on the
# wekan/FerretDB releases (https://github.com/wekan/FerretDB/releases),
# which is where the WeKan builds fetch it from. The per-arch FerretDB
# binaries are embedded inside each wekan-<version>-<arch>.zip bundle.
# FerretDB binaries are NOT attached here: the per-arch ferretdb-<arch>
# binaries live on the wekan/FerretDB releases
# (https://github.com/wekan/FerretDB/releases), which is where the WeKan
# builds fetch them from. Each wekan-<version>-<arch>.zip bundle embeds
# its own arch's FerretDB binary.
files: |
wekan-${{ needs.prepare.outputs.version }}-amd64.zip
wekan-${{ needs.prepare.outputs.version }}-arm64.zip
@@ -462,7 +474,7 @@ jobs:
# Build win64 bundle (rebuild native modules on Windows).
build-win64:
needs: [prepare, build-amd64, release, build-ferretdb]
needs: [prepare, build-amd64, release]
runs-on: windows-latest
timeout-minutes: 60
env:
@@ -492,10 +504,12 @@ jobs:
shell: bash
run: |
7z x wekan-${VERSION}-amd64.zip
# Drop the Linux node + FerretDB binaries + POSIX launcher inherited from
# the amd64 base bundle; the Windows node.exe, ferretdb.exe and
# start-wekan.bat are added in a later step.
# Drop the Linux node + FerretDB binaries + MongoDB Database Tools + POSIX
# launcher inherited from the amd64 base bundle; the Windows node.exe,
# ferretdb.exe, *.exe tools and start-wekan.bat are added in later steps.
rm -f bundle/node bundle/ferretdb bundle/.ferretdb-default bundle/start-wekan.sh
rm -f bundle/bsondump bundle/mongodump bundle/mongoexport bundle/mongofiles \
bundle/mongoimport bundle/mongorestore bundle/mongostat bundle/mongotop
# Fix: bcrypt 5.0.1 (Meteor accounts-password) ships node-addon-api@3
# which fails to compile on Node.js 24. Replace with bcrypt 6.0.0.
BCRYPT_DIR="$(pwd)/bundle/programs/server/npm/node_modules/meteor/accounts-password/node_modules/bcrypt"
@@ -518,64 +532,43 @@ jobs:
rm -rf node_modules
npm install
- name: Add MongoDB tools, mongosh and start-wekan.bat to the bundle
- name: Add MongoDB Database Tools to the bundle
shell: bash
run: |
set -euo pipefail
# Use the same MongoDB tools/mongosh versions as the snap, which
# releases/version.sh keeps at the newest release for each bundle.
TOOLS_VER=$(grep -oE 'mongodb-database-tools-ubuntu2204-\$\{TOOLS_ARCH\}-[0-9]+\.[0-9]+\.[0-9]+' src/snapcraft.yaml \
| grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
MONGOSH_VER=$(grep -oE 'mongosh-[0-9]+\.[0-9]+\.[0-9]+-linux' src/snapcraft.yaml \
| grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
echo "MongoDB Database Tools: $TOOLS_VER mongosh: $MONGOSH_VER"
# MongoDB Database Tools (Windows): bsondump, mongodump, mongoexport,
# mongofiles, mongoimport, mongorestore, mongostat, mongotop.
TOOLS_DIR="mongodb-database-tools-windows-x86_64-${TOOLS_VER}"
curl -fL -o tools.zip \
"https://fastdl.mongodb.org/tools/db/${TOOLS_DIR}.zip"
7z x -y tools.zip > /dev/null
cp "${TOOLS_DIR}/bin/"*.exe bundle/
# mongosh (Windows): mongosh.exe + mongosh_crypt_v1.dll.
MONGOSH_DIR="mongosh-${MONGOSH_VER}-win32-x64"
curl -fL -o mongosh.zip \
"https://downloads.mongodb.com/compass/${MONGOSH_DIR}.zip"
7z x -y mongosh.zip > /dev/null
cp "${MONGOSH_DIR}/bin/mongosh.exe" bundle/
cp "${MONGOSH_DIR}/bin/mongosh_crypt_v1.dll" bundle/
# Windows launcher from the repo root.
cp src/start-wekan.bat bundle/
# MongoDB Database Tools (Windows) built by wekan/mongo-tools (pure Go),
# one <tool>-win64.exe per tool from that repo's newest release — no
# mongodb.com dependency. No mongosh: WeKan no longer bundles the MongoDB
# Shell; scripted DB access uses the bundled Node.js 24 + `mongodb` driver.
# (The Windows launcher, start-wekan.bat, is added by the FerretDB embed
# step below from releases/ferretdb/start-wekan.bat.)
BASE="https://github.com/wekan/mongo-tools/releases/latest/download"
for tool in bsondump mongodump mongoexport mongofiles mongoimport mongorestore mongostat mongotop; do
curl -fL --retry 5 --retry-delay 10 -o "bundle/${tool}.exe" "${BASE}/${tool}-win64.exe"
done
echo "=== bundle contents ==="
ls -1 bundle/
- name: Download ferretdb.zip
uses: actions/download-artifact@v8
with:
name: ferretdb-zip
- name: Embed Node.js, FerretDB (win64) and launcher into the bundle
shell: bash
# Make the Windows .zip self-contained: bundle node.exe (from the runner's
# win-x64 Node 24), ferretdb.exe (from the single-source ferretdb.zip) and
# start-wekan.bat. FerretDB embedding is tolerant: if it did not compile for
# windows/amd64 the bundle stays MongoDB-only (start-wekan.bat then won't
# find ferretdb.exe).
# win-x64 Node 24), ferretdb.exe (downloaded per-arch from the newest
# wekan/FerretDB release) and start-wekan.bat. FerretDB embedding is
# tolerant: if the win64 asset is missing the bundle stays MongoDB-only
# (start-wekan.bat then won't find ferretdb.exe).
run: |
# Bundled Node.js (win-x64 node.exe from setup-node).
NODE_SRC="$(command -v node)"
[ -f "$NODE_SRC" ] || NODE_SRC="${NODE_SRC}.exe"
cp "$NODE_SRC" bundle/node.exe
# Bundled FerretDB (win64).
if 7z e -y ferretdb.zip "ferretdb/win64/ferretdb-win64.exe" -obundle > /dev/null 2>&1 \
&& [ -f bundle/ferretdb-win64.exe ]; then
mv bundle/ferretdb-win64.exe bundle/ferretdb.exe
# Bundled FerretDB (win64): download only this arch's binary.
if curl -fSL --retry 5 --retry-delay 10 -o bundle/ferretdb.exe \
"https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-win64.exe"; then
echo "Embedded FerretDB win64 -> bundle/ferretdb.exe"
else
echo "No win64 FerretDB in ferretdb.zip; Windows bundle stays MongoDB-only."
rm -f bundle/ferretdb.exe
echo "No win64 FerretDB asset in the release; Windows bundle stays MongoDB-only."
fi
# Self-contained Windows launcher (defaults to FerretDB SQLite).
cp src/releases/ferretdb/start-wekan.bat bundle/
@@ -602,7 +595,7 @@ jobs:
# Build mac-arm64 bundle (rebuild native modules on Apple Silicon).
build-mac-arm64:
needs: [prepare, build-amd64, release, build-ferretdb]
needs: [prepare, build-amd64, release]
runs-on: macos-14 # macos-14 runners are Apple Silicon (arm64)
timeout-minutes: 60
env:
@@ -620,10 +613,12 @@ jobs:
- name: Rebuild native modules for macOS arm64
run: |
unzip -q wekan-${VERSION}-amd64.zip
# Replace the Linux node + FerretDB binaries inherited from the amd64 base
# bundle with the macOS builds (added in a later step). The POSIX launcher
# start-wekan.sh works on macOS, so keep it.
# Replace the Linux node + FerretDB binaries + MongoDB Database Tools
# inherited from the amd64 base bundle with the macOS builds (added in a
# later step). The POSIX launcher start-wekan.sh works on macOS, so keep it.
rm -f bundle/node bundle/ferretdb bundle/.ferretdb-default
rm -f bundle/bsondump bundle/mongodump bundle/mongoexport bundle/mongofiles \
bundle/mongoimport bundle/mongorestore bundle/mongostat bundle/mongotop
# Fix: bcrypt 5.0.1 (Meteor accounts-password) ships node-addon-api@3
# which fails to compile on Node.js 24. Replace with bcrypt 6.0.0.
BCRYPT_DIR="$(pwd)/bundle/programs/server/npm/node_modules/meteor/accounts-password/node_modules/bcrypt"
@@ -643,28 +638,30 @@ jobs:
npm install
cd ../../..
- name: Download ferretdb.zip
uses: actions/download-artifact@v8
with:
name: ferretdb-zip
- name: Embed Node.js + FerretDB (mac-arm64) into the bundle
# Bundle the macOS arm64 Node.js (runner's darwin-arm64 Node 24) and the
# macOS FerretDB binary from the single-source ferretdb.zip. FerretDB is
# tolerant: if it did not compile for darwin/arm64 the bundle stays
# MongoDB-only (start-wekan.sh then won't find ferretdb).
# macOS FerretDB binary, downloaded per-arch from the newest wekan/FerretDB
# release. FerretDB is tolerant: if the mac-arm64 asset is missing the
# bundle stays MongoDB-only (start-wekan.sh then won't find ferretdb).
run: |
cp -L "$(command -v node)" bundle/node
chmod +x bundle/node
if unzip -o -j ferretdb.zip "ferretdb/mac-arm64/ferretdb-mac-arm64" -d bundle >/dev/null 2>&1 \
&& [ -f bundle/ferretdb-mac-arm64 ]; then
mv bundle/ferretdb-mac-arm64 bundle/ferretdb
if curl -fSL --retry 5 --retry-delay 10 -o bundle/ferretdb \
"https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-mac-arm64"; then
chmod +x bundle/ferretdb
echo "Embedded FerretDB mac-arm64 -> bundle/ferretdb"
else
echo "No mac-arm64 FerretDB in ferretdb.zip; macOS bundle stays MongoDB-only."
rm -f bundle/ferretdb
echo "No mac-arm64 FerretDB asset in the release; macOS bundle stays MongoDB-only."
rm -f bundle/start-wekan.sh
fi
# macOS MongoDB Database Tools (mac-arm64) from wekan/mongo-tools; tolerant
# (skip any tool not built for macOS).
MT="https://github.com/wekan/mongo-tools/releases/latest/download"
for t in bsondump mongodump mongoexport mongofiles mongoimport mongorestore mongostat mongotop; do
curl -fSL --retry 5 --retry-delay 10 -o "bundle/$t" "$MT/$t-mac-arm64" \
&& chmod +x "bundle/$t" || { rm -f "bundle/$t"; echo "No $t-mac-arm64; skipping"; }
done
- name: Create mac-arm64 zip
run: zip -r wekan-${VERSION}-mac-arm64.zip bundle
@@ -683,39 +680,6 @@ jobs:
GH_REPO: ${{ github.repository }}
run: gh release upload "v${VERSION}" "wekan-${VERSION}-mac-arm64.zip" --clobber
# ─── Fetch the prebuilt standalone FerretDB binaries: ferretdb.zip ───────────
# WeKan normally uses MongoDB, but MongoDB Community only ships amd64/arm64
# server binaries. On every other platform WeKan can instead use FerretDB v1
# (the wekan/FerretDB fork with its embedded pure-Go SQLite backend, which
# speaks the MongoDB wire protocol). FerretDB is built + released SEPARATELY in
# the wekan/FerretDB repo (its build.sh cross-compiles every platform into
# ferretdb.zip and it is attached to a GitHub Release there); this workflow does
# NOT build FerretDB with Go. Here we just download the newest released
# ferretdb.zip and republish it, so every WeKan build (bundle .zip, snap, docker,
# win64, mac) takes its FerretDB binary from that same single source. The zip
# layout is ferretdb/<arch>/ferretdb-<arch>[.exe] + ferretdb/README.md.
build-ferretdb:
needs: prepare
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- name: Download the latest ferretdb.zip from wekan/FerretDB releases
run: |
set -euo pipefail
# /releases/latest/download/<asset> always resolves to the asset on the
# newest (non-prerelease) release of wekan/FerretDB.
url="https://github.com/wekan/FerretDB/releases/latest/download/ferretdb.zip"
echo "Downloading ${url} ..."
curl -fSL --retry 5 --retry-delay 10 -o ferretdb.zip "$url"
echo "=== ferretdb.zip contents ==="
unzip -l ferretdb.zip
- uses: actions/upload-artifact@v7
with:
name: ferretdb-zip
path: ferretdb.zip
retention-days: 1
# Extra-architecture Linux bundles (ppc64le, s390x, riscv64) — the arches that
# have a Node.js 24 build but NO MongoDB server, so they ship FerretDB instead.
# ppc64le and s390x use official nodejs.org binaries; riscv64 uses the
@@ -725,7 +689,7 @@ jobs:
# an armv7 device, regardless of RAM. See https://nodejs.org/dist/latest-v24.x/
# (no -linux-armv7l) and https://unofficial-builds.nodejs.org/ (riscv64 only).
build-extra-arches:
needs: [prepare, build-amd64, release, build-ferretdb]
needs: [prepare, build-amd64, release]
runs-on: ubuntu-24.04
timeout-minutes: 300
strategy:
@@ -815,20 +779,22 @@ jobs:
chmod +x /bundle/node
'
- name: Download ferretdb.zip
uses: actions/download-artifact@v8
with:
name: ferretdb-zip
- name: Embed FerretDB (${{ matrix.arch }}) into the bundle
# These arches have no MongoDB server, so FerretDB is their default DB.
# The launcher (start-wekan.sh) is inherited from the amd64 base
# bundle; swap in this arch's binary from ferretdb.zip. A marker file makes
# FerretDB the default backend at runtime (see the launcher + Docker entrypoint).
# The launcher (start-wekan.sh) is inherited from the amd64 base bundle;
# download only this arch's binary from the newest wekan/FerretDB release.
# A marker file makes FerretDB the default backend at runtime (see the
# launcher + Docker entrypoint).
run: |
unzip -o -j ferretdb.zip "ferretdb/${{ matrix.arch }}/ferretdb-${{ matrix.arch }}" -d bundle
mv bundle/ferretdb-${{ matrix.arch }} bundle/ferretdb
curl -fSL --retry 5 --retry-delay 10 -o bundle/ferretdb \
"https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-${{ matrix.arch }}"
chmod +x bundle/ferretdb
# Overwrite the inherited amd64 MongoDB Database Tools with this arch's ones.
MT="https://github.com/wekan/mongo-tools/releases/latest/download"
for t in bsondump mongodump mongoexport mongofiles mongoimport mongorestore mongostat mongotop; do
curl -fSL --retry 5 --retry-delay 10 -o "bundle/$t" "$MT/$t-${{ matrix.arch }}"
chmod +x "bundle/$t"
done
touch bundle/.ferretdb-default
- name: Create ${{ matrix.arch }} zip
@@ -991,11 +957,85 @@ jobs:
# ─── 9. Build the snap on Launchpad, push to the store, attach to release ────
# The snap's `wekan` part downloads wekan-<version>-<arch>.zip from the GitHub
# Release, so this job runs only after `release` has published those assets.
# `snapcraft remote-build` builds every platform listed in snapcraft.yaml
# (amd64 + arm64) on Launchpad.
snap:
# Release, so these jobs run only after `release` has published those assets.
#
# snap-native + snap-launchpad replace the old single `snap` job. The mainstream
# arches (amd64 + arm64) build NATIVELY on GitHub-hosted runners — fast, no
# Launchpad queue. The exotic arches (s390x, ppc64el, riscv64) have no native
# GitHub runners and snapcraft cannot cross-build, so they stay on Launchpad but
# in a NON-BLOCKING, per-arch matrix so a slow/failed arch (riscv64 queues for
# hours) never holds up the release or the other arches. Each arch publishes to
# the Snap Store (candidate + beta + edge) and attaches to the Release the moment
# it finishes — all 5 arches, published independently.
snap-native:
needs: [prepare, release]
strategy:
fail-fast: false
matrix:
include:
- arch: amd64
runner: ubuntu-24.04
- arch: arm64
runner: ubuntu-24.04-arm
runs-on: ${{ matrix.runner }}
env:
VERSION: ${{ needs.prepare.outputs.version }}
steps:
- uses: actions/checkout@v7
with:
ref: refs/tags/v${{ needs.prepare.outputs.version }}
- name: Verify snapcraft.yaml version matches the release
# snapcraft.yaml's `version:` names the produced file (wekan_<version>_<arch>.snap).
# Assert it matches the tag so a stale version fails fast here.
run: |
set -euo pipefail
if ! grep -qxF "version: '${VERSION}'" snapcraft.yaml; then
echo "::error::snapcraft.yaml is not at version '${VERSION}' ($(grep -m1 '^version:' snapcraft.yaml)). The bump job (releases/version.sh) did not update the tagged commit."
exit 1
fi
echo "snapcraft.yaml is at version '${VERSION}'."
- name: Build the ${{ matrix.arch }} snap natively
# Runs on a native ${{ matrix.arch }} GitHub runner, so snapcraft builds the
# platform whose `build-on` matches this host — no Launchpad, no emulation.
id: build
uses: snapcore/action-build@v1
- name: Verify the built snap is ${{ matrix.arch }}
run: |
set -euo pipefail
snap="${{ steps.build.outputs.snap }}"
echo "Built: $snap"
case "$snap" in
*_${{ matrix.arch }}.snap) : ;;
*) echo "::error::Built snap '$snap' is not ${{ matrix.arch }}."; exit 1 ;;
esac
- name: Push ${{ matrix.arch }} to the Snap Store (candidate + beta + edge)
uses: snapcore/action-publish@v1
env:
SNAPCRAFT_STORE_CREDENTIALS: ${{ secrets.SNAP_AUTH }}
with:
snap: ${{ steps.build.outputs.snap }}
release: candidate,beta,edge
- name: Attach the ${{ matrix.arch }} snap to the GitHub Release
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: gh release upload "v${VERSION}" "${{ steps.build.outputs.snap }}" --clobber
snap-launchpad:
needs: [prepare, release]
# continue-on-error: the exotic Launchpad arches must NOT hold up or fail the
# release. riscv64 in particular queues for hours / can time out; that must not
# turn the whole release red. fail-fast: false so one arch never cancels the
# others. Each leg publishes the moment it finishes.
continue-on-error: true
strategy:
fail-fast: false
matrix:
arch: [s390x, ppc64el, riscv64]
runs-on: ubuntu-latest
env:
VERSION: ${{ needs.prepare.outputs.version }}
@@ -1007,11 +1047,8 @@ jobs:
fetch-depth: 0
- name: Install snapcraft
# The Snap Store intermittently rejects the install with
# 'error: cannot install "snapcraft": too many requests' (a 429-style
# rate limit) that instantly fails the whole snap job before any build.
# Retry a few times so one transient store throttle does not fail the
# release (same spirit as the remote-build retry below).
# The Snap Store intermittently rejects the install with a 429-style rate
# limit; retry so one transient throttle does not fail the build.
run: |
set -uo pipefail
for i in 1 2 3 4 5; do
@@ -1031,15 +1068,6 @@ jobs:
chmod 600 ~/.local/share/snapcraft/launchpad-credentials
- name: Verify snapcraft.yaml version matches the release
# The `bump` job (releases/version.sh) is the single source of truth for
# the snap version and updates snapcraft.yaml before the tag is created.
# snapcraft.yaml's `version:` names the produced files
# (wekan_<version>_<arch>.snap), so if a stale tag carried the wrong
# version the build would produce wekan_<old>_*.snap and the upload/attach
# globs (wekan_${VERSION}_*.snap) would match nothing — passing the literal
# glob to `snapcraft upload` ("is not a valid file", exit 64). Assert it
# here so that mismatch fails fast (before a ~20 min Launchpad build) with
# a clear pointer, instead of re-bumping the version inside this build job.
run: |
set -euo pipefail
if ! grep -qxF "version: '${VERSION}'" snapcraft.yaml; then
@@ -1048,31 +1076,26 @@ jobs:
fi
echo "snapcraft.yaml is at version '${VERSION}'."
- name: Build snaps on Launchpad (amd64 + arm64)
# `snapcraft remote-build` is experimental and talks to Launchpad over
# HTTPS after pushing the whole repo; it intermittently dies with a
# transient TLS drop (e.g. "SSLEOFError: EOF occurred in violation of
# protocol", exit 70) that has nothing to do with the build itself.
# Retry a few times so one network hiccup doesn't fail the release.
- name: Build the ${{ matrix.arch }} snap on Launchpad
# --build-for ${{ matrix.arch }}: build ONLY this leg's arch so a slow/failed
# arch never blocks the others. remote-build can exit 0 without producing a
# .snap (it just downloads logs), so require the file. Retry a few times to
# survive transient TLS drops to Launchpad.
run: |
set -uo pipefail
shopt -s nullglob
attempts=3
for i in $(seq 1 "$attempts"); do
echo "::group::Remote build attempt $i/$attempts"
snapcraft remote-build --launchpad-accept-public-upload && rc=0 || rc=$?
echo "::group::Remote build ${{ matrix.arch }} attempt $i/$attempts"
snapcraft remote-build --launchpad-accept-public-upload \
--build-for ${{ matrix.arch }} && rc=0 || rc=$?
echo "::endgroup::"
# snapcraft remote-build can exit 0 even when the Launchpad build
# FAILED (it just downloads the build logs and produces no .snap), so
# don't trust the exit code alone — require that .snap files exist.
snaps=( wekan_${VERSION}_*.snap )
snaps=( wekan_${VERSION}_${{ matrix.arch }}.snap )
if [ "$rc" -eq 0 ] && [ "${#snaps[@]}" -gt 0 ]; then
echo "Remote build succeeded on attempt $i: ${snaps[*]}"
echo "Remote build ${{ matrix.arch }} succeeded on attempt $i: ${snaps[*]}"
exit 0
fi
echo "Attempt $i: snapcraft exit=$rc, .snap files produced=${#snaps[@]}."
# Surface the Launchpad build logs so a real build failure is
# diagnosable here, instead of as a later cryptic upload error.
for log in snapcraft-wekan-*.txt; do
echo "::group::Launchpad build log: $log (last 150 lines)"
tail -n 150 "$log"
@@ -1083,34 +1106,34 @@ jobs:
sleep 60
fi
done
echo "::error::Remote build failed after $attempts attempts (no wekan_${VERSION}_*.snap produced)." >&2
echo "::error::Remote build ${{ matrix.arch }} failed after $attempts attempts (no wekan_${VERSION}_${{ matrix.arch }}.snap produced)." >&2
exit 1
- name: Push snaps to the Snap Store (edge + beta channels)
- name: Push ${{ matrix.arch }} to the Snap Store (candidate + beta + edge)
env:
SNAPCRAFT_STORE_CREDENTIALS: ${{ secrets.SNAP_AUTH }}
run: |
set -euo pipefail
shopt -s nullglob
snaps=( wekan_${VERSION}_*.snap )
snaps=( wekan_${VERSION}_${{ matrix.arch }}.snap )
if [ "${#snaps[@]}" -eq 0 ]; then
echo "::error::No wekan_${VERSION}_*.snap files to upload."
echo "::error::No wekan_${VERSION}_${{ matrix.arch }}.snap to upload."
exit 1
fi
# base: core24 allows publishing to candidate (core26 does not). Stable is
# published MANUALLY later, once the build has proven stable enough.
for f in "${snaps[@]}"; do
echo "Uploading $f to the Snap Store (edge,beta)..."
snapcraft upload --release=edge,beta "$f"
echo "Uploading $f to the Snap Store (candidate,beta,edge)..."
snapcraft upload --release=candidate,beta,edge "$f"
done
- name: Attach snaps to the GitHub Release
- name: Attach the ${{ matrix.arch }} snap to the GitHub Release
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
set -euo pipefail
shopt -s nullglob
snaps=( wekan_${VERSION}_*.snap )
if [ "${#snaps[@]}" -eq 0 ]; then
echo "::error::No wekan_${VERSION}_*.snap files to attach."
exit 1
snaps=( wekan_${VERSION}_${{ matrix.arch }}.snap )
if [ "${#snaps[@]}" -gt 0 ]; then
gh release upload "v${VERSION}" "${snaps[@]}" --clobber
fi
gh release upload "v${VERSION}" "${snaps[@]}" --clobber
+145
View File
@@ -0,0 +1,145 @@
name: Publish .spk to Sandstorm App Market
# Manually triggered. Takes the Sandstorm .spk that sandstorm.yml already built and
# attached to a WeKan GitHub Release, renames it to wekan-<VERSION>.spk (VERSION is the
# WeKan release version, e.g. 9.88), and publishes it to the Sandstorm App Market with
# spk publish wekan-<VERSION>.spk
# exactly like releases/release-sandstorm.sh does locally.
#
# gh workflow run sandstorm-store.yml
# gh workflow run sandstorm-store.yml -f version=9.88
# gh workflow run sandstorm-store.yml -f version=9.88 -f tag=v9.88
#
# Needs SANDSTORM_KEYRING (base64 of ~/.sandstorm-keyring) — `spk publish` proves app
# ownership with the WeKan Sandstorm app's private key from that keyring — and installs
# Sandstorm + assembles meteor-spk the same way sandstorm.yml does, so `spk` is present.
# It does NOT rebuild the .spk; it publishes the one already on the release.
on:
workflow_dispatch:
inputs:
version:
description: 'WeKan version for the store filename wekan-<VERSION>.spk (e.g. 9.88). Default: derived from the release tag.'
required: false
default: ''
tag:
description: 'Release tag whose .spk to publish (default: newest release).'
required: false
default: ''
permissions:
contents: read
env:
NODE_VERSION: '24'
jobs:
sandstorm-store:
runs-on: ubuntu-24.04
timeout-minutes: 120
steps:
- uses: actions/checkout@v7
- uses: actions/setup-node@v6
with:
node-version: ${{ env.NODE_VERSION }}
- name: Enable unprivileged user namespaces (Ubuntu 24.04 restricts them)
run: |
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 || true
sudo sysctl -w kernel.unprivileged_userns_clone=1 2>/dev/null || true
- name: Install system dependencies
run: |
sudo apt-get update
sudo apt-get install -y p7zip-full wget curl build-essential g++ make python3 unzip xz-utils git
- name: Install Sandstorm (dev, unattended)
# Provides the `spk` command used to publish, and the sandstorm-http-bridge that
# build-deps.sh copies into the meteor-spk deps.
run: curl https://install.sandstorm.io | sudo bash -s -- -d
- name: Assemble modern meteor-spk.deps (same as sandstorm.yml)
run: |
bash sandstorm-src/build-deps.sh
echo "$HOME/projects/meteor-spk/meteor-spk-0.6.0" >> "$GITHUB_PATH"
- name: Restore the Sandstorm signing keyring
env:
SANDSTORM_KEYRING: ${{ secrets.SANDSTORM_KEYRING }}
run: |
if [ -n "${SANDSTORM_KEYRING:-}" ]; then
# spk publish reads the app signing key from ~/.sandstorm-keyring (a FILE in
# $HOME), same location meteor-spk pack uses.
printf '%s' "$SANDSTORM_KEYRING" | base64 -d > "$HOME/.sandstorm-keyring"
chmod 600 "$HOME/.sandstorm-keyring"
echo "Restored ~/.sandstorm-keyring ($(wc -c < "$HOME/.sandstorm-keyring") bytes)."
else
echo "::error::SANDSTORM_KEYRING secret is not set. 'spk publish' proves ownership of the WeKan Sandstorm app with the private key from this keyring, so publishing cannot proceed without it. Add the base64 of your ~/.sandstorm-keyring file as the SANDSTORM_KEYRING repository secret (e.g. 'base64 -w0 ~/.sandstorm-keyring')."
exit 1
fi
- name: Download the newest .spk from the WeKan release and name it wekan-<VERSION>.spk
id: fetch
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GH_REPO: ${{ github.repository }}
IN_TAG: ${{ github.event.inputs.tag }}
IN_VERSION: ${{ github.event.inputs.version }}
run: |
set -euo pipefail
# 1) Which release to publish from.
TAG="${IN_TAG:-}"
if [ -z "$TAG" ]; then
TAG="$(gh release list --limit 1 --json tagName --jq '.[0].tagName' 2>/dev/null || true)"
fi
if [ -z "${TAG:-}" ] || [ "$TAG" = "null" ]; then
echo "::error::No release found to publish the .spk from."
exit 1
fi
# 2) VERSION for the store filename wekan-<VERSION>.spk. Use the input, else
# derive it from the tag (strip a leading 'v', e.g. v9.88 -> 9.88).
VERSION="${IN_VERSION:-}"
if [ -z "$VERSION" ]; then
VERSION="${TAG#v}"
fi
echo "Release: $TAG -> store filename: wekan-${VERSION}.spk"
# 3) Download the newest .spk asset on that release. sandstorm.yml attaches it
# as wekan-sandstorm-YYYY_MM_DD-HH_MM_SS.spk; if several exist, take the
# lexicographically-newest (the timestamp sorts chronologically).
ASSET="$(gh release view "$TAG" --json assets \
--jq '[.assets[].name | select(endswith(".spk"))] | sort | last' 2>/dev/null || true)"
if [ -z "${ASSET:-}" ] || [ "$ASSET" = "null" ]; then
echo "::error::Release $TAG has no .spk asset. Run sandstorm.yml first to build and attach one."
exit 1
fi
echo "Downloading .spk asset: $ASSET"
gh release download "$TAG" --pattern "$ASSET" --dir . --clobber
SPK="wekan-${VERSION}.spk"
mv -f "$ASSET" "$SPK"
ls -la "$SPK"
echo "spk=$SPK" >> "$GITHUB_OUTPUT"
- name: Publish to the Sandstorm App Market
env:
SPK: ${{ steps.fetch.outputs.spk }}
run: |
set -euo pipefail
# Resolve the spk binary: prefer PATH, then the Sandstorm install location.
SPK_BIN="$(command -v spk || true)"
if [ -z "$SPK_BIN" ]; then
for c in /opt/sandstorm/latest/bin/spk /opt/sandstorm/spk /usr/local/bin/spk; do
[ -x "$c" ] && SPK_BIN="$c" && break
done
fi
if [ -z "$SPK_BIN" ]; then
echo "::error::Could not find the 'spk' command from the Sandstorm install."
exit 1
fi
echo "Publishing $SPK with $SPK_BIN ..."
# Same command as releases/release-sandstorm.sh: spk publish wekan-<VERSION>.spk
"$SPK_BIN" publish "$SPK"
+58 -14
View File
@@ -15,6 +15,11 @@ name: Build Sandstorm .spk
on:
workflow_dispatch:
inputs:
ref:
description: 'Branch, tag or SHA to build the .spk from (default: main)'
required: false
default: 'main'
permissions:
contents: write
@@ -29,53 +34,92 @@ jobs:
steps:
- uses: actions/checkout@v7
with:
ref: main
# Build the dispatched ref so a fix branch can be tested before it is
# merged to main; defaults to main for a plain `gh workflow run`.
ref: ${{ github.event.inputs.ref || 'main' }}
- uses: actions/setup-node@v6
with:
node-version: ${{ env.NODE_VERSION }}
- name: Enable unprivileged user namespaces (Ubuntu 24.04 restricts them)
# Ubuntu 24.04's AppArmor defaults kernel.apparmor_restrict_unprivileged_userns=1,
# which blocks the unprivileged user namespaces that the Sandstorm install and
# the spk supervisor rely on (the "fragile part" noted above). Relax it so
# `install.sandstorm.io` and meteor-spk can create sandboxes on the runner.
# `|| true`: on kernels/runners without these knobs, setting them is a no-op.
run: |
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 || true
sudo sysctl -w kernel.unprivileged_userns_clone=1 2>/dev/null || true
- name: Install system dependencies and Meteor
run: |
sudo apt-get update
sudo apt-get install -y p7zip-full wget curl build-essential g++ make python3 unzip
sudo apt-get install -y p7zip-full wget curl build-essential g++ make python3 unzip xz-utils git
if [ ! -f "$HOME/.meteor/meteor" ]; then curl https://install.meteor.com/ | sh; fi
echo "$HOME/.meteor" >> "$GITHUB_PATH"
- name: Install meteor-spk
run: |
cd "$HOME"
wget -q https://releases.wekan.team/dev/meteor-spk/projects.7z
7z x projects.7z >/dev/null
rm -f projects.7z
echo "$HOME/projects/meteor-spk/meteor-spk-0.6.0" >> "$GITHUB_PATH"
- name: Install Sandstorm (dev, unattended)
# Installed BEFORE assembling the deps: build-deps.sh's [bridge] step copies
# the modern /opt/sandstorm/latest/bin/sandstorm-http-bridge over the ancient
# bundled one, so the Sandstorm install must be in place first.
run: curl https://install.sandstorm.io | sudo bash -s -- -d
- name: Assemble modern meteor-spk.deps (Node 24 + FerretDB + Mongo 3.x CLIs)
# Base = upstream meteor-spk 0.6.0 from dl.sandstorm.io (has mongod 3.0 +
# niscud). build-deps.sh swaps in Node 24, adds FerretDB + the Mongo 3.x
# CLIs + the migration launcher/importer, keeps niscud, and swaps in the
# modern sandstorm-http-bridge from the Sandstorm install above. No dependency
# on the retired releases.wekan.team or the old projects.7z.
run: |
bash sandstorm-src/build-deps.sh
echo "$HOME/projects/meteor-spk/meteor-spk-0.6.0" >> "$GITHUB_PATH"
- name: Restore the Sandstorm signing keyring
env:
SANDSTORM_KEYRING: ${{ secrets.SANDSTORM_KEYRING }}
run: |
if [ -n "${SANDSTORM_KEYRING:-}" ]; then
mkdir -p "$HOME/.sandstorm"
printf '%s' "$SANDSTORM_KEYRING" | base64 -d > "$HOME/.sandstorm/sandstorm-keyring"
chmod 600 "$HOME/.sandstorm/sandstorm-keyring"
# meteor-spk / spk read the app signing key from ~/.sandstorm-keyring —
# a FILE directly in $HOME (see the pack crash path
# "/home/runner/.sandstorm-keyring"). Write it exactly there, NOT to
# ~/.sandstorm/sandstorm-keyring, or `meteor-spk pack` aborts with
# "open(~/.sandstorm-keyring): No such file or directory".
printf '%s' "$SANDSTORM_KEYRING" | base64 -d > "$HOME/.sandstorm-keyring"
chmod 600 "$HOME/.sandstorm-keyring"
echo "Restored ~/.sandstorm-keyring ($(wc -c < "$HOME/.sandstorm-keyring") bytes)."
else
echo "::warning::SANDSTORM_KEYRING secret not set; meteor-spk pack may fail to sign the app update."
echo "::error::SANDSTORM_KEYRING secret is not set. meteor-spk pack signs the .spk with the WeKan Sandstorm app's private key, which lives in this keyring, so packing cannot proceed without it. Add the base64 of your ~/.sandstorm-keyring file as the SANDSTORM_KEYRING repository secret (e.g. 'base64 -w0 ~/.sandstorm-keyring')."
exit 1
fi
- name: Install Meteor npm dependencies
# PUPPETEER_SKIP_DOWNLOAD: puppeteer is a devDependency used only by tests,
# not by the server, so it never belongs in the packed .spk. Skipping its
# Chromium download (~150 MB) avoids any risk of it bloating the build and
# speeds up CI.
env:
PUPPETEER_SKIP_DOWNLOAD: '1'
run: |
(meteor update --npm 2>/dev/null || true) && meteor npm install
- name: Build the Sandstorm .spk
id: build
env:
PUPPETEER_SKIP_DOWNLOAD: '1'
run: |
set -euo pipefail
STAMP="$(date +'%Y_%m_%d-%H_%M_%S')"
SPK="wekan-sandstorm-${STAMP}.spk"
meteor-spk pack "$SPK"
# Report the packed size and warn if it exceeds Cloudflare's 100 MB upload
# cap (a proxied browser upload to a Cloudflare-fronted Sandstorm 413s above
# this; install via a DNS-only host / SSH tunnel, or trim further).
SPK_BYTES=$(stat -c%s "$SPK")
echo "Packed $SPK: $((SPK_BYTES/1024/1024)) MiB ($SPK_BYTES bytes)"
if [ "$SPK_BYTES" -gt $((100*1024*1024)) ]; then
echo "::warning::$SPK is $((SPK_BYTES/1024/1024)) MiB — over Cloudflare's 100 MB upload limit. Upload via a DNS-only host / SSH tunnel to Sandstorm, or trim the bundle further."
fi
ls -la "$SPK"
echo "spk=$SPK" >> "$GITHUB_OUTPUT"
+14
View File
@@ -70,3 +70,17 @@ test-results/
_build-local-test
*/build-assets-local-test
*/build-chunks-local-test
# Local-only working copies: other wekan repos cloned under this repo for editing,
# and build inputs. These are separate git repos / large machine-specific dirs;
# never commit them.
# - projects/ : unarchived meteor-spk fork (Node/Mongo/FerretDB binaries)
# - sandstorm/ : clone of sandstorm-io/sandstorm (platform source, for reference)
# - FerretDB/ : clone of wekan/FerretDB
# - mongo-tools/ : clone of wekan/mongo-tools
# - mongosh/ : clone of wekan/mongosh
/projects/
/sandstorm/
/FerretDB/
/mongo-tools/
/mongosh/
+609 -11
View File
@@ -2,21 +2,13 @@
Newest WeKan at these platforms:
- [Install](https://wekan.fi/install/)
- [Upgrade WeKan](https://wekan.fi/upgrade/)
- [bundle zip at releases](https://github.com/wekan/wekan/releases), docs at https://wekan.fi/docs/
- [Linux amd64, arm64, s390x, ppc64le](https://github.com/wekan/wekan/blob/main/docs/Platforms/FOSS/RaspberryPi/Raspberry-Pi.md)
- [Windows amd64/arm64](https://github.com/wekan/wekan/blob/main/docs/Platforms/Propietary/Windows/Offline.md)
- [Mac arm64](https://github.com/wekan/wekan/blob/main/docs/Platforms/Propietary/Mac.md)
- https://wekan.fi/install/
- Snap Beta amd64/arm64
- Docker amd64/arm64
- Kubernetes Docker amd64/arm64
- Bitnami MongoDB Docker images do not exist anymore. [MongoDump/MongoRestore to groundhog2k MongoDB images](https://github.com/wekan/charts/issues/45)
- [Docs](https://wekan.fi/docs/)
Versions:
- WeKan 8.75 and newer uses Meteor 3.5-rc.x, [Node.js 24.x](https://nodejs.org/dist/latest-v24.x/),
MongoDB 7.x (or 6.x), or [FerretDB2/PostgreSQL](https://github.com/wekan/wekan/blob/main/docs/Databases/FerretDB2-PostgreSQL.md)
- WeKan 8.75 and newer uses Meteor 3.5
- WeKan 8.43 upgraded to Meteor 3.x, huge thanks to harryadel:
- https://harryadel.com/dev-diary-24/
- https://harryadel.com/dev-diary-25/
@@ -94,6 +86,612 @@ them up next.
same `params.user` feeds both the e-mail notification text, where the full name is intended, and the webhook payload,
where a username is expected; the safe change is to ADD a `username` field to the webhook rather than repurpose `user`).
# v9.89 2026-07-13 WeKan ® release
This release fixes the following CRITICAL SECURITY ISSUE of
[SortBleed](https://wekan.fi/hall-of-fame/sortbleed/):
- **[SortBleed](https://github.com/wekan/wekan/security/advisories/GHSA-xm8x-c8wg-jhmf):
a low-privilege (comment-only / read-only) board member could escalate to board admin and take
over a private board via the board `sort` collection-allow rule**
([GHSA-xm8x-c8wg-jhmf](https://github.com/wekan/wekan/security/advisories/GHSA-xm8x-c8wg-jhmf),
CWE-863 Incorrect Authorization, CWE-269 Improper Privilege Management). Same broken-access-control
class as [BoardBleed](https://wekan.fi/hall-of-fame/boardbleed/) (CVE-2026-55234) — a Meteor
collection allow-rule field conflation — but on the Board document itself. To support drag-to-reorder
on the All Boards / Public Boards pages, a second `Boards.allow({ update })` rule returned `true` for
any board member whenever the update touched the `sort` field. Meteor evaluates allow rules with OR
semantics and does **not** scope an approving rule to the field that satisfied it: once any allow
callback returns `true` and no deny callback returns `true`, the **entire** modifier is applied.
Because `canUpdateBoardSort` only checked that `sort` was **among** the modified fields (not that it
was the **only** one), a comment-only / read-only member could smuggle arbitrary board mutations into
the same `$set` as `sort` in a single unprivileged DDP `Boards.update` call:
`{$set: {sort: 99, members: [...only themselves as admin...], permission: 'public', title: '...'}}`.
The member could therefore make themselves board admin, flip a private board to public (world-readable
in Wekan), rename it, and evict the legitimate owner. The last-admin deny rule did not help because it
only inspected `$pull`, so a wholesale `$set` of the `members` array bypassed it entirely.
- **Fixed** by restricting `canUpdateBoardSort` (`server/lib/utils.js`) so the sort-reorder rule
approves an update **only** when `sort` is the sole modified field (`fieldNames` is exactly
`['sort']`) — it can no longer approve a modifier that also mutates `members`, `permission`, `title`
or anything else. As defense in depth, the last-admin deny rule (`server/permissions/boards.js`) now
also rejects a `$set` rewrite of the `members` array that would drop the last active admin, not just
a `$pull`. A regression test covers the multi-field smuggling case
(`server/lib/tests/boards.security.tests.js`). The legitimate All Boards drag-reorder is unaffected:
it persists the order per-user in `profile.boardSortIndex` (`Users.setBoardSortIndex`), not in the
board document. CVSS:3.1 8.8 High (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
- Affected Wekan v9.85 and earlier through the current release; fixed at the upcoming WeKan release.
Reported by **5ud0 / Tarmo Technologies**.
Thanks to 5ud0 / Tarmo Technologies and xet7.
and adds the following updates:
- Update Sandstorm WeKan info.
[Part 1](https://github.com/wekan/wekan/commit/1bf68f54b29ab29a54abb90f777a88be4aa45d7e),
[Part 2](https://github.com/wekan/wekan/commit/ade9f16db459708200f4d7677c3877f1cdc837a4),
[Part 3](https://github.com/wekan/wekan/commit/0d90011affcf3789ed3ea820db5f3402ad1019b3).
Thanks to xet7.
Thanks to above GitHub users for their contributions and translators for their translations.
# v9.88 2026-07-13 WeKan ® release
This release adds the following new features:
- [Added docs about new Sandstorm WeKan](https://github.com/wekan/wekan/commit/9f23e6384bdfa5ca81be18e4f0426c347e9894eb).
Thanks to xet7.
and fixes the following bugs:
- **Sandstorm build: fixed "not writing through dangling symlink" that failed the
`sandstorm.yml` workflow at `sandstorm-src/build-deps.sh` step [3/7]**. The
meteor-spk 0.6.0 base ships some runtime libs in `meteor-spk.deps/lib` as
DANGLING symlinks (e.g. `libstdc++.so.6` → a library that no longer exists), so
refreshing them with the host's newer libs failed: `cp -fL` refuses to write
through a dangling destination symlink. Added `--remove-destination` so `cp`
deletes the existing destination (dangling symlink included) before copying the
host's real library. Thanks to xet7.
- **Sandstorm build: write the signing keyring to the path `meteor-spk pack`
actually reads**. The `sandstorm.yml` "Restore the Sandstorm signing keyring"
step wrote the decoded `SANDSTORM_KEYRING` secret to `~/.sandstorm/sandstorm-keyring`,
but `meteor-spk` / `spk` read the app private key from `~/.sandstorm-keyring` (a
file directly in `$HOME`), so packing aborted with
`open(~/.sandstorm-keyring): No such file or directory` even when the secret was
set. Now it writes `~/.sandstorm-keyring`, and — since the `.spk` cannot be signed
without it — fails early with an actionable message when the secret is missing,
instead of the cryptic later crash. Thanks to xet7.
- **Sandstorm .spk: trim it back toward Cloudflare's 100 MB upload limit**. The
Sandstorm build no longer bundles the ~300 MB of modern MongoDB Database Tools
(wekan/mongo-tools) — they are unused in Sandstorm (grains back up/restore
themselves; the MongoDB 3 → FerretDB migration uses the legacy migratemongo CLIs
+ the `.mjs` importer). Also set `PUPPETEER_SKIP_DOWNLOAD=1` for the Meteor build
(puppeteer is a test-only devDependency, so its ~150 MB Chromium never belongs in
the `.spk`), and the pack step now prints the `.spk` size and warns if it exceeds
100 MB. (The Database Tools remain in the WeKan `.zip` bundle / Docker / Snap,
which do use them.) Thanks to xet7.
- [Sandstorm .spk: bundle the matching glibc dynamic loader so grains start](https://github.com/wekan/wekan/commit/143607ef22ae91803cb611053fd4ce00754e7096):
the `.spk` bundled the host's new glibc `libc.so.6` (Ubuntu 24.04, glibc 2.39)
but kept the old glibc 2.31 `ld-linux` from the meteor-spk 0.6.0 base, so `node`
failed at startup with `libc.so.6: undefined symbol: _dl_audit_symbind_alt,
version GLIBC_PRIVATE` (HTTP-BRIDGE exit 127) and the grain crash-looped.
`sandstorm-src/build-deps.sh` now also copies the host's `ld-linux-x86-64.so.2`
so the loader and libc are the same glibc, and adds a `[verify]` gate that fails
the build if they differ or the bundled `node` cannot run under them — turning a
silent grain crash-loop into a loud build failure. Thanks to xet7.
- [Sandstorm build workflow: enable unprivileged user namespaces and build the dispatched branch](https://github.com/wekan/wekan/commit/66d8706c4d2afab4d127f8c63e05d43407efaf30):
Ubuntu 24.04 defaults `kernel.apparmor_restrict_unprivileged_userns=1`, which
blocks the unprivileged user namespaces the Sandstorm install and the `spk`
supervisor rely on, so `sandstorm.yml` now relaxes it on the runner. A new `ref`
`workflow_dispatch` input also lets the workflow build a fix branch before it is
merged, instead of a hardcoded `main`. Thanks to xet7.
- [Meteor unit tests: fix server-boot crash from `__dirname` in an ESM test file](https://github.com/wekan/wekan/commit/60116bc72f68c7bc0aa56a7d5700e33b98e870af):
`server/lib/tests/dependencies.openapi.tests.js` is an ES module that referenced
the bare `__dirname` global; under Node 24 / Meteor 3.5 the compiler injects
`const __dirname = fileURLToPath(import.meta.url)`, colliding with the `__dirname`
the CommonJS module wrapper already provides, so the server bundle failed to boot
with `Identifier '__dirname' has already been declared` and the "Meteor unit
tests" CI job died before any test ran. Drop the `__dirname` seed
(`process.env.PWD` already reaches the repo root under `meteor test`). Thanks to xet7.
- [Sandstorm .spk: point FerretDB state dir to writable /var so the grain starts](https://github.com/wekan/wekan/commit/1c28b40fd41acd9b9e21671548411f25e55464b8):
FerretDB persists a `state.json` (version/UUID) via its state provider even with
telemetry disabled, and its `--state-dir` defaults to `.` — which in a Sandstorm
grain is `/`, read-only. So FerretDB failed with `Failed to create state
provider: failed to persist state: open /state.json: read-only file system`,
exited (code 1), and the grain crash-looped. `sandstorm-src/start.js` now creates
`/var/ferretdb` and passes `--state-dir=/var/ferretdb` (plus `FERRETDB_STATE_DIR`)
in `startFerret()`, covering both the migration and steady-state FerretDB launches.
Thanks to xet7.
- [Sandstorm .spk: don't crash the grain when capnp.node can't load on Node 24](https://github.com/wekan/wekan/commit/f4f22bbe24e10659cc80cd1efeb6b4890b58ea49):
WeKan on Sandstorm bundles Node 24, but `capnp.node` (node-capnp) is built for an
older Node ABI (NODE_MODULE_VERSION 83 = Node 14), so `Npm.require('capnp')` in
`sandstorm.js` failed with `ERR_DLOPEN_FAILED` and crash-looped the whole grain on
boot. Cap'n Proto is now loaded lazily in a `try/catch` and degrades gracefully:
the grain boots and core WeKan works, because login and user identity come from
the sandstorm-http-bridge `X-Sandstorm-*` HTTP headers (`wekan-accounts-sandstorm`)
and need no Cap'n Proto. Only the two capnp-only features are skipped when the
addon cannot load — the Powerbox identity-claim method and Sandstorm activity
notifications — with a clear warning. They can be restored by rebuilding node-capnp
for Node 24, or reimplemented over the bridge's HTTP/JSON API. Thanks to xet7.
- [Snap release: build amd64+arm64 natively on GitHub, exotic arches non-blocking on Launchpad](https://github.com/wekan/wekan/commit/8549a62c85f43ad48e8f049eead64691c3f1dbf0):
the single snap job ran `snapcraft remote-build` for all 5 platforms on Launchpad
and blocked until the slowest resolved, so the release hung ~3.5h on riscv64's
Launchpad queue even though amd64+arm64 finished in minutes. It is now split in
two: `snap-native` builds amd64 (`ubuntu-24.04`) and arm64 (`ubuntu-24.04-arm`)
natively on GitHub runners via `snapcore/action-build`; `snap-launchpad` builds
s390x/ppc64el/riscv64 on Launchpad in a non-blocking (`continue-on-error`),
per-arch matrix (`remote-build --build-for <arch>`) so a slow or failed exotic
arch never delays the release or the other arches. Each arch publishes to the
Snap Store (candidate,beta,edge) and attaches to the GitHub Release the moment it
finishes — all 5 arches still ship. Thanks to xet7.
- [Sandstorm .spk: fix server-boot crashes from stale globals (Users, HTTP) in sandstorm.js](https://github.com/wekan/wekan/commit/60e40199c965460b95528ef9ea07281172c2d9b6):
once the capnp load was made non-fatal, the grain reached the rest of
`sandstorm.js` and hit two latent Meteor-2.x-isms the Meteor 3.x migration missed
(this file only runs on Sandstorm, so it was not exercised): it referenced the
`Users`/`Boards`/`Swimlanes`/`Activities` collections as implicit globals, but
those are now ES module default exports, so `Users.after.insert` threw
`Users is not defined` at boot; and it monkey-patched `HTTP.methods` from the
removed `meteor/http` package, so `HTTP` was undefined. The collections (and
`Accounts`) are now imported explicitly, and the obsolete `HTTP.methods` patch is
removed. Thanks to xet7.
- [Sandstorm .spk: use boolean index options so FerretDB accepts the users index](https://github.com/wekan/wekan/commit/975316f5cd6e81b6ea8ae6ede588d26055f9f649):
`wekan-accounts-sandstorm` created the unique index on `services.sandstorm.id`
with `{unique: 1, sparse: 1}`. Real MongoDB accepts the truthy `1`, but FerretDB
(used by the Sandstorm `.spk`) is strict and rejects it with `The field 'unique'
has value unique: 1, which is not convertible to bool`, crashing the grain at boot
during index creation. Now uses real booleans (`unique: true, sparse: true`).
Thanks to xet7.
- [Sandstorm .spk: strip Accept-Encoding so the grain doesn't serve corrupted (gzip) content](https://github.com/wekan/wekan/commit/013b6b5266be34326e36762b1a50e212237b109d):
the grain boots, but the page failed to load with a browser "Corrupted Content
Error" (`NS_ERROR_NET_CORRUPTED_CONTENT`). `sandstorm-http-bridge` advertises
`Accept-Encoding: gzip` to the app regardless of what the browser actually sent,
so Meteor served gzip/brotli-encoded responses the browser could not decode. A
`WebApp.rawHandlers` middleware now strips `Accept-Encoding` (it runs before
Meteor's static/boilerplate serving) so responses go out uncompressed; bandwidth
is a non-issue behind the local bridge. Thanks to xet7.
- [Sandstorm .spk: bundle a modern sandstorm-http-bridge to fix "Corrupted Content"](https://github.com/wekan/wekan/commit/7f0706e45f26aa0937a15a2a8f7336df63830511):
the grain boots, but the page failed with a browser "Corrupted Content Error"
(`NS_ERROR_NET_CORRUPTED_CONTENT`) on WeKan's `/` redirect. The meteor-spk 0.6.0
base bundles an ancient (~2016) `sandstorm-http-bridge` that mangles responses
(it always advertises `Accept-Encoding: gzip` to the app and mishandles
redirect/encoding). `build-deps.sh` now overwrites the bundled
`/sandstorm-http-bridge` with the modern one from a Sandstorm install
(`/opt/sandstorm/latest/bin/sandstorm-http-bridge`; override with
`SANDSTORM_HTTP_BRIDGE`), and `sandstorm.yml` installs Sandstorm before assembling
the deps so the bridge is available on the CI runner. Thanks to xet7.
- [Sandstorm .spk: fix the "/" redirect (malformed Location + Content-Length mismatch)](https://github.com/wekan/wekan/commit/ccdd1a0846ffed64546265c38263c7e1b8530480):
the grain's `/` served a broken `301`: the `Location` was `.../:6080board` because
`FlowRouter.path()` does not resolve on the server in Meteor 3.x (it returned the
bare route name `board`), and the response advertised `Content-Length: 90` while
sending an empty body — which the browser rejected as a "Corrupted Content Error"
(`NS_ERROR_NET_CORRUPTED_CONTENT`). The handler now builds the board path directly
(`/b/:id/:slug`) and sends a real HTML body (meta refresh + link) with a matching
`Content-Length`, so the redirect to the hard-coded Sandstorm board works. Thanks
to xet7.
- [Sandstorm .spk: open the grain on the All Boards page, not a hard-coded board](https://github.com/wekan/wekan/commit/b5945cf596be546b9440854ee9c39520c3c715c0):
WeKan on Sandstorm originally opened a single hard-coded board
(`/b/sandstorm/libreboard`) and redirected `/` to it. It now supports many boards
and that board is no longer the right destination, so the `WebApp.handlers.get("/")`
redirect is removed entirely — `/` now falls through to WeKan's normal serving,
whose client `home` route renders the **All Boards** list, the right landing page
for a multi-board grain. This also removes the last server-side redirect the
browser was rejecting as a Corrupted Content Error. Thanks to xet7.
- [Sandstorm .spk: don't auto-create a board; map grain permissions to global role](https://github.com/wekan/wekan/commit/8f11e8ac66d7348f62e8cf9278f4196b44c719b0):
a new grain/user no longer gets a hard-coded `sandstorm`/libreboard board
auto-created — WeKan on Sandstorm is multi-board now, so the user creates their own
boards from the All Boards page. `updateUserPermissions` previously added the user
as a member of that single board (which would now crash since the board no longer
exists); it now maps the grain's Sandstorm permissions to the user's **global**
WeKan role — `configure` (grain owner) becomes a WeKan admin, everyone else is a
regular user who can create and manage their own boards. Thanks to xet7.
- [Sandstorm .spk: set SANDSTORM=1 so the header-based auto-login runs](https://github.com/wekan/wekan/commit/b0712e6656ce33bfe7c360547185fea04660c9f7):
WeKan loaded in the grain but every page showed "Must be logged in". The
`wekan-accounts-sandstorm` client only starts the automatic `X-Sandstorm-*` header
login when `__meteor_runtime_config__.SANDSTORM` is set, and the package only sets
that when `process.env.SANDSTORM` is present — which nothing did. The launcher now
sets `process.env.SANDSTORM = '1'` before loading the WeKan bundle, so the client
auto-logs-in the Sandstorm user from the headers. Thanks to xet7.
- [Sandstorm .spk: rewrite ROOT_URL per request to the grain URL (fixes login + CORS)](https://github.com/wekan/wekan/commit/d5f707fd37b63ff038f61d7aa1316d5800859b35):
WeKan loaded but stayed on "Must be logged in", and the console showed
`Cross-Origin Request Blocked … http://127.0.0.1:4000/__meteor__/dynamic-import/fetch`.
The launcher sets a fixed `ROOT_URL` (`http://127.0.0.1:4000`, the internal bridge
target), but Sandstorm serves each grain at a per-session host
(`ui-<hash>.<host>`), so the client sent its DDP connection and dynamic-import
fetches to `127.0.0.1:4000` — cross-origin and unreachable — and the header-based
login handshake (a DDP method call) never completed. A `WebApp.addRuntimeConfigHook`
now rewrites `ROOT_URL` to the grain's real base URL (`X-Sandstorm-Base-Path`) per
request, so DDP, dynamic imports and the Sandstorm auto-login work. Thanks to xet7.
- [Sandstorm .spk: bounce from sign-in to the boards list once auto-login lands](https://github.com/wekan/wekan/commit/6f3174b23d7072a383703a5fe03711090fe9f844):
the Sandstorm login was actually succeeding (`Meteor.userId()` gets set), but the
grain stayed on the sign-in page. WeKan's home route checks `Meteor.userId()` once
and, because the Sandstorm header login is asynchronous and uses
`connection.setUserId()` (bypassing accounts-base, so `Accounts.onLogin` never
fires), finds it still null on first render and redirects to `atSignIn` — where the
user is stranded even after login completes. A Sandstorm-only reactive autorun now
sends the user from `atSignIn` back to `home` as soon as `Meteor.userId()` is set,
so the grain lands on the All Boards page. Thanks to xet7.
- [Sandstorm .spk: keep the grain URL in sync with the in-app route](https://github.com/wekan/wekan/commit/68e59ab66f68d1c60bc10c954c50999809e5381b):
navigating between boards worked but the Sandstorm shell's grain URL never updated
(it stayed on the grain root), unlike standalone WeKan. The path was synced via a
global `FlowRouter.triggers.enter` callback, which does not fire reliably on client
navigation in this flow-router-extra / Meteor 3 setup; it is now synced from a
reactive `Tracker.autorun` on `FlowRouter.watchPathChange()` (the same mechanism
the title sync uses), so every route change updates the grain URL to
`/grain/<id><path>`. Thanks to xet7.
- [Sandstorm .spk: upload attachments over DDP (bridge strips Meteor-Files' HTTP headers)](https://github.com/wekan/wekan/commit/dc8ff6e6ca3093298d5e07f2c8726f597d672449):
adding a file to a card in the grain failed with HTTP 400 `Can't continue upload,
session expired [408]` and the file silently disappeared. Meteor-Files' HTTP
upload signals the first chunk with an `x-start` header and tracks the session
with `x-mtok`/`x-chunkid`/`x-fileid`/`x-eof`, but Sandstorm's request-header
whitelist does not include them, so the `sandstorm-http-bridge` strips them — the
server never sees `x-start`, treats every request as a chunk continuation, cannot
find the session and returns 408. Attachment uploads now use `transport: 'ddp'` on
Sandstorm (DDP method calls, no custom HTTP headers); HTTP transport is kept
everywhere else. Thanks to xet7.
- [Sandstorm .spk: authorize attachment/avatar downloads via X-Sandstorm-User-Id](https://github.com/wekan/wekan/commit/1ca7bd3bb6016f560aaa3f748bbb23cec514acf0):
once uploads worked, the uploaded image still showed as a broken thumbnail,
minicard cover and slideshow in the grain — the file was on disk but the download
returned HTTP 403. The download route (`server/routes/universalFileServer.js`)
authorizes files on private boards with a Meteor login token (Authorization /
X-Auth-Token / `authToken` query / `meteor_login_token` cookie), but Sandstorm has
none of these: authentication is via `connection.setUserId()` and the
`sandstorm-http-bridge` `X-Sandstorm-*` request headers, so `extractLoginToken()`
returned null and `isAuthorizedForBoard()` denied every request. Sandstorm already
gates grain access at the platform level, so any request that reaches WeKan is an
authenticated grain user — both `isAuthorizedForBoard()` and
`isAuthorizedForAvatar()` now allow when `Meteor.settings.public.sandstorm` is set
and the request carries the bridge-injected `X-Sandstorm-User-Id` header. Gating on
the setting means a spoofed header cannot bypass auth on non-Sandstorm deployments.
Thanks to xet7.
- [Sandstorm .spk: open All Boards (not sign-in) and keep the grain URL in sync](https://github.com/wekan/wekan/commit/3ab2b9dccbf3b32dd510d4634af88a1b9eb8513c):
two grain-navigation regressions against the last working Sandstorm build (v6.15).
(1) Opening a grain showed *"Must be logged in"* instead of the All Boards page: on
Sandstorm the platform authenticates the user asynchronously over DDP via
`connection.setUserId()`, which (unlike a password login) does not set
`Meteor.loggingIn()`, so `Meteor.userId()` is null for the first moments after the
grain opens — and useraccounts' `ensureSignedIn` trigger plus `renderBoardList()`
both bounced that brief null window to the `atSignIn` route, a sign-in page that
does not exist inside a grain. `config/router.js` now uses a Sandstorm-aware
`ensureSignedInUnlessSandstorm` wrapper (a no-op on Sandstorm) and
`renderBoardList()` no longer redirects on Sandstorm; the list renders and fills in
reactively once the login lands. (2) The Sandstorm shell's outer grain URL did not
update when switching boards — the shell rewrites `/grain/<id><path>` when the app
posts a `{ setPath }` message, but the sync was a bare top-level `Tracker.autorun`
that could run before flow-router-extra's reactive path tracking was ready and then
never re-run. Restored v6.15's event-driven `FlowRouter.triggers.enter` (fresh
entering path, order-independent) and kept a `watchPathChange()` autorun wrapped in
`Meteor.startup` as a backup. Thanks to xet7.
- [Sandstorm .spk: fix the MongoDB 3 → FerretDB migration of an existing grain](https://github.com/wekan/wekan/commit/3f5c70e6435c5305cb165eeb866fc1ac88f58dd0):
importing an old WeKan grain crash-looped in the one-time migration — mongod 3.0
forked and its child aborted with exit code 14. Two bugs. (1) *WiredTiger
cache_size=0G*: mongod 3.0 sizes its WiredTiger cache from detected RAM
(`RAM/2 − 1GB`), but inside a Sandstorm grain sandbox RAM detection returns 0, so it
computed `cache_size=0G` and WiredTiger refused to open (minimum is 1MB), logging
*"Value too small for key 'cache_size'"* / *"Fatal Assertion 28561"* to
`/var/migration-mongod.log` before aborting. Both mongod invocations (the niscu →
3.0 stage and the 3.0 → FerretDB stage) now pass an explicit
`--wiredTigerCacheSizeGB 1` so the cache size never depends on RAM detection
(mongod 3.0.7 parses this option as an integer number of GB — a decimal like `0.25`
fails with `Bad digit "."`, [fixed to `1`](https://github.com/wekan/wekan/commit/0804cd19e) —
and it is a cache cap, not a preallocation). The data
itself is intact (the *"unclean shutdown"* notice is harmless —
WiredTiger recovers from the last checkpoint). (2) *Wrong source database*:
Sandstorm WeKan grains store their data in the Meteor-default database `meteor`, but
the importer was told `SRC_DB=wekan`, so even once mongod started it would have
exported zero collections; only the FerretDB *target* database is `wekan`. Thanks to
xet7.
- [Sandstorm/Snap migration: import mongodb and bson as default (CommonJS) exports under Node 24](https://github.com/wekan/wekan/commit/a5bcb2e27c070643f17c9ed62ca6284564da1c51):
with the WiredTiger cache fixed mongod 3.0 started and the migration importer ran,
but crashed immediately on its named imports — `import { EJSON } from 'bson'` and
`import { MongoClient } from 'mongodb'` each threw *"Named export '…' not found. The
requested module is a CommonJS module"*. Both packages, as bundled in WeKan's server
`node_modules`, are CommonJS, so Node 24's ESM loader exposes no named exports on
them. Import the default and destructure, as Node's own error message advises (bson in
the commit linked above; [mongodb in the same way](https://github.com/wekan/wekan/commit/50abd8f95)).
Shared by the Snap MongoDB 3 → FerretDB migration too (same Node 24). Thanks to xet7.
- [Sandstorm/Snap migration: connect mongoexport over IPv4 so it can read the old data](https://github.com/wekan/wekan/commit/6142396ae9f95872f5b2ff0e3ee889e519fd56e8):
with the importer finally running, every `mongoexport` of a source collection failed
— at first silently (its own [`--quiet` flag suppressed the reason](https://github.com/wekan/wekan/commit/3076f2317)),
and once that was
dropped the real error showed: *"error connecting to db server: no reachable
servers"*. `mongoexport` is a Go tool whose `--host` defaults to `localhost`, which
resolves to `::1` (IPv6) first, but the migration `mongod` listens only on
`--bind_ip 127.0.0.1` (IPv4); the mongo shell defaults its host to `127.0.0.1` and so
connected fine (it listed all 42 collections), which is why only the shell worked.
Pass `--host 127.0.0.1` explicitly. The one-time progress dashboard also now shows a
live Activity panel (mongoexport-ready line, per-collection export/insert counts, GridFS
extraction counts) with a [spinner and an auto-updating timestamp](https://github.com/wekan/wekan/commit/62df99153),
so it is
clear what the migration is doing rather than sitting on *"(waiting…)"*. Thanks to
xet7.
- [Sandstorm/Snap migration: resolve bson/mongodb from the modern server bundle so EJSON exists](https://github.com/wekan/wekan/commit/beefe441d):
once mongoexport connected, every collection failed with *"Cannot read properties of
undefined (reading 'parse')"* — `EJSON` was undefined. The importer script sits at the
deps root right next to the OLD meteor-spk 0.6.0 base `node_modules` (kept only for the
niscu → 3.0 stage): its `bson` is 1.x with no `EJSON` at all, and its `mongodb` is
ancient — it has `MongoClient` (so the connection worked) but no `EJSON` re-export. A
bare `import`/`require` from the script resolved those adjacent old copies, so every
way of reaching `EJSON` (bare `bson`, `mongodb.EJSON`) came back undefined. WeKan's
current `bson` 7.3 and mongodb driver (with `EJSON`) live under
`programs/server/npm/node_modules`; [anchor `createRequire`](https://github.com/wekan/wekan/commit/0e0a8bbb3)
inside that modern bundle
first (falling back to the deps root) and load both `mongodb` and `bson` through it —
which also moves the importer to the same modern mongodb driver the WeKan app uses
against FerretDB. An upfront guard fails loudly with a diagnostic list if `EJSON.parse`
is still unreachable. Thanks to xet7.
- [Sandstorm/Snap migration: insert into FerretDB with the modern mongodb driver (OP_MSG)](https://github.com/wekan/wekan/commit/cab231ee3):
text collections exported and *"inserted N/N"* was logged, but every document actually
failed with *"Unsupported OP_QUERY command: update"* — nothing reached FerretDB.
`requireAny('mongodb')` had resolved the ancient meteor-spk base driver (v2.x, at the
deps root) because the modern driver is not directly under
`programs/server/npm/node_modules` — Meteor nests it at
`…/meteor/npm-mongo/node_modules/mongodb` (v6.16). The 2.x driver speaks legacy
OP_QUERY, which FerretDB rejects; the 6.x driver speaks OP_MSG (the same driver the
WeKan app uses against FerretDB). Add the npm-mongo path as the first resolver anchor,
and log the resolved driver version. Thanks to xet7.
- [Sandstorm/Snap migration: extract Meteor-Files GridFS attachments + parse legacy v1 binary](https://github.com/wekan/wekan/commit/3476cd17c):
with text migrating, attachments still produced 0 files and *"parse attachments.chunks:
Unexpected Binary Extended JSON format"*. Two causes. (1) mongo 3.x `mongoexport` writes
binary as legacy Extended JSON v1 `{"$binary":"<b64>","$type":"00"}`, but modern bson
`EJSON.parse` only accepts v2 `{"$binary":{"base64":…,"subType":…}}` — rewrite v1→v2 per
line before parsing. (2) The grain stores attachments in Meteor-Files' own GridFS buckets
(`attachments.files` + `attachments.chunks`, with the FilesCollection record in the
`attachments` collection), not CollectionFS's `cfs_gridfs.*`. Reassemble those buckets to
disk, link each GridFS file to its record via `metadata.fileId`/`versionName`, then repoint
the record's `versions.<v>` at the file and drop `versions.<v>.meta.gridFsFileId` —
otherwise WeKan's `getFileStrategy` keeps choosing the now-empty GridFS backend and the
image 404s. Verified end to end on a real grain: boards/cards/lists/swimlanes migrate and
all 3 attachments extract and display. Thanks to xet7.
- [Sandstorm/Snap migration: auto-open All Boards after migrating, WeKan-themed dashboard](https://github.com/wekan/wekan/commit/b8bdbcd2d):
the one-time progress dashboard used to sit on the grain URL for 60s after completion,
forcing a manual reload to reach WeKan. On success the importer now hands off quickly and
the done page polls `/` until WeKan's app shell answers (riding out the brief
importer→WeKan port hand-off) and then opens All Boards, with the spinner still spinning so
it is clear the grain is still working. The dashboard is also recoloured to WeKan's
blue/white/grey. Thanks to xet7.
- **Avatars and original members now travel with a board (export/import), from every
identity source.** A board could be moved between servers (or imported into Sandstorm)
but member avatars vanished — they lived in Sandstorm / LDAP / OAuth2, not in WeKan —
and original members were collapsed onto the importing user by a mapping that could
attach the wrong person and leak board permissions. Now:
- [External avatars are localized into WeKan's own files/avatars](https://github.com/wekan/wekan/commit/ac8bedfef),
triggered when a board is opened and at login, from any source — Sandstorm profile
picture, LDAP [`jpegPhoto`/`thumbnailPhoto`](https://github.com/wekan/wekan/commit/c258d862d),
OAuth2/OIDC `picture` claim, gravatar or a pasted URL — every network fetch guarded
against SSRF (http/https only; no private, loopback, link-local or cloud-metadata
address; timeout + size + image-type caps). ([board-open trigger](https://github.com/wekan/wekan/commit/5a38ca3ca).
Inside a Sandstorm grain outbound fetch is sandboxed, so a still-external Sandstorm
picture is a best-effort no-op there — but any avatar that is already a local file
exports/imports fully, grain included.)
- [Board export embeds each member's local avatar file as base64](https://github.com/wekan/wekan/commit/92c769fd1)
alongside their username, fullname and initials — never passwords, emails or services.
- [Board import preserves the original members as inert placeholder users](https://github.com/wekan/wekan/commit/aff3017ff)
(`authenticationMethod:'imported'`, `loginDisabled`, `isActive:false`, no secrets),
reusing each original `_id` so card/comment/activity references resolve to the right
person with NO mapping at import time, and restores their avatar. The importer stays
the sole admin; imported members hold no permissions until reconciled.
- [Reconciliation maps placeholders to the valid accounts deliberately, later](https://github.com/wekan/wekan/commit/6985281d5):
an admin sweep merges each placeholder into a matching real account (provisioned by
LDAP/OIDC at login) by reassigning every reference, and leaves the rest inactive
(e.g. a person not in LDAP); a one-off admin merge is available too.
- [Avatars visibly distinguish account state](https://github.com/wekan/wekan/commit/fae20c8bc),
on card avatars and in the right-sidebar member list: a dashed ring + amber "?" badge
for un-reconciled imported placeholders, greyscale + dim for inactive members, and the
sidebar now lists everyone (active first, then inactive) instead of hiding inactive
members. Thanks to xet7.
Thanks to above GitHub users for their contributions and translators for their translations.
# v9.87 2026-07-11 WeKan ® release
This release fixes the following bugs:
- [Normal users cannot move cards between swimlanes](https://github.com/wekan/wekan/commit/b227a931933a3a8abff67c1084f9561b8847f444):
in the swimlanes view the `.js-swimlanes` sortable — which also carries moving a
card from one swimlane to another — was disabled for every non-admin
(`!isBoardAdmin()`), even though its own comment said it should be disabled only
for non-members. So ordinary board members could move a card within a swimlane
but not between swimlanes, and could not reorder swimlanes. Now it is disabled
only for users without write access (`!canModifyCard()`: comment-only, worker,
read-only), so board members can move cards between swimlanes again.
Thanks to xet7.
Thanks to above GitHub users for their contributions and translators for their translations.
# v9.86 2026-07-11 WeKan ® release
This release fixes the following bugs:
- [At default docker-compose.yml, changed DDP_TRANSPORT from uws to sockjs, because uws does not work at s390x](https://github.com/wekan/wekan/commit/aa5847f21561957216a34a7f6a61699f427971c8).
Thanks to xet7.
- **FerretDB v1 is now downloaded as an individual per-arch binary, not `ferretdb.zip`**:
the wekan/FerretDB release now attaches one `ferretdb-<arch>` (`.exe` on Windows)
asset per platform instead of a single multi-platform `ferretdb.zip`. Every WeKan
build path now downloads only the one binary for the platform it targets from
`https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-<arch>`:
`release-all.yml` (the amd64/arm64/win64/mac/ppc64le/s390x/riscv64 bundle jobs —
the separate `build-ferretdb` job and its `ferretdb-zip` artifact are removed),
the default `docker-compose.yml`, and the Sandstorm `sandstorm-src/build-deps.sh`.
FerretDB itself also moved its Go toolchain to 1.25.11 to clear the Quay.io
`stdlib` security advisories. Thanks to xet7.
- **Drop the `mongosh` binary; use bundled Node.js 24 + the `mongodb` driver instead**:
WeKan no longer bundles or downloads the MongoDB Shell anywhere (snap, Windows
bundle). Every scripted database operation it was used for — readiness `ping`,
replica-set `initiate`/`status`, and the v8.43 schema migration — now runs
through the new `snap-src/bin/db-eval` (a tiny wrapper around the bundled Node.js
24 + the `mongodb` driver), so the snap control scripts (`wekan-control`,
`mongodb-control`, `migration-control`), the `start-wekan.sh`/`start-wekan.bat`
launchers, and the ported `migrate-schema-v843.mjs` are all mongosh-free. This
removes a large, CVE-prone binary and works identically on every architecture
(including s390x/ppc64le/riscv64, which have no prebuilt mongosh). The legacy
MongoDB 3.2 `mongo` shell (migratemongo, amd64) stays for migration-time reads
only. Thanks to xet7.
- **MongoDB Database Tools now come from `wekan/mongo-tools`, not the MongoDB website**:
every WeKan build downloads the per-arch `<tool>-<arch>` binaries (bsondump,
mongodump, mongoexport, mongofiles, mongoimport, mongorestore, mongostat,
mongotop) built by the [wekan/mongo-tools](https://github.com/wekan/mongo-tools)
fork (pure Go, cross-compiled for every architecture) from its newest release,
replacing the `fastdl.mongodb.org` / `downloads.mongodb.com` downloads. They are
embedded in the Linux `.zip` bundles (amd64/arm64/s390x/ppc64le/riscv64) — and
therefore in the Docker image, which is built from those bundles — the Windows
and macOS bundles, the Snap (`mongotools` part), and the Sandstorm `.spk`. The
MongoDB 7 server (mongod) is still fetched from MongoDB (amd64/arm64 only), since
MongoDB ships no server for the other architectures; the legacy MongoDB 3.2 CLIs
(migratemongo, amd64) remain only for the one-time MongoDB 3 migration. Thanks to xet7.
- **Snap: the default `snapcraft.yaml` is now the `base: core24`, `grade: stable` build**:
the previous `snapcraft.yaml` (core26, `grade: devel`) is renamed to
`snapcraft-core26.yaml`, and the former `snapcraft-core24.yaml` becomes
`snapcraft.yaml`. Because the default is `base: core24` (a released base), it can
be published to the Snap **candidate** channel, which core26 cannot. The automated
`release-all.yml` workflow publishes the snap to the **candidate + beta + edge**
channels; the **stable** channel is published manually later, once it is proven
stable enough. Thanks to xet7.
Thanks to above GitHub users for their contributions and translators for their translations.
# v9.85 2026-07-11 WeKan ® release
This release adds the following features and fixes:
- **Docker: FerretDB v1 + SQLite is now the default `docker-compose.yml`**:
The default database for `docker compose up -d` is now **FerretDB v1 with embedded
SQLite** (from https://github.com/wekan/FerretDB) — light and self-contained, no
separate database server. The compose files were renamed accordingly:
`docker-compose-ferretdb-v1-sqlite.yml` -> **`docker-compose.yml`** (the new default),
and the previous MongoDB default `docker-compose.yml` -> **`docker-compose-mongodb-v7.yml`**.
The other files are unchanged: `docker-compose-ferretdb-v2-postgresql.yml` (FerretDB 2
+ PostgreSQL) and `docker-compose-multitenancy.yml` (MongoDB multitenancy). To use
MongoDB 7, run `docker compose -f docker-compose-mongodb-v7.yml up -d` or rename that
file to `docker-compose.yml`. `rebuild-wekan.sh` / `rebuild-wekan.bat` Docker menus now
list FerretDB v1 SQLite first (default) and point at the new filenames, the compose
files' own header comments were updated, and the Docker docs now describe which
compose file maps to which database. The Docker menus also gained a **Build from
source & start (up -d --build)** action per compose file, which builds the wekan-app
image from the local `Dockerfile` (tagged as the image the compose file references)
and starts that freshly built container instead of a possibly-stale prebuilt image —
useful when a change (e.g. the FerretDB Version-page detection) isn't in the pulled
image yet. Finally, the obsolete `version:` attribute (which Docker Compose v2 warns
about and ignores) was removed from all compose files (`docker-compose.yml`,
`docker-compose-mongodb-v7.yml`, `docker-compose-ferretdb-v2-postgresql.yml`,
`docker-compose-multitenancy.yml`, `.devcontainer/docker-compose.yml`, and the
ToroDB docs example).
- **rebuild-wekan.sh / rebuild-wekan.bat: reorganized into category submenus + Docker start/logs/stop**:
The long flat menu is now grouped into a short top-level menu — **Setup**,
**Dev server**, **Tests**, **Docker**, **Tools**, **Quit** — each opening a small
submenu with `0) Back`, so you read only a handful of items at a time and labels
are shorter (the category provides the context). **Docker** is a two-stage submenu:
pick a backend (MongoDB `docker-compose.yml`, FerretDB v1 SQLite, FerretDB v2
PostgreSQL, MongoDB Multitenancy), then an action — **Start** (`up -d`),
**Follow logs** (`logs -f`) or **Stop** (`down`) — which removes the previous
repetition of 12 near-identical entries. The `.sh` auto-detects `docker compose`
vs legacy `docker-compose`. All existing actions are unchanged, just regrouped.
- **rebuild-wekan.sh / rebuild-wekan.bat: Dev server options now stop the previous
server (including the rspack :8080 dev server) before starting, plus a new "Kill
all dev servers" option, and docs updated for the new menu**:
Every **Dev server** option (`localhost:3000`, `+ trace warnings`, `+ bundle
visualizer`, `CURRENT-IP:3000`, `CURRENT-IP:3000 + MONGO_URL 27019`, and
`CUSTOM-IP:PORT`) now stops any Meteor dev server already running before starting a
fresh one, so re-running a dev option no longer fails because a port is taken — no
need to hunt down and kill the old processes yourself. Crucially it frees **both**
the app port **and the rspack dev-server port `8080`**: `meteor run` starts an rspack
dev server on 8080 that can outlive the `meteor` parent, and a leftover one made the
restart crash with `Error: listen EADDRINUSE ... :8080`. Port detection now checks the
listening socket directly (`ss`/`lsof`, with a bash `/dev/tcp` fallback that needs no
external tools, and `netstat` on `.bat`) instead of an HTTP probe, so it also catches
a server that is still building. A new **Dev server -> Kill all dev servers** option
frees every dev/test port the scripts use at once — the dev app (3000) and its Mongo
(3001), the Mocha test server (3100) and its Mongo (3101), a Sandstorm standalone dev
server (4000) and its Mongo (4001), and the rspack dev server (8080) — killing meteor,
the rspack watcher and Meteor's bundled `--replSet meteor` Mongos (never a
production/system Mongo). Both scripts escalate to SIGKILL if a port does not free up.
Also updated the build-from-source docs (README.md, Build-from-source.md,
Build-and-Create-Pull-Request.md, Emoji.md, and the two Sandstorm developer docs) to
the new two-level menu (**Setup -> Install dependencies**, **Setup -> Build WeKan**,
**Dev server -> localhost:3000**) and fixed a stale dev-server port
(`localhost:4000` -> `3000`).
- **FerretDB: quieter logs, and removed a dead MongoDB-driver-selection subsystem**:
On FerretDB (SQLite), the driver debug logs revealed a second, TLS-enabled Mongo
monitor connection retrying every ~0.5s and being rejected by the plaintext FerretDB
port, which FerretDB logged at WARN (`Connection stopped … invalid message length` /
`before secure TLS connection was established`) — harmless (WeKan runs fine on the real
plaintext connection) but very noisy. FerretDB is now started with `--log-level=error`
in all bundled launch points (Docker entrypoint, snap `ferretdb-control`, the release
`start-wekan.sh`, and the `docker-compose-ferretdb-v1-sqlite.yml` example), which drops
the per-connection WARN spam. Separately removed a **dead, unused "MongoDB Driver System"**
(`server/mongodb-driver-startup.js` + `models/lib/{meteorMongoIntegration,mongodbConnectionManager,mongodbDriverManager}.js`)
— an abandoned attempt to auto-detect MongoDB 3.0–8.0 and pick versioned driver packages
that were never even installed; WeKan uses the mongodb-7 driver via Meteor.
- **Fix snap build failing on the `caddy` part (Cloudsmith unreachable on Launchpad)**:
The snap installed Caddy from the Cloudsmith apt repo
(`curl … dl.cloudsmith.io … | gpg --dearmor`), which fails on the Launchpad remote
builders — their network is restricted to a fetch proxy that can't reach Cloudsmith, so
`gpg` got no key (`no valid OpenPGP data found`) and the `caddy` `override-build` failed
with code 2 on both arches, all attempts. Both `snapcraft.yaml` and `snapcraft-core24.yaml`
now download the **official prebuilt Caddy static binary from GitHub releases** (per-arch,
latest stable with a pinned fallback) instead. WeKan uses only built-in Caddy directives,
so vanilla Caddy is sufficient — no apt repo, no `gpg`, no `xcaddy`/custom-module build.
- **Fix Admin Panel / Version showing "MongoDB" when running on FerretDB**:
The database detection only recognised a `buildInfo.ferretdb` sub-document, but the
wekan/FerretDB v1 fork reports its identity as a **top-level `ferretdbVersion`** string
(e.g. `v1.24.2-60-gb5523566`) plus `ferretdbFeatures`, with its git commit in `gitVersion`.
So the Version page showed `Database type: MongoDB` and hid the FerretDB rows. Detection now
handles both shapes ([server/statistics.js](https://github.com/wekan/wekan/blob/main/server/statistics.js)),
so it shows `Database type: FerretDB`, the `FerretDB version` and `FerretDB commit` rows, and
the `SQLite` storage engine. (FerretDB v1's `version: 7.0.42` is the MongoDB version it emulates.)
- **Design doc: WeKan on Sandstorm (Meteor 3.5 / Node 24) with MongoDB 3 → FerretDB migration**:
Added [docs/Platforms/FOSS/Sandstorm/Meteor3/Migration.md](https://github.com/wekan/wekan/blob/main/docs/Platforms/FOSS/Sandstorm/Meteor3/Migration.md)
describing how to build a modern Sandstorm `.spk` (Node 24, replacing meteor-spk
0.6.0's Node 14) that runs on FerretDB v1 (embedded SQLite) instead of MongoDB 3.0,
migrating an existing grain's MongoDB 3.0 data on first launch — reusing the snap's
proven `migrate-mongo3-to-ferretdb` logic (mongoexport read → FerretDB insert;
CollectionFS/Meteor-Files GridFS attachments+avatars → filesystem). Includes the
grain sandbox (seccomp) compatibility analysis, the rewritten `start.js`, and a new
`isSandstorm`-only Admin Panel / Attachments / Sandstorm section (migration status,
raw-MongoDB disk usage, and a guarded delete-raw-MongoDB-files action). Implementation
of the in-app pieces follows.
- **Sandstorm: Admin Panel / Attachments / Sandstorm (migration status + free raw-MongoDB disk space)**:
Implemented the in-app pieces from the design above. When WeKan runs inside a
Sandstorm grain (`isSandstorm`), a new **Sandstorm** section appears in Admin
Panel / Attachments showing whether the one-time MongoDB 3 → FerretDB v1
migration succeeded, and the disk space the raw MongoDB 3 database files, the
FerretDB SQLite, and the attachments/avatars currently use inside the grain.
An admin can delete the now-redundant raw MongoDB files to free disk space —
guarded so it only runs after a confirmed-successful migration, behind a
confirmation. New admin-gated server methods `sandstormMigrationStatus` /
`sandstormDeleteRawMongo` ([server/methods/sandstormMigration.js](https://github.com/wekan/wekan/blob/main/server/methods/sandstormMigration.js));
the migration importer now writes a `migration-status.json` the panel reads.
- **Sandstorm: grain launcher + spk build tooling (Node 24 / FerretDB, no releases.wekan.team)**:
Added the grain launcher [sandstorm-src/start.js](https://github.com/wekan/wekan/blob/main/sandstorm-src/start.js):
on first launch it runs the migration chain for whatever an existing grain holds —
**niscu (MongoDB 2.x) → MongoDB 3.0** (the preserved legacy path for very old grains) then
**MongoDB 3.0 → FerretDB v1** — then runs WeKan (Node 24) on FerretDB. Migration support from
old versions is permanent (niscud + mongod 3.0 are kept). Added the deps-assembly script
[sandstorm-src/build-deps.sh](https://github.com/wekan/wekan/blob/main/sandstorm-src/build-deps.sh)
which builds a modern `meteor-spk.deps` on top of **upstream meteor-spk 0.6.0**
(`dl.sandstorm.io`) — swapping in Node 24, adding FerretDB + the Mongo 3.x CLIs + the
launcher/importer, keeping niscud — with extra binaries fetched from **GitHub releases**
(the retired `releases.wekan.team` / old `projects.7z` are no longer used). `sandstorm.yml`
now calls it, and `WRITABLE_PATH` in `sandstorm-pkgdef.capnp` is `/var/files`. Build/CI only —
not yet packed/tested end-to-end in a grain.
Thanks to xet7.
Thanks to above GitHub users for their contributions and translators for their translations.
# v9.84 2026-07-11 WeKan ® release
This release adds the following features and fixes:
+5 -3
View File
@@ -7,7 +7,7 @@ LABEL org.opencontainers.image.source="https://github.com/wekan/wekan"
# TARGETARCH and TARGETVARIANT are automatically provided by Docker Buildx
ARG TARGETARCH
ARG TARGETVARIANT
ARG VERSION=9.84
ARG VERSION=9.89
ARG DEBIAN_FRONTEND=noninteractive
ENV BUILD_DEPS="apt-utils gnupg wget bzip2 g++ curl libarchive-tools build-essential git ca-certificates python3 unzip"
@@ -242,8 +242,10 @@ mv /home/wekan/app/bundle /build
# The .zip bundle now ships a self-contained launcher + its own Node.js for the
# offline downloads; the Docker image installs its own Node and uses
# wekan-entrypoint.sh, so drop the redundant bundled node + launchers (keeps
# /build/ferretdb, which the entrypoint uses). Saves ~80 MB per arch.
# wekan-entrypoint.sh, so drop the redundant bundled node + launchers. Keeps
# /build/ferretdb (used by the entrypoint) and the per-arch MongoDB Database Tools
# (bsondump, mongodump, mongorestore, … from wekan/mongo-tools, embedded in the
# bundle) for backup/restore inside the container. Saves ~80 MB per arch.
rm -f /build/node /build/start-wekan.sh /build/start-wekan.bat
# Restore original tar
+20 -12
View File
@@ -106,7 +106,7 @@ By working directly with WeKan ® you get the benefit of active maintenance and
The main branch uses Meteor 3.5 with Node.js 24.x.
See [CHANGELOG.md](https://github.com/wekan/wekan/blob/main/CHANGELOG.md) for the latest runtime updates.
To contribute, [create a fork](https://github.com/wekan/wekan/blob/main/docs/DeveloperDocs/Build-and-Create-Pull-Request.md#2-create-fork-of-httpsgithubcomwekanwekan-at-github-web-page) and run `./rebuild-wekan.sh` (or `./rebuild-wekan.bat` on Windows) as detailed [here](https://github.com/wekan/wekan/blob/main/docs/DeveloperDocs/Build-and-Create-Pull-Request.md#3-select-option-1-to-install-dependencies-and-then-enter). Once you're ready, please test your code and [submit a pull request (PR)](https://github.com/wekan/wekan/blob/main/docs/DeveloperDocs/Build-and-Create-Pull-Request.md#7-test).
To contribute, [create a fork](https://github.com/wekan/wekan/blob/main/docs/DeveloperDocs/Build-and-Create-Pull-Request.md#2-create-fork-of-httpsgithubcomwekanwekan-at-github-web-page) and run `./rebuild-wekan.sh` (or `./rebuild-wekan.bat` on Windows) as detailed [here](https://github.com/wekan/wekan/blob/main/docs/DeveloperDocs/Build-and-Create-Pull-Request.md#3-install-dependencies-build-wekan-and-run-the-dev-server). Once you're ready, please test your code and [submit a pull request (PR)](https://github.com/wekan/wekan/blob/main/docs/DeveloperDocs/Build-and-Create-Pull-Request.md#7-test).
Please refer to the [developer documentation](https://github.com/wekan/wekan/blob/main/docs/DeveloperDocs/Developer-Documentation.md) for more information.
@@ -138,11 +138,17 @@ curl https://install.meteor.com/ | sh
### Building WeKan
The `rebuild-wekan.sh` script guides you through a three-stage process:
The `rebuild-wekan.sh` script shows a two-level menu. The top level groups options into categories:
1. **Install dependencies (Option 1)** - Downloads all required Meteor packages and npm modules
2. **Build WeKan (Option 2)** - Compiles the application
3. **Run WeKan (Option 3)** - Starts the development server at http://localhost:4000
```
1) Setup 2) Dev server 3) Tests 4) Docker 5) Tools 6) Quit
```
You pick a category number, then the item number inside it (each submenu also has a `Back` entry). Building from source is a three-stage process:
1. **Setup -> Install dependencies** - Downloads all required Meteor packages and npm modules
2. **Setup -> Build WeKan** - Compiles the application
3. **Dev server -> localhost:3000** - Starts the development server at http://localhost:3000
```bash
# Clone your fork
@@ -152,25 +158,27 @@ cd wekan
# Make the script executable
chmod +x rebuild-wekan.sh
# Step 1: Install dependencies
# Step 1: Install dependencies (Setup -> Install dependencies)
./rebuild-wekan.sh
# Press 1 and Enter
# Press 1 (Setup) and Enter, then 1 (Install dependencies) and Enter
# Step 2: Build WeKan (after dependencies complete)
# Step 2: Build WeKan (Setup -> Build WeKan, after dependencies complete)
./rebuild-wekan.sh
# Press 2 and Enter
# Press 1 (Setup) and Enter, then 2 (Build WeKan) and Enter
# Step 3: Run WeKan in development mode
# Step 3: Run WeKan in development mode (Dev server -> localhost:3000)
./rebuild-wekan.sh
# Press 3 and Enter
# Press 2 (Dev server) and Enter, then 1 (localhost:3000) and Enter
```
If a dev server is already running on that port, the **Dev server** options stop it automatically and start a fresh server on the same port.
### WSL Users
WSL users can use Snap Candidate. See [install docs](https://wekan.fi/install/).
The development server will start at http://localhost:4000. Any changes you make to the source code will automatically trigger a rebuild and refresh your browser.
The development server will start at http://localhost:3000. Any changes you make to the source code will automatically trigger a rebuild and refresh your browser.
## Screenshot
+1 -1
View File
@@ -1,5 +1,5 @@
appId: wekan-public/apps/77b94f60-dec9-0136-304e-16ff53095928
appVersion: "v9.84.0"
appVersion: "v9.89.0"
files:
userUploads:
- README.md
+9 -2
View File
@@ -570,11 +570,18 @@ Template.boardBody.onRendered(function () {
$swimlanesDom.sortable('option', 'handle', '.swimlane-header');
}
// Disable drag-dropping if the current user is not a board member
// #6446: enable swimlane drag-drop — which also carries moving cards BETWEEN
// swimlanes — for any board member with write access, not only board admins.
// The old !isBoardAdmin() check disabled this sortable for every non-admin, so
// a normal member could still move a card WITHIN a swimlane but not BETWEEN
// swimlanes (a card crossing swimlanes is received across this sortable), and
// could not reorder swimlanes. canModifyCard() is the client write-access
// predicate (board member, not comment-only / worker / read-only), matching
// the server's allowIsBoardMemberWithWriteAccess.
$swimlanesDom.sortable(
'option',
'disabled',
!ReactiveCache.getCurrentUser()?.isBoardAdmin(),
!Utils.canModifyCard(),
);
}
});
+13 -6
View File
@@ -432,11 +432,16 @@ export async function handleFileUpload(card, files) {
fileName: fileName,
meta: Utils.getCommonAttachmentMetaFrom(card),
chunkSize: 'dynamic',
// Use HTTP transport instead of DDP so file chunks go over a dedicated
// fetch POST rather than flooding the WebSocket/DDP channel. DDP
// upload causes repeated DDP reconnects in Safari, showing the
// "Loading, please wait" offline banner and stalling progress at ~95%.
transport: 'http',
// Use HTTP transport (a dedicated fetch POST per chunk) rather than DDP,
// which floods the WebSocket channel and causes repeated reconnects in
// Safari (the "Loading, please wait" offline banner, stalling at ~95%).
// EXCEPT on Sandstorm: the grain's sandstorm-http-bridge strips Meteor-Files'
// custom upload headers — x-start/x-mtok/x-chunkid/x-fileid/x-eof are not on
// Sandstorm's request-header whitelist — so the server never sees x-start,
// treats every request as a chunk continuation, and fails with "Can't
// continue upload, session expired" [408]. DDP uploads go over method calls
// (no custom HTTP headers), so they work through the bridge.
transport: Meteor.settings?.public?.sandstorm ? 'ddp' : 'http',
};
config.meta.fileId = fileId;
@@ -528,7 +533,9 @@ Template.previewClipboardImagePopup.events({
meta: Utils.getCommonAttachmentMetaFrom(card),
fileName: file.name || file.type.replace('image/', 'clipboard.'),
chunkSize: 'dynamic',
transport: 'http',
// DDP on Sandstorm (its bridge strips Meteor-Files' x-* upload headers),
// HTTP elsewhere — see the note in the other upload handler above.
transport: Meteor.settings?.public?.sandstorm ? 'ddp' : 'http',
};
config.meta.fileId = fileId;
const uploader = await Attachments.insertAsync(
@@ -61,6 +61,12 @@ template(name="attachments")
span.emoji-icon
i.fa.fa-archive
| {{_ 'backup'}}
if isSandstorm
li(class="{{#if isSandstormActive}}active{{/if}}")
a.js-attachments-menu(data-id="sandstorm")
span.emoji-icon
i.fa.fa-hdd-o
| Sandstorm
.main-body
if loading.get
@@ -580,6 +586,49 @@ template(name="attachments")
.form-group
button.js-restore-backup.btn.btn-warning(type="button" disabled=backupRunning) {{_ 'backup-restore'}}
else if isSandstormActive
ul#attachment-sandstorm-setting.setting-detail
li
h3 Sandstorm
.description {{_ 'sandstorm-migration-description'}}
if sandstormStatus
.form-group
strong {{_ 'sandstorm-migration-status'}}
if sandstormStatus.migrationSuccess
span.text-success {{_ 'sandstorm-migration-success'}}
else if sandstormStatus.migrationDone
span.text-danger {{_ 'sandstorm-migration-failed'}}
else
span.text-muted {{_ 'sandstorm-migration-pending'}}
if sandstormStatus.status
p.form-text.text-muted {{_ 'database-migration-phase'}}: {{sandstormStatus.status.phase}}
table.gridfs-stats-table
tr
th {{_ 'sandstorm-storage-item'}}
th {{_ 'sandstorm-disk-usage'}}
tr
td {{_ 'sandstorm-raw-mongodb'}}
td {{rawMongoSize}}
tr
td FerretDB (SQLite)
td {{ferretSize}}
tr
td {{_ 'attachments'}}
td {{attachmentsSize}}
tr
td {{_ 'avatars'}}
td {{avatarsSize}}
if sandstormStatus.rawMongoExists
.form-group
.description {{_ 'sandstorm-delete-raw-mongodb-description'}}
button.js-sandstorm-delete-raw-mongodb.btn.btn-warning(type="button" disabled=sandstormDeleteDisabled) {{_ 'sandstorm-delete-raw-mongodb'}}
if sandstormDeleteResult
p.form-text.text-success {{_ 'sandstorm-raw-mongodb-deleted'}} ({{sandstormDeleteFreed}})
if sandstormDeleteError
p.form-text.text-danger {{sandstormDeleteError}}
else
p.form-text.text-muted {{_ 'loading'}}
template(name="moveAttachments")
.move-storage-form
.move-storage-selects
+77
View File
@@ -276,6 +276,20 @@ Template.attachments.onCreated(function () {
this.backupPoll = null;
Meteor.call('getBackupSchedule', (err, s) => { if (!err && s) this.backupSchedule.set(s); });
// Sandstorm: MongoDB 3 -> FerretDB migration status + raw-MongoDB disk usage.
this.sandstormStatus = new ReactiveVar(null);
this.sandstormDeleteResult = new ReactiveVar(null);
this.sandstormDeleteError = new ReactiveVar('');
// Fetch (once) when the Sandstorm tab is opened. Migration runs in start.js
// before the app boots, so the status is static by the time the UI is shown.
this.autorun(() => {
if (this.activeSection.get() === 'sandstorm') {
Meteor.call('sandstormMigrationStatus', (err, res) => {
if (!err && res) this.sandstormStatus.set(res);
});
}
});
this.autorun(() => {
const ready = this.storageSettingsSubscription.ready();
if (ready) {
@@ -371,6 +385,51 @@ Template.attachments.helpers({
isBackupActive() {
return Template.instance().activeSection.get() === 'backup';
},
isSandstorm() {
return !!(
Meteor.settings &&
Meteor.settings.public &&
Meteor.settings.public.sandstorm
);
},
isSandstormActive() {
return Template.instance().activeSection.get() === 'sandstorm';
},
sandstormStatus() {
return Template.instance().sandstormStatus.get();
},
rawMongoSize() {
const s = Template.instance().sandstormStatus.get();
return s ? filesize(s.rawMongoBytes || 0) : '';
},
ferretSize() {
const s = Template.instance().sandstormStatus.get();
return s ? filesize(s.ferretBytes || 0) : '';
},
attachmentsSize() {
const s = Template.instance().sandstormStatus.get();
return s ? filesize(s.attachmentsBytes || 0) : '';
},
avatarsSize() {
const s = Template.instance().sandstormStatus.get();
return s ? filesize(s.avatarsBytes || 0) : '';
},
sandstormDeleteDisabled() {
const s = Template.instance().sandstormStatus.get();
// Only allow deleting the raw MongoDB files after a confirmed-successful
// migration, and only while they still exist.
return !(s && s.migrationSuccess && s.rawMongoExists);
},
sandstormDeleteResult() {
return Template.instance().sandstormDeleteResult.get();
},
sandstormDeleteFreed() {
const r = Template.instance().sandstormDeleteResult.get();
return r ? filesize(r.freedBytes || 0) : '';
},
sandstormDeleteError() {
return Template.instance().sandstormDeleteError.get();
},
backupStatus() {
return Template.instance().backupStatus.get();
},
@@ -655,6 +714,24 @@ Template.attachments.events({
tpl.activeSection.set(targetID);
},
'click .js-sandstorm-delete-raw-mongodb'(event, tpl) {
event.preventDefault();
if (!window.confirm(TAPi18n.__('sandstorm-delete-raw-mongodb-confirm'))) {
return;
}
tpl.sandstormDeleteError.set('');
Meteor.call('sandstormDeleteRawMongo', (error, result) => {
if (error) {
tpl.sandstormDeleteError.set(error.reason || error.message);
return;
}
tpl.sandstormDeleteResult.set(result);
// Refresh disk usage / status after deletion.
Meteor.call('sandstormMigrationStatus', (err, res) => {
if (!err && res) tpl.sandstormStatus.set(res);
});
});
},
'click .js-migrate-to-ferretdb'(event, tpl) {
event.preventDefault();
startDbMigration(tpl, 'toFerretDB');
+1 -1
View File
@@ -85,7 +85,7 @@ template(name="membersWidget")
+userAvatar(userId=currentBoard.userId showStatus=true)
.clearfix
else
each currentBoard.activeMembers
each currentBoard.membersForSidebar
+userAvatar(userId=this.userId showStatus=true)
if isSandstorm
if currentUser.isBoardMember
+39
View File
@@ -118,3 +118,42 @@
height: clamp(40px, 5vw, 60px);
margin-inline-end: 10px;
}
/* Account-status distinction on the avatar itself (see userAvatar.js
memberAccountClass / isImportedMember / isInactiveMember):
- imported-member: an un-reconciled board-import placeholder that is not yet mapped
to a real account — dashed ring + amber "?" corner badge.
- inactive-member: deactivated on this board (e.g. a person not in LDAP after
reconciliation) — greyscale + dimmed, grey corner badge.
A placeholder is usually both; a real, active account gets neither. */
.member.imported-member .avatar {
border: 2px dashed #7f8c9a;
box-sizing: border-box;
opacity: 0.9;
}
.member.inactive-member .avatar {
filter: grayscale(1);
opacity: 0.55;
}
.member .member-account-badge {
position: absolute;
bottom: -2px;
right: -2px;
min-width: 14px;
height: 14px;
line-height: 13px;
padding: 0 1px;
border-radius: 7px;
font-size: 10px;
font-weight: bold;
text-align: center;
color: #fff;
box-shadow: 0 0 0 1.5px #fff;
pointer-events: none;
}
.member .member-account-badge.imported {
background: #f39c12;
}
.member .member-account-badge.inactive {
background: #95a5a6;
}
+6 -1
View File
@@ -1,5 +1,5 @@
template(name="userAvatar")
a.member(class="js-{{#if assignee}}assignee{{else}}member{{/if}}" title="{{#if userData}}{{userData.profile.fullname}} ({{userData.username}}) {{_ memberType}}{{/if}}")
a.member(class="js-{{#if assignee}}assignee{{else}}member{{/if}} {{memberAccountClass}}" title="{{#if userData}}{{userData.profile.fullname}} ({{userData.username}}) {{_ memberType}}{{#if isImportedMember}} — {{_ 'imported-member-no-account'}}{{else}}{{#if isInactiveMember}} — {{_ 'inactive-member'}}{{/if}}{{/if}}{{/if}}")
if userData
if userData.profile.avatarUrl
img.avatar.avatar-image(src="{{avatarUrl}}" alt="")
@@ -8,6 +8,11 @@ template(name="userAvatar")
else
+userAvatarInitials(userId=this.userId)
if isImportedMember
span.member-account-badge.imported(title="{{_ 'imported-member-no-account'}}") ?
else if isInactiveMember
span.member-account-badge.inactive(title="{{_ 'inactive-member'}}")
if showStatus
span.member-presence-status(class=presenceStatusClassName)
span.member-type(class=memberType)
+44
View File
@@ -11,11 +11,55 @@ Template.userAvatar.helpers({
fields: {
profile: 1,
username: 1,
authenticationMethod: 1,
isActive: 1,
},
});
return user;
},
// Distinguish, on the avatar itself, whether a real account backs this member:
// - imported-member: an inert placeholder created by a board import that has not been
// reconciled/mapped to a real account yet (dashed ring + "?" badge).
// - inactive-member: deactivated on this board (e.g. a person not in LDAP after
// reconciliation) (greyscale + dim).
// A placeholder is typically both. A real, active account gets neither.
memberAccountClass() {
const user = ReactiveCache.getUser(this.userId, {
fields: { authenticationMethod: 1, isActive: 1 },
});
if (!user) return '';
const classes = [];
if (user.authenticationMethod === 'imported') classes.push('imported-member');
let inactive = user.isActive === false;
if (!inactive) {
const board = Utils.getCurrentBoard && Utils.getCurrentBoard();
const m = board && Array.isArray(board.members)
? board.members.find(x => x.userId === this.userId)
: null;
if (m && m.isActive === false) inactive = true;
}
if (inactive) classes.push('inactive-member');
return classes.join(' ');
},
isImportedMember() {
const user = ReactiveCache.getUser(this.userId, { fields: { authenticationMethod: 1 } });
return !!(user && user.authenticationMethod === 'imported');
},
isInactiveMember() {
const user = ReactiveCache.getUser(this.userId, { fields: { authenticationMethod: 1, isActive: 1 } });
if (!user) return false;
if (user.authenticationMethod === 'imported') return false; // shown via the imported badge
if (user.isActive === false) return true;
const board = Utils.getCurrentBoard && Utils.getCurrentBoard();
const m = board && Array.isArray(board.members)
? board.members.find(x => x.userId === this.userId)
: null;
return !!(m && m.isActive === false);
},
avatarUrl() {
const user = ReactiveCache.getUser(this.userId, { fields: { profile: 1 } });
const base = (user && user.profile && user.profile.avatarUrl) || '';
+19 -1
View File
@@ -17,7 +17,25 @@ const fs = require('fs');
const path = require('path');
const { expect } = require('chai');
const repoRoot = path.resolve(__dirname, '..', '..', '..');
// Find the repo root by walking up from process.cwd()/PWD, NOT from the bare `__dirname`
// global: under `meteor test` referencing `__dirname` makes Meteor inject a
// `const __dirname` that collides with the one its CommonJS module wrapper already
// provides, crashing the whole server bundle at boot with "Identifier '__dirname' has
// already been declared" (same fix as server/lib/tests/dependencies.openapi.tests.js).
function findRepoRoot(marker) {
const seeds = [process.cwd(), process.env.PWD, process.env.OLDPWD].filter(Boolean);
for (const seed of seeds) {
let dir = seed;
for (let i = 0; i < 12; i += 1) {
try { fs.accessSync(path.join(dir, marker)); return dir; } catch (e) { /* walk up */ }
const parent = path.dirname(dir);
if (parent === dir) break;
dir = parent;
}
}
return process.cwd();
}
const repoRoot = findRepoRoot(path.join('client', 'components', 'rules', 'triggers', 'boardTriggers.jade'));
const jadePath = path.join(
repoRoot,
'client',
+46 -22
View File
@@ -10,6 +10,27 @@ import { Utils } from '/client/lib/utils';
let previousPath;
// On Sandstorm the grain is authenticated by the platform, not by a local WeKan
// account. That login is delivered asynchronously over the DDP connection (via
// connection.setUserId(), which — unlike a normal password login — does NOT set
// Meteor.loggingIn()), so for the first moments after a grain opens Meteor.userId()
// is still null even though the user is, and always will be, authenticated. There
// is no local sign-in page in a grain. useraccounts' ensureSignedIn would bounce the
// grain straight to the (nonexistent) atSignIn route on that brief null window,
// stranding the user on a "Must be logged in" page instead of opening All Boards.
const isSandstorm = Meteor.settings?.public?.sandstorm;
// Drop-in replacement for AccountsTemplates.ensureSignedIn used as a route
// triggersEnter: a no-op on Sandstorm (the platform guarantees authentication and
// the route repopulates reactively once Meteor.userId() lands), and the normal
// useraccounts guard everywhere else.
function ensureSignedInUnlessSandstorm(context, redirect, stop) {
if (isSandstorm) {
return undefined;
}
return AccountsTemplates.ensureSignedIn(context, redirect, stop);
}
FlowRouter.triggers.exit([
({ path }) => {
previousPath = path;
@@ -21,8 +42,11 @@ FlowRouter.triggers.exit([
// redirected to; the chosen view is passed to boardList through the
// `boardListMenu` Session value.
function renderBoardList(ctx, menu) {
// Redirect to sign-in immediately if user is not logged in
if (!Meteor.userId()) {
// Redirect to sign-in immediately if user is not logged in — except on Sandstorm,
// where the platform authenticates asynchronously (see isSandstorm note above) and
// there is no sign-in page. There we render the All Boards list, which reactively
// fills in once the grain login lands, instead of bouncing to atSignIn.
if (!Meteor.userId() && !isSandstorm) {
FlowRouter.go('atSignIn');
return;
}
@@ -48,7 +72,7 @@ function renderBoardList(ctx, menu) {
FlowRouter.route('/', {
name: 'home',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
renderBoardList(this, 'starred');
},
@@ -56,7 +80,7 @@ FlowRouter.route('/', {
FlowRouter.route('/templates', {
name: 'allboards-templates',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
renderBoardList(this, 'templates');
},
@@ -64,7 +88,7 @@ FlowRouter.route('/templates', {
FlowRouter.route('/remaining', {
name: 'allboards-remaining',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
renderBoardList(this, 'remaining');
},
@@ -72,7 +96,7 @@ FlowRouter.route('/remaining', {
FlowRouter.route('/public', {
name: 'public',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -96,7 +120,7 @@ FlowRouter.route('/public', {
FlowRouter.route('/accessibility', {
name: 'accessibility',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -120,7 +144,7 @@ FlowRouter.route('/accessibility', {
FlowRouter.route('/support', {
name: 'support',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -144,7 +168,7 @@ FlowRouter.route('/support', {
FlowRouter.route('/b/:id/:slug/rules', {
name: 'board-rules',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action(params) {
const currentBoard = params.id;
Session.set('currentBoard', currentBoard);
@@ -272,7 +296,7 @@ FlowRouter.route('/shortcuts', {
FlowRouter.route('/b/templates', {
name: 'template-container',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -296,7 +320,7 @@ FlowRouter.route('/b/templates', {
FlowRouter.route('/my-cards', {
name: 'my-cards',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Filter.reset();
Session.set('sortBy', '');
@@ -316,7 +340,7 @@ FlowRouter.route('/my-cards', {
FlowRouter.route('/due-cards', {
name: 'due-cards',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Filter.reset();
Session.set('sortBy', '');
@@ -336,7 +360,7 @@ FlowRouter.route('/due-cards', {
FlowRouter.route('/global-search', {
name: 'global-search',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Filter.reset();
Session.set('sortBy', '');
@@ -371,7 +395,7 @@ FlowRouter.route('/global-search', {
// Mobile Bookmarks page
FlowRouter.route('/bookmarks', {
name: 'bookmarks',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action() {
Filter.reset();
Session.set('sortBy', '');
@@ -409,7 +433,7 @@ FlowRouter.route('/broken-cards', {
FlowRouter.route('/import/:source', {
name: 'import',
triggersEnter: [AccountsTemplates.ensureSignedIn],
triggersEnter: [ensureSignedInUnlessSandstorm],
action(params) {
if (Session.get('currentBoard')) {
Session.set('fromBoard', Session.get('currentBoard'));
@@ -434,7 +458,7 @@ FlowRouter.route('/import/:source', {
FlowRouter.route('/setting', {
name: 'setting',
triggersEnter: [
AccountsTemplates.ensureSignedIn,
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -459,7 +483,7 @@ FlowRouter.route('/setting', {
FlowRouter.route('/information', {
name: 'information',
triggersEnter: [
AccountsTemplates.ensureSignedIn,
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -483,7 +507,7 @@ FlowRouter.route('/information', {
FlowRouter.route('/people', {
name: 'people',
triggersEnter: [
AccountsTemplates.ensureSignedIn,
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -507,7 +531,7 @@ FlowRouter.route('/people', {
FlowRouter.route('/admin-reports', {
name: 'admin-reports',
triggersEnter: [
AccountsTemplates.ensureSignedIn,
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -531,7 +555,7 @@ FlowRouter.route('/admin-reports', {
FlowRouter.route('/attachments', {
name: 'attachments',
triggersEnter: [
AccountsTemplates.ensureSignedIn,
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -555,7 +579,7 @@ FlowRouter.route('/attachments', {
FlowRouter.route('/translation', {
name: 'translation',
triggersEnter: [
AccountsTemplates.ensureSignedIn,
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
Session.set('currentList', null);
@@ -579,7 +603,7 @@ FlowRouter.route('/translation', {
FlowRouter.route('/admin-features', {
name: 'admin-features',
triggersEnter: [
AccountsTemplates.ensureSignedIn,
ensureSignedInUnlessSandstorm,
() => {
Session.set('currentBoard', null);
Session.set('currentList', null);
+5 -6
View File
@@ -1,10 +1,10 @@
# WeKan with FerretDB 2 + PostgreSQL (DocumentDB extension)
#
# Use this compose file instead of docker-compose.yml on platforms where
# MongoDB Community Edition is not available, or when you prefer PostgreSQL
# as the backing store. For a lighter, single-container, no-PostgreSQL option,
# see docker-compose-ferretdb-v1-sqlite.yml (FerretDB v1 with the embedded
# SQLite backend, using the wekan/FerretDB release binaries).
# Use this compose file instead of the default docker-compose.yml when you
# prefer PostgreSQL as the backing store. For the lighter, single-container,
# no-PostgreSQL option, see the default docker-compose.yml (FerretDB v1 with the
# embedded SQLite backend, using the wekan/FerretDB release binaries). For the
# classic MongoDB 7 option, see docker-compose-mongodb-v7.yml.
#
# Supported on all platforms where Node.js 22 runs:
# linux/amd64, linux/arm64, linux/arm/v7, linux/ppc64le, linux/s390x
@@ -17,7 +17,6 @@
# To stop:
# docker compose -f docker-compose-ferretdb-v2-postgresql.yml stop
version: '3.8'
services:
# PostgreSQL 17 with the DocumentDB extension (FerretDB 2 backing store).
@@ -1,75 +1,287 @@
# WeKan with FerretDB v1 + embedded SQLite (no PostgreSQL, no MongoDB)
# WeKan with MongoDB 7 (docker-compose-mongodb-v7.yml)
#
# Use this compose file instead of docker-compose.yml for a light, self-contained
# database: FerretDB v1 (the wekan/FerretDB fork, https://github.com/wekan/FerretDB)
# with its embedded pure-Go SQLite backend, which speaks the MongoDB wire protocol.
# There is no separate PostgreSQL or MongoDB server — FerretDB stores everything in
# SQLite files on a volume, and WeKan stores attachments/avatars on the filesystem.
# For the PostgreSQL-backed FerretDB 2 option instead, see
# docker-compose-ferretdb-v2-postgresql.yml.
#
# The FerretDB binary is downloaded (once, then cached on the volume) from the
# newest wekan/FerretDB release: https://github.com/wekan/FerretDB/releases
# The ferretdb.zip there contains ferretdb/<arch>/ferretdb-<arch> for every
# platform; the container picks the binary matching its architecture (amd64,
# arm64, ppc64le, s390x, riscv64, ...).
#
# Setup:
# docker compose -f docker-compose-ferretdb-v1-sqlite.yml up -d
#
# To stop:
# docker compose -f docker-compose-ferretdb-v1-sqlite.yml stop
# This is the classic MongoDB 7 setup. It is NOT the default anymore: the default
# docker-compose.yml now uses FerretDB v1 with SQLite (see docker-compose.yml).
# To use this MongoDB 7 file, either run it explicitly with
# docker compose -f docker-compose-mongodb-v7.yml up -d
# or rename/copy it to docker-compose.yml. The examples below use the bare
# "docker compose ..." form, which assumes you renamed it to docker-compose.yml.
#---------------------------------------------------------------------------------------------------------
# Note: Do not add single quotes '' to variables. Having spaces still works without quotes where required.
#---------------------------------------------------------------------------------------------------------
# ==== CREATING USERS AND LOGGING IN TO WEKAN ====
# https://github.com/wekan/wekan/blob/main/docs/Login/Adding-users.md
#---------------------------------------------------------------------------------------------------------
# ==== FORGOT PASSWORD ====
# https://github.com/wekan/wekan/blob/main/docs/Login/Forgot-Password.md
#---------------------------------------------------------------------------------------------------------
# ==== Upgrading Wekan to new version =====
# NOTE: MongoDB has changed from 3.x to 4.x, in that case you need backup/restore with --noIndexRestore
# see https://github.com/wekan/wekan/tree/main/docs/Backup
# 1) Stop Wekan:
# docker compose stop
# 2) Remove old Wekan app (wekan-app only, not that wekan-db container that has all your data)
# docker rm wekan-app
# 3) Get newest docker-compose-mongodb-v7.yml from https://github.com/wekan/wekan to have correct image,
# for example: "image: quay.io/wekan/wekan" or version tag "image: quay.io/wekan/wekan:v4.52"
# 4) Start Wekan:
# docker compose up -d
#----------------------------------------------------------------------------------
# ==== OPTIONAL: DEDICATED DOCKER USER ====
# 1) Optionally create a dedicated user for Wekan, for example:
# sudo useradd -d /home/wekan -m -s /bin/bash wekan
# 2) Add this user to the docker group, then logout+login or reboot:
# sudo usermod -aG docker wekan
# 3) Then login as user wekan.
# 4) Create this file /home/wekan/docker-compose.yml with your modifications.
#----------------------------------------------------------------------------------
# ==== RUN DOCKER AS SERVICE ====
# 1a) Running Docker as service, on Systemd like Debian 9, Ubuntu 16.04, CentOS 7:
# sudo systemctl enable docker
# sudo systemctl start docker
# 1b) Running Docker as service, on init.d like Debian 8, Ubuntu 14.04, CentOS 6:
# sudo update-rc.d docker defaults
# sudo service docker start
# ----------------------------------------------------------------------------------
# ==== USAGE OF THIS docker-compose-mongodb-v7.yml ====
# 1) For seeing does Wekan work, try this and check with your web browser:
# docker compose up
# 2) Stop Wekan and start Wekan in background:
# docker compose stop
# docker compose up -d
# 3) See running Docker containers:
# docker ps
# 4) Stop Docker containers:
# docker compose stop
# ----------------------------------------------------------------------------------
# ===== INSIDE DOCKER CONTAINERS, AND BACKUP/RESTORE ====
# https://github.com/wekan/wekan/tree/main/docs/Backup
# If really necessary, repair MongoDB: https://github.com/wekan/wekan-mongodb/issues/6#issuecomment-424004116
# 1) Going inside containers:
# a) Wekan app, does not contain data
# docker exec -it wekan-app bash
# b) MongoDB, contains all data
# docker exec -it wekan-db bash
# 2) Copying database to outside of container:
# docker exec -it wekan-db bash
# cd /data
# mongodump
# exit
# docker cp wekan-db:/data/dump .
# 3) Restoring database
# # 1) Stop wekan
# docker stop wekan-app
# # 2) Go inside database container
# docker exec -it wekan-db bash
# # 3) and data directory
# cd /data
# # 4) Remove previous dump
# rm -rf dump
# # 5) Exit db container
# exit
# # 6) Copy dump to inside docker container
# docker cp dump wekan-db:/data/
# # 7) Go inside database container
# docker exec -it wekan-db bash
# # 8) and data directory
# cd /data
# # 9) Restore
# mongorestore --drop
# # 10) Exit db container
# exit
# # 11) Start wekan
# docker start wekan-app
#-------------------------------------------------------------------------
version: '3.8'
services:
# FerretDB v1 with the embedded SQLite backend (MongoDB-compatible on :27017).
# A tiny Debian container fetches the wekan/FerretDB v1 release binary for its
# architecture (cached on the volume so restarts do not re-download) and runs it.
# SQLite data lives in /data/sqlite on the ferretdb-data volume.
ferretdb:
image: debian:bookworm-slim
container_name: wekan-ferretdb
#-------------------------------------------------------------------------------------
# ==== DATABASE: FerretDB 2 + PostgreSQL 16 ====
# FerretDB is a MongoDB-compatible proxy that stores data in PostgreSQL.
# It supports the full MongoDB wire protocol used by Meteor/WeKan,
# including OpLog via replication-set emulation (--replication-set-name=rs0).
#
# Upgrade path from MongoDB:
# The wekan-migrate service below runs ONCE before wekan starts.
# It copies all data from an existing MongoDB instance (if reachable at
# SOURCE_MONGO_URL) to FerretDB, upgrades the schema to v8.43, and
# moves GridFS / CollectionFS binary files to the filesystem.
# Progress is visible in a browser while migration runs.
#
# If you are upgrading from a MongoDB-based install:
# 1. Keep your old MongoDB container running (or start it separately).
# 2. Set SOURCE_MONGO_URL in the wekan-migrate environment below.
# 3. Run: docker compose up -d
# 4. Watch migration at http://localhost:8080/ until "completed".
# 5. Shut down old MongoDB once satisfied.
#
# If this is a fresh install, wekan-migrate exits instantly (nothing to migrate).
#-------------------------------------------------------------------------------------
#
#wekan-postgres:
# image: postgres:16-alpine
# container_name: wekan-postgres
# restart: always
# networks:
# - wekan-tier
# expose:
# - 5432
# environment:
# - POSTGRES_DB=wekan
# - POSTGRES_USER=wekan
# - POSTGRES_PASSWORD=wekan
# # Tune for a kanban workload (low connection count, moderate write rate)
# - POSTGRES_INITDB_ARGS=--encoding=UTF8 --locale=C
# volumes:
# - /etc/localtime:/etc/localtime:ro
# - wekan-postgres:/var/lib/postgresql/data
# healthcheck:
# test: ["CMD-SHELL", "pg_isready -U wekan -d wekan"]
# interval: 5s
# timeout: 5s
# retries: 10
#
#wekan-ferretdb:
# image: ghcr.io/ferretdb/ferretdb:2
# container_name: wekan-ferretdb
# restart: always
# networks:
# - wekan-tier
# expose:
# - 27017
# environment:
# # FerretDB stores everything in PostgreSQL
# - FERRETDB_POSTGRESQL_URL=postgresql://wekan:wekan@wekan-postgres:5432/wekan
# # Emulate MongoDB replica-set for Meteor OpLog (real-time updates)
# - FERRETDB_REPLICATION_SET_NAME=rs0
# # Suppress verbose debug output
# - FERRETDB_LOG_LEVEL=warn
# depends_on:
# wekan-postgres:
# condition: service_healthy
# healthcheck:
# test: ["CMD", "ferretdb", "--version"]
# interval: 5s
# timeout: 5s
# retries: 10
#
#-------------------------------------------------------------------------------------
# ==== MIGRATION SERVICE ====
# Runs once, before WeKan starts. Exits 0 on success, 1 on fatal error.
# WeKan only starts after this service exits successfully
# (depends_on condition: service_completed_successfully).
#
# On a FRESH install (no SOURCE_MONGO_URL or source unreachable) it exits
# immediately — no penalty for new deployments.
#
# SOURCE_MONGO_URL: point to your old MongoDB container/host.
# e.g. mongodb://wekandb:27017/wekan
# mongodb://192.168.1.10:27017/wekan
# Leave it unset or empty to skip migration.
#-------------------------------------------------------------------------------------
#wekan-migrate:
# image: node:24.17.0-slim
# container_name: wekan-migrate
# restart: "no"
# networks:
# - wekan-tier
# working_dir: /migrate
# # Install the mongodb driver then run the migration script.
# # npm ci is used if package-lock.json exists; npm install otherwise.
# command: >
# sh -c "
# cd /migrate &&
# npm install --omit=dev --prefer-offline 2>/dev/null || npm install --omit=dev &&
# node migrate-mongodb-to-ferretdb.mjs
# "
# environment:
# # ---- Source (old MongoDB) ----
# # Set to your old MongoDB URL to trigger data migration.
# # Leave empty for a fresh install (migration is skipped automatically).
# - SOURCE_MONGO_URL=
# #- SOURCE_MONGO_URL=mongodb://wekandb:27017/wekan
#
# # ---- Target (FerretDB) ----
# - TARGET_MONGO_URL=mongodb://wekan-ferretdb:27017/wekan
#
# # ---- File storage ----
# # Must match the WRITABLE_PATH used by the wekan service.
# - WRITABLE_PATH=/data
#
# # ---- Progress dashboard ----
# # Browse to http://localhost:8080/ while migration runs.
# - MIGRATION_PORT=8080
#
# # ---- Tuning (optional) ----
# #- BATCH_SIZE=200
# #- DRY_RUN=true # Log only, no writes — useful for testing
# #- FORCE_MIGRATE=true # Re-run even if already marked complete
# ports:
# - 8080:8080
# depends_on:
# wekan-ferretdb:
# condition: service_healthy
# volumes:
# - /etc/localtime:/etc/localtime:ro
# - wekan-files:/data:rw
# - ./releases:/migrate:ro
#-------------------------------------------------------------------------------------
# ==== LEGACY MONGODB (commented out) ====
# Uncomment to keep old MongoDB running alongside FerretDB during migration.
# After migration is verified, remove this block entirely.
#-------------------------------------------------------------------------------------
wekandb:
image: mongo:7
container_name: wekan-db
restart: always
environment:
DO_NOT_TRACK: "1"
FERRETDB_TELEMETRY: disable
# Pin a specific release instead of the newest by setting e.g.
# FERRETDB_RELEASE=download/v1.24.2
FERRETDB_RELEASE: ${FERRETDB_RELEASE:-latest/download}
command:
- sh
- -c
- |
set -eu
BIN=/data/bin/ferretdb
if [ ! -x "$$BIN" ]; then
echo "Fetching FerretDB v1 from the wekan/FerretDB release ..."
apt-get update -qq
apt-get install -y -qq --no-install-recommends curl unzip ca-certificates >/dev/null
arch="$$(dpkg --print-architecture)"
case "$$arch" in ppc64el) arch=ppc64le ;; esac
mkdir -p /data/bin
curl -fSL --retry 5 -o /tmp/ferretdb.zip \
"https://github.com/wekan/FerretDB/releases/$${FERRETDB_RELEASE}/ferretdb.zip"
unzip -o -j /tmp/ferretdb.zip "ferretdb/$${arch}/ferretdb-$${arch}" -d /data/bin
mv "/data/bin/ferretdb-$${arch}" "$$BIN"
chmod +x "$$BIN"
rm -f /tmp/ferretdb.zip
fi
mkdir -p /data/files/db
exec "$$BIN" \
--handler=sqlite \
--sqlite-url=file:/data/files/db/ \
--listen-addr=0.0.0.0:27017 \
--telemetry=disable
volumes:
- ferretdb-data:/data
#command: mongod --logpath /dev/null --storageEngine wiredTiger --wiredTigerCacheSizeGB 32 --timeZoneInfo /usr/share/zoneinfo --setParameter logicalSessionRefreshMillis=900000 --setParameter localLogicalSessionTimeoutMinutes=45 --oplogSize 20480 --replSet rs0 --quiet
#command: mongod --storageEngine wiredTiger --wiredTigerCacheSizeGB 32 --timeZoneInfo /usr/share/zoneinfo --setParameter logicalSessionRefreshMillis=900000 --setParameter localLogicalSessionTimeoutMinutes=45 --oplogSize 20480 --replSet rs0 --quiet
command: >
sh -c '
mongod --storageEngine wiredTiger --wiredTigerCacheSizeGB 32 --timeZoneInfo /usr/share/zoneinfo --setParameter logicalSessionRefreshMillis=900000 --setParameter localLogicalSessionTimeoutMinutes=45 --oplogSize 20480 --replSet rs0 --bind_ip_all --quiet &
until mongosh --host 127.0.0.1 --quiet --eval "
try {
const status = rs.status();
quit(status.ok === 1 ? 0 : 1);
} catch (e) {
if (
e.codeName === \"NotYetInitialized\" ||
e.message.includes(\"no replset config has been received\") ||
e.message.includes(\"not yet initialized\")
) {
rs.initiate({
_id: \"rs0\",
members: [{ _id: 0, host: \"wekandb:27017\" }]
});
quit(1);
}
quit(1);
}
" >/dev/null 2>&1; do
sleep 2
done
wait
'
networks:
- wekan-tier
# Expose only on localhost by default; remove to keep it internal to the network.
ports:
- 127.0.0.1:27017:27017
expose:
- 27017
# Healthcheck: report healthy only once the replica set has an elected
# primary, so the wekan app (depends_on: condition: service_healthy) does
# not start before MongoDB is ready and crash with "Topology is closed".
# start_period gives a large database time to replay its journal after an
# upgrade before failures are counted.
healthcheck:
test: ["CMD", "mongosh", "--host", "127.0.0.1", "--port", "27017", "--quiet", "--eval", "try { quit(rs.status().ok === 1 && db.hello().isWritablePrimary ? 0 : 1) } catch (e) { quit(1) }"]
interval: 10s
timeout: 10s
retries: 30
start_period: 60s
volumes:
- /etc/localtime:/etc/localtime:ro
- wekan-db:/data/db
- wekan-db-dump:/dump
wekan:
#-------------------------------------------------------------------------------------
@@ -123,8 +335,7 @@ services:
# https://github.com/meteor/meteor/blob/release-3.5/v3-docs/docs/performance/change-streams-observer-driver.md#choosing-the-reactivity-driver-order
# Keep oplog/polling fallback available for deployments that cannot use Change Streams:
# https://github.com/wekan/wekan/issues/6307#issuecomment-4299349231
# FerretDB has no MongoDB change streams / replica-set oplog, so use polling:
- METEOR_REACTIVITY_ORDER=polling
- METEOR_REACTIVITY_ORDER=changeStreams,oplog,polling
- DDP_TRANSPORT=uws
#- DDP_TRANSPORT=sockjs
#-----------------------------------------------------------------
@@ -142,7 +353,7 @@ services:
#-----------------------------------------------------------------
# ==== MONGO_URL — points to FerretDB (MongoDB-compatible) ====
#- MONGO_URL=mongodb://wekan-ferretdb:27017/wekan
- MONGO_URL=mongodb://ferretdb:27017/wekan
- MONGO_URL=mongodb://wekandb:27017/wekan
#- MONGO_PASSWORD_FILE=/run/secrets/mongo_password
#---------------------------------------------------------------
# ==== ROOT_URL SETTING ====
@@ -193,7 +404,7 @@ services:
# FerretDB emulates OpLog via --replication-set-name=rs0.
# HIGHLY RECOMMENDED — enables real-time DDP updates (sub-100ms latency).
#- MONGO_OPLOG_URL=mongodb://wekan-ferretdb:27017/local?replicaSet=rs0
# MONGO_OPLOG_URL intentionally unset: FerretDB v1 has no replica-set oplog (WeKan uses polling).
- MONGO_OPLOG_URL=mongodb://wekandb:27017/local?replicaSet=rs0
#---------------------------------------------------------------
# ==== OPTIONAL: KADIRA PERFORMANCE MONITORING FOR METEOR ====
# https://github.com/edemaine/kadira-compose
@@ -782,8 +993,8 @@ services:
# If you use FerretDB instead, comment out the wekandb block below and
# uncomment the wekan-ferretdb block.
depends_on:
ferretdb:
condition: service_started
wekandb:
condition: service_healthy
# wekan-migrate:
# condition: service_completed_successfully
# wekan-ferretdb:
@@ -791,13 +1002,92 @@ services:
volumes:
- /etc/localtime:/etc/localtime:ro
- wekan-files:/data:rw
# Secrets are optional. Uncomment below and ensure files exist to use them.
#secrets:
# - ldap_auth_password
# - oauth2_secret
# - mail_service_password
# - mongo_password
# - s3_secret
#---------------------------------------------------------------------------------
# ==== OPTIONAL: SHARE DATABASE TO OFFICE LAN AND REMOTE VPN ====
# When using Wekan both at office LAN and remote VPN:
# 1) Have above Wekan docker container config with LAN IP address
# 2) Copy all of above wekan container config below, look above of this part above and all config below it,
# before above depends_on: part:
#
# wekan:
# #-------------------------------------------------------------------------------------
# # ==== MONGODB AND METEOR VERSION ====
# # a) For Wekan Meteor 1.8.x version at meteor-1.8 branch, .....
#
#
# and change name to different name like wekan2 or wekanvpn, and change ROOT_URL to server VPN IP
# address.
# 3) This way both Wekan containers can use same MongoDB database
# and see the same Wekan boards.
# 4) You could also add 3rd Wekan container for 3rd network etc.
# EXAMPLE:
# wekan2:
# ....COPY CONFIG FROM ABOVE TO HERE...
# environment:
# - ROOT_URL='http://10.10.10.10'
# ...COPY CONFIG FROM ABOVE TO HERE...
#---------------------------------------------------------------------------------
# OPTIONAL NGINX CONFIG FOR REVERSE PROXY
# nginx:
# image: nginx
# container_name: nginx
# restart: always
# networks:
# - wekan-tier
# depends_on:
# - wekan
# ports:
# - 80:80
# - 443:443
# volumes:
# - ./nginx/ssl:/etc/nginx/ssl/:ro
# - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
## Alternative volume config:
## volumes:
## - ./nginx/nginx.conf:/etc/nginx/conf.d/default.conf:ro
## - ./nginx/ssl/ssl.conf:/etc/nginx/conf.d/ssl/ssl.conf:ro
## - ./nginx/ssl/testvm-ehu.crt:/etc/nginx/conf.d/ssl/certs/mycert.crt:ro
## - ./nginx/ssl/testvm-ehu.key:/etc/nginx/conf.d/ssl/certs/mykey.key:ro
## - ./nginx/ssl/pphrase:/etc/nginx/conf.d/ssl/pphrase:ro
volumes:
wekan-files:
driver: local
ferretdb-data:
#wekan-postgres:
# driver: local
# Legacy MongoDB volumes — kept so existing data survives until migration is done.
# Remove once migration is verified and old MongoDB is decommissioned.
wekan-db:
driver: local
wekan-db-dump:
driver: local
networks:
wekan-tier:
driver: bridge
# Docker Compose Secrets
# Create secret files on the host system before running docker-compose up
# Example: echo "your_password_here" > ldap_auth_password.txt
# Then use: docker-compose up -d
# Secrets are optional. Uncomment to enable and ensure files exist at provided paths.
#secrets:
# ldap_auth_password:
# file: ./secrets/ldap_auth_password.txt
# oauth2_secret:
# file: ./secrets/oauth2_secret.txt
# mail_service_password:
# file: ./secrets/mail_service_password.txt
# mongo_password:
# file: ./secrets/mongo_password.txt
# s3_secret:
# file: ./secrets/s3_secret.txt
-2
View File
@@ -36,8 +36,6 @@
# to a fresh value (5003, 5004, …). The MongoDB service and the
# reverse proxy in front of WeKan don't need any change.
version: '3.8'
services:
# ---------------------------------------------------------------------
+79 -356
View File
@@ -1,278 +1,77 @@
# Note: Do not add single quotes '' to variables. Having spaces still works without quotes where required.
#---------------------------------------------------------------------------------------------------------
# ==== CREATING USERS AND LOGGING IN TO WEKAN ====
# https://github.com/wekan/wekan/blob/main/docs/Login/Adding-users.md
#---------------------------------------------------------------------------------------------------------
# ==== FORGOT PASSWORD ====
# https://github.com/wekan/wekan/blob/main/docs/Login/Forgot-Password.md
#---------------------------------------------------------------------------------------------------------
# ==== Upgrading Wekan to new version =====
# NOTE: MongoDB has changed from 3.x to 4.x, in that case you need backup/restore with --noIndexRestore
# see https://github.com/wekan/wekan/tree/main/docs/Backup
# 1) Stop Wekan:
# docker compose stop
# 2) Remove old Wekan app (wekan-app only, not that wekan-db container that has all your data)
# docker rm wekan-app
# 3) Get newest docker-compose.yml from https://github.com/wekan/wekan to have correct image,
# for example: "image: quay.io/wekan/wekan" or version tag "image: quay.io/wekan/wekan:v4.52"
# 4) Start Wekan:
# docker compose up -d
#----------------------------------------------------------------------------------
# ==== OPTIONAL: DEDICATED DOCKER USER ====
# 1) Optionally create a dedicated user for Wekan, for example:
# sudo useradd -d /home/wekan -m -s /bin/bash wekan
# 2) Add this user to the docker group, then logout+login or reboot:
# sudo usermod -aG docker wekan
# 3) Then login as user wekan.
# 4) Create this file /home/wekan/docker-compose.yml with your modifications.
#----------------------------------------------------------------------------------
# ==== RUN DOCKER AS SERVICE ====
# 1a) Running Docker as service, on Systemd like Debian 9, Ubuntu 16.04, CentOS 7:
# sudo systemctl enable docker
# sudo systemctl start docker
# 1b) Running Docker as service, on init.d like Debian 8, Ubuntu 14.04, CentOS 6:
# sudo update-rc.d docker defaults
# sudo service docker start
# ----------------------------------------------------------------------------------
# ==== USAGE OF THIS docker-compose.yml ====
# 1) For seeing does Wekan work, try this and check with your web browser:
# docker compose up
# 2) Stop Wekan and start Wekan in background:
# docker compose stop
# docker compose up -d
# 3) See running Docker containers:
# docker ps
# 4) Stop Docker containers:
# docker compose stop
# ----------------------------------------------------------------------------------
# ===== INSIDE DOCKER CONTAINERS, AND BACKUP/RESTORE ====
# https://github.com/wekan/wekan/tree/main/docs/Backup
# If really necessary, repair MongoDB: https://github.com/wekan/wekan-mongodb/issues/6#issuecomment-424004116
# 1) Going inside containers:
# a) Wekan app, does not contain data
# docker exec -it wekan-app bash
# b) MongoDB, contains all data
# docker exec -it wekan-db bash
# 2) Copying database to outside of container:
# docker exec -it wekan-db bash
# cd /data
# mongodump
# exit
# docker cp wekan-db:/data/dump .
# 3) Restoring database
# # 1) Stop wekan
# docker stop wekan-app
# # 2) Go inside database container
# docker exec -it wekan-db bash
# # 3) and data directory
# cd /data
# # 4) Remove previous dump
# rm -rf dump
# # 5) Exit db container
# exit
# # 6) Copy dump to inside docker container
# docker cp dump wekan-db:/data/
# # 7) Go inside database container
# docker exec -it wekan-db bash
# # 8) and data directory
# cd /data
# # 9) Restore
# mongorestore --drop
# # 10) Exit db container
# exit
# # 11) Start wekan
# docker start wekan-app
#-------------------------------------------------------------------------
# This docker-compose.yml uses FerretDB v1 with SQLite from
# https://github.com/wekan/FerretDB by default.
#
# WeKan with FerretDB v1 + embedded SQLite (no PostgreSQL, no MongoDB)
#
# This is the DEFAULT WeKan compose file (docker-compose.yml): a light,
# self-contained database — FerretDB v1 (the wekan/FerretDB fork,
# https://github.com/wekan/FerretDB) with its embedded pure-Go SQLite backend,
# which speaks the MongoDB wire protocol. There is no separate PostgreSQL or
# MongoDB server — FerretDB stores everything in SQLite files on a volume, and
# WeKan stores attachments/avatars on the filesystem.
# For the classic MongoDB 7 option instead, see docker-compose-mongodb-v7.yml;
# for the PostgreSQL-backed FerretDB 2 option, see
# docker-compose-ferretdb-v2-postgresql.yml.
#
# The FerretDB binary is downloaded (once, then cached on the volume) from the
# newest wekan/FerretDB release: https://github.com/wekan/FerretDB/releases
# Each platform is a separate ferretdb-<arch> asset there; the container downloads
# only the one matching its architecture (amd64, arm64, ppc64le, s390x, riscv64, ...).
#
# Setup (this is the default docker-compose.yml, so no -f is needed):
# docker compose up -d
#
# To stop:
# docker compose stop
services:
#-------------------------------------------------------------------------------------
# ==== DATABASE: FerretDB 2 + PostgreSQL 16 ====
# FerretDB is a MongoDB-compatible proxy that stores data in PostgreSQL.
# It supports the full MongoDB wire protocol used by Meteor/WeKan,
# including OpLog via replication-set emulation (--replication-set-name=rs0).
#
# Upgrade path from MongoDB:
# The wekan-migrate service below runs ONCE before wekan starts.
# It copies all data from an existing MongoDB instance (if reachable at
# SOURCE_MONGO_URL) to FerretDB, upgrades the schema to v8.43, and
# moves GridFS / CollectionFS binary files to the filesystem.
# Progress is visible in a browser while migration runs.
#
# If you are upgrading from a MongoDB-based install:
# 1. Keep your old MongoDB container running (or start it separately).
# 2. Set SOURCE_MONGO_URL in the wekan-migrate environment below.
# 3. Run: docker compose up -d
# 4. Watch migration at http://localhost:8080/ until "completed".
# 5. Shut down old MongoDB once satisfied.
#
# If this is a fresh install, wekan-migrate exits instantly (nothing to migrate).
#-------------------------------------------------------------------------------------
#
#wekan-postgres:
# image: postgres:16-alpine
# container_name: wekan-postgres
# restart: always
# networks:
# - wekan-tier
# expose:
# - 5432
# environment:
# - POSTGRES_DB=wekan
# - POSTGRES_USER=wekan
# - POSTGRES_PASSWORD=wekan
# # Tune for a kanban workload (low connection count, moderate write rate)
# - POSTGRES_INITDB_ARGS=--encoding=UTF8 --locale=C
# volumes:
# - /etc/localtime:/etc/localtime:ro
# - wekan-postgres:/var/lib/postgresql/data
# healthcheck:
# test: ["CMD-SHELL", "pg_isready -U wekan -d wekan"]
# interval: 5s
# timeout: 5s
# retries: 10
#
#wekan-ferretdb:
# image: ghcr.io/ferretdb/ferretdb:2
# container_name: wekan-ferretdb
# restart: always
# networks:
# - wekan-tier
# expose:
# - 27017
# environment:
# # FerretDB stores everything in PostgreSQL
# - FERRETDB_POSTGRESQL_URL=postgresql://wekan:wekan@wekan-postgres:5432/wekan
# # Emulate MongoDB replica-set for Meteor OpLog (real-time updates)
# - FERRETDB_REPLICATION_SET_NAME=rs0
# # Suppress verbose debug output
# - FERRETDB_LOG_LEVEL=warn
# depends_on:
# wekan-postgres:
# condition: service_healthy
# healthcheck:
# test: ["CMD", "ferretdb", "--version"]
# interval: 5s
# timeout: 5s
# retries: 10
#
#-------------------------------------------------------------------------------------
# ==== MIGRATION SERVICE ====
# Runs once, before WeKan starts. Exits 0 on success, 1 on fatal error.
# WeKan only starts after this service exits successfully
# (depends_on condition: service_completed_successfully).
#
# On a FRESH install (no SOURCE_MONGO_URL or source unreachable) it exits
# immediately — no penalty for new deployments.
#
# SOURCE_MONGO_URL: point to your old MongoDB container/host.
# e.g. mongodb://wekandb:27017/wekan
# mongodb://192.168.1.10:27017/wekan
# Leave it unset or empty to skip migration.
#-------------------------------------------------------------------------------------
#wekan-migrate:
# image: node:24.17.0-slim
# container_name: wekan-migrate
# restart: "no"
# networks:
# - wekan-tier
# working_dir: /migrate
# # Install the mongodb driver then run the migration script.
# # npm ci is used if package-lock.json exists; npm install otherwise.
# command: >
# sh -c "
# cd /migrate &&
# npm install --omit=dev --prefer-offline 2>/dev/null || npm install --omit=dev &&
# node migrate-mongodb-to-ferretdb.mjs
# "
# environment:
# # ---- Source (old MongoDB) ----
# # Set to your old MongoDB URL to trigger data migration.
# # Leave empty for a fresh install (migration is skipped automatically).
# - SOURCE_MONGO_URL=
# #- SOURCE_MONGO_URL=mongodb://wekandb:27017/wekan
#
# # ---- Target (FerretDB) ----
# - TARGET_MONGO_URL=mongodb://wekan-ferretdb:27017/wekan
#
# # ---- File storage ----
# # Must match the WRITABLE_PATH used by the wekan service.
# - WRITABLE_PATH=/data
#
# # ---- Progress dashboard ----
# # Browse to http://localhost:8080/ while migration runs.
# - MIGRATION_PORT=8080
#
# # ---- Tuning (optional) ----
# #- BATCH_SIZE=200
# #- DRY_RUN=true # Log only, no writes — useful for testing
# #- FORCE_MIGRATE=true # Re-run even if already marked complete
# ports:
# - 8080:8080
# depends_on:
# wekan-ferretdb:
# condition: service_healthy
# volumes:
# - /etc/localtime:/etc/localtime:ro
# - wekan-files:/data:rw
# - ./releases:/migrate:ro
#-------------------------------------------------------------------------------------
# ==== LEGACY MONGODB (commented out) ====
# Uncomment to keep old MongoDB running alongside FerretDB during migration.
# After migration is verified, remove this block entirely.
#-------------------------------------------------------------------------------------
wekandb:
image: mongo:7
container_name: wekan-db
# FerretDB v1 with the embedded SQLite backend (MongoDB-compatible on :27017).
# A tiny Debian container fetches the wekan/FerretDB v1 release binary for its
# architecture (cached on the volume so restarts do not re-download) and runs it.
# SQLite data lives in /data/sqlite on the ferretdb-data volume.
ferretdb:
image: debian:bookworm-slim
container_name: wekan-ferretdb
restart: always
#command: mongod --logpath /dev/null --storageEngine wiredTiger --wiredTigerCacheSizeGB 32 --timeZoneInfo /usr/share/zoneinfo --setParameter logicalSessionRefreshMillis=900000 --setParameter localLogicalSessionTimeoutMinutes=45 --oplogSize 20480 --replSet rs0 --quiet
#command: mongod --storageEngine wiredTiger --wiredTigerCacheSizeGB 32 --timeZoneInfo /usr/share/zoneinfo --setParameter logicalSessionRefreshMillis=900000 --setParameter localLogicalSessionTimeoutMinutes=45 --oplogSize 20480 --replSet rs0 --quiet
command: >
sh -c '
mongod --storageEngine wiredTiger --wiredTigerCacheSizeGB 32 --timeZoneInfo /usr/share/zoneinfo --setParameter logicalSessionRefreshMillis=900000 --setParameter localLogicalSessionTimeoutMinutes=45 --oplogSize 20480 --replSet rs0 --bind_ip_all --quiet &
until mongosh --host 127.0.0.1 --quiet --eval "
try {
const status = rs.status();
quit(status.ok === 1 ? 0 : 1);
} catch (e) {
if (
e.codeName === \"NotYetInitialized\" ||
e.message.includes(\"no replset config has been received\") ||
e.message.includes(\"not yet initialized\")
) {
rs.initiate({
_id: \"rs0\",
members: [{ _id: 0, host: \"wekandb:27017\" }]
});
quit(1);
}
quit(1);
}
" >/dev/null 2>&1; do
sleep 2
done
wait
'
environment:
DO_NOT_TRACK: "1"
FERRETDB_TELEMETRY: disable
# Pin a specific release instead of the newest by setting e.g.
# FERRETDB_RELEASE=download/v1.24.2
FERRETDB_RELEASE: ${FERRETDB_RELEASE:-latest/download}
command:
- sh
- -c
- |
set -eu
BIN=/data/bin/ferretdb
if [ ! -x "$$BIN" ]; then
echo "Fetching FerretDB v1 from the wekan/FerretDB release ..."
apt-get update -qq
apt-get install -y -qq --no-install-recommends curl ca-certificates >/dev/null
arch="$$(dpkg --print-architecture)"
case "$$arch" in ppc64el) arch=ppc64le ;; esac
mkdir -p /data/bin
# Download only this arch's binary (per-arch release assets, no ferretdb.zip).
curl -fSL --retry 5 -o "$$BIN" \
"https://github.com/wekan/FerretDB/releases/$${FERRETDB_RELEASE}/ferretdb-$${arch}"
chmod +x "$$BIN"
fi
mkdir -p /data/files/db
exec "$$BIN" \
--handler=sqlite \
--sqlite-url=file:/data/files/db/ \
--listen-addr=0.0.0.0:27017 \
--telemetry=disable \
--log-level=error
volumes:
- ferretdb-data:/data
networks:
- wekan-tier
expose:
- 27017
# Healthcheck: report healthy only once the replica set has an elected
# primary, so the wekan app (depends_on: condition: service_healthy) does
# not start before MongoDB is ready and crash with "Topology is closed".
# start_period gives a large database time to replay its journal after an
# upgrade before failures are counted.
healthcheck:
test: ["CMD", "mongosh", "--host", "127.0.0.1", "--port", "27017", "--quiet", "--eval", "try { quit(rs.status().ok === 1 && db.hello().isWritablePrimary ? 0 : 1) } catch (e) { quit(1) }"]
interval: 10s
timeout: 10s
retries: 30
start_period: 60s
volumes:
- /etc/localtime:/etc/localtime:ro
- wekan-db:/data/db
- wekan-db-dump:/dump
# Expose only on localhost by default; remove to keep it internal to the network.
ports:
- 127.0.0.1:27017:27017
wekan:
#-------------------------------------------------------------------------------------
@@ -326,9 +125,12 @@ services:
# https://github.com/meteor/meteor/blob/release-3.5/v3-docs/docs/performance/change-streams-observer-driver.md#choosing-the-reactivity-driver-order
# Keep oplog/polling fallback available for deployments that cannot use Change Streams:
# https://github.com/wekan/wekan/issues/6307#issuecomment-4299349231
- METEOR_REACTIVITY_ORDER=changeStreams,oplog,polling
- DDP_TRANSPORT=uws
#- DDP_TRANSPORT=sockjs
# FerretDB has no MongoDB change streams / replica-set oplog, so use polling:
- DEFAULT_METEOR_REACTIVITY_ORDER=polling
- METEOR_REACTIVITY_ORDER=polling
# uws does not work at s390x. sockjs works.
#- DDP_TRANSPORT=uws
- DDP_TRANSPORT=sockjs
#-----------------------------------------------------------------
# ==== WRITEABLE PATH FOR FILE UPLOADS ====
- WRITABLE_PATH=/data
@@ -344,7 +146,7 @@ services:
#-----------------------------------------------------------------
# ==== MONGO_URL — points to FerretDB (MongoDB-compatible) ====
#- MONGO_URL=mongodb://wekan-ferretdb:27017/wekan
- MONGO_URL=mongodb://wekandb:27017/wekan
- MONGO_URL=mongodb://ferretdb:27017/wekan
#- MONGO_PASSWORD_FILE=/run/secrets/mongo_password
#---------------------------------------------------------------
# ==== ROOT_URL SETTING ====
@@ -395,7 +197,7 @@ services:
# FerretDB emulates OpLog via --replication-set-name=rs0.
# HIGHLY RECOMMENDED — enables real-time DDP updates (sub-100ms latency).
#- MONGO_OPLOG_URL=mongodb://wekan-ferretdb:27017/local?replicaSet=rs0
- MONGO_OPLOG_URL=mongodb://wekandb:27017/local?replicaSet=rs0
# MONGO_OPLOG_URL intentionally unset: FerretDB v1 has no replica-set oplog (WeKan uses polling).
#---------------------------------------------------------------
# ==== OPTIONAL: KADIRA PERFORMANCE MONITORING FOR METEOR ====
# https://github.com/edemaine/kadira-compose
@@ -984,8 +786,8 @@ services:
# If you use FerretDB instead, comment out the wekandb block below and
# uncomment the wekan-ferretdb block.
depends_on:
wekandb:
condition: service_healthy
ferretdb:
condition: service_started
# wekan-migrate:
# condition: service_completed_successfully
# wekan-ferretdb:
@@ -993,92 +795,13 @@ services:
volumes:
- /etc/localtime:/etc/localtime:ro
- wekan-files:/data:rw
# Secrets are optional. Uncomment below and ensure files exist to use them.
#secrets:
# - ldap_auth_password
# - oauth2_secret
# - mail_service_password
# - mongo_password
# - s3_secret
#---------------------------------------------------------------------------------
# ==== OPTIONAL: SHARE DATABASE TO OFFICE LAN AND REMOTE VPN ====
# When using Wekan both at office LAN and remote VPN:
# 1) Have above Wekan docker container config with LAN IP address
# 2) Copy all of above wekan container config below, look above of this part above and all config below it,
# before above depends_on: part:
#
# wekan:
# #-------------------------------------------------------------------------------------
# # ==== MONGODB AND METEOR VERSION ====
# # a) For Wekan Meteor 1.8.x version at meteor-1.8 branch, .....
#
#
# and change name to different name like wekan2 or wekanvpn, and change ROOT_URL to server VPN IP
# address.
# 3) This way both Wekan containers can use same MongoDB database
# and see the same Wekan boards.
# 4) You could also add 3rd Wekan container for 3rd network etc.
# EXAMPLE:
# wekan2:
# ....COPY CONFIG FROM ABOVE TO HERE...
# environment:
# - ROOT_URL='http://10.10.10.10'
# ...COPY CONFIG FROM ABOVE TO HERE...
#---------------------------------------------------------------------------------
# OPTIONAL NGINX CONFIG FOR REVERSE PROXY
# nginx:
# image: nginx
# container_name: nginx
# restart: always
# networks:
# - wekan-tier
# depends_on:
# - wekan
# ports:
# - 80:80
# - 443:443
# volumes:
# - ./nginx/ssl:/etc/nginx/ssl/:ro
# - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
## Alternative volume config:
## volumes:
## - ./nginx/nginx.conf:/etc/nginx/conf.d/default.conf:ro
## - ./nginx/ssl/ssl.conf:/etc/nginx/conf.d/ssl/ssl.conf:ro
## - ./nginx/ssl/testvm-ehu.crt:/etc/nginx/conf.d/ssl/certs/mycert.crt:ro
## - ./nginx/ssl/testvm-ehu.key:/etc/nginx/conf.d/ssl/certs/mykey.key:ro
## - ./nginx/ssl/pphrase:/etc/nginx/conf.d/ssl/pphrase:ro
volumes:
wekan-files:
driver: local
#wekan-postgres:
# driver: local
# Legacy MongoDB volumes — kept so existing data survives until migration is done.
# Remove once migration is verified and old MongoDB is decommissioned.
wekan-db:
driver: local
wekan-db-dump:
ferretdb-data:
driver: local
networks:
wekan-tier:
driver: bridge
# Docker Compose Secrets
# Create secret files on the host system before running docker-compose up
# Example: echo "your_password_here" > ldap_auth_password.txt
# Then use: docker-compose up -d
# Secrets are optional. Uncomment to enable and ensure files exist at provided paths.
#secrets:
# ldap_auth_password:
# file: ./secrets/ldap_auth_password.txt
# oauth2_secret:
# file: ./secrets/oauth2_secret.txt
# mail_service_password:
# file: ./secrets/mail_service_password.txt
# mongo_password:
# file: ./secrets/mongo_password.txt
# s3_secret:
# file: ./secrets/s3_secret.txt
+1 -1
View File
@@ -4,7 +4,7 @@
## WeKan
- Alternatively, use wekan-app Docker container from https://raw.githubusercontent.com/wekan/wekan/refs/heads/main/docker-compose.yml
- Alternatively, use the ready-made FerretDB 2 + PostgreSQL compose file from https://raw.githubusercontent.com/wekan/wekan/refs/heads/main/docker-compose-ferretdb-v2-postgresql.yml (the default docker-compose.yml uses FerretDB v1 with SQLite instead)
```
git clone --branch main --depth 1 https://github.com/wekan/wekan.git
@@ -1,5 +1,3 @@
version: '2'
# Note: Do not add single quotes '' to variables. Having spaces still works without quotes where required.
#---------------------------------------------------------------------------------------------------------
# ==== CREATING USERS AND LOGGING IN TO WEKAN ====
@@ -55,28 +55,32 @@ cd wekan
Because it downgrades @meteorjs/rspack and breaks builds.
### 3. Select option 1 to install dependencies, and then Enter.
### 3. Install dependencies, build WeKan, and run the dev server
`rebuild-wekan.sh` shows a two-level menu. The top level is `1) Setup 2) Dev server 3) Tests 4) Docker 5) Tools 6) Quit`; pick a category number, then the item number inside it (each submenu also has a `Back` entry).
```
# Setup -> Install dependencies
./rebuild-wekan.sh
1 # Setup
1 # Install dependencies
1
# Setup -> Build WeKan
./rebuild-wekan.sh
1 # Setup
2 # Build WeKan
2
# Dev server -> localhost:3000
./rebuild-wekan.sh
3
2 # Dev server
1 # localhost:3000
```
That does:
- 1 install dependencies,
- 2 builds wekan
- 3 starts wekan in development mode with command `meteor`, so it can detect if some file changes and try to rebuild automatically.
- **Setup -> Install dependencies** installs dependencies,
- **Setup -> Build WeKan** builds wekan,
- **Dev server -> localhost:3000** starts wekan in development mode with command `meteor`, so it can detect if some file changes and try to rebuild automatically. If a dev server is already running on that port, it is stopped first and a fresh one started on the same port.
And then [register and login](../Login/Adding-users.md) with webbrowser at http://localhost:4000
And then [register and login](../Login/Adding-users.md) with webbrowser at http://localhost:3000
### 4. Make and test your changes
+37 -20
View File
@@ -78,23 +78,40 @@ git clone git@github.com:YourGithubUsername/wekan.git
cd wekan
```
### 3. Select option 1 to install dependencies, and then Enter.
### 3. Run the menu: Setup -> Install dependencies, then Setup -> Build WeKan, then Dev server -> localhost:3000
`rebuild-wekan.sh` shows a two-level menu. The top level is:
```
./rebuild-wekan.sh
1
./rebuild-wekan.sh
2
./rebuild-wekan.sh
3
1) Setup 2) Dev server 3) Tests 4) Docker 5) Tools 6) Quit
```
That does: 1 install dependencies, 2 builds wekan, 3 starts wekan in development mode with command `meteor`, so it can detect if some file changes and try to rebuild automatically and reload webbroser. But, still sometimes, it may need stopping with Ctrl-c and full build with option 2.
And then [register and login](../Login/Adding-users.md) at http://localhost:4000
Pick a category number, then the item number inside it (each submenu also has a `Back` entry to return to the top level). To build from source and run it:
```
# Install dependencies: Setup -> Install dependencies
./rebuild-wekan.sh
1 # Setup
1 # Install dependencies
# Build WeKan: Setup -> Build WeKan
./rebuild-wekan.sh
1 # Setup
2 # Build WeKan
# Run in development mode: Dev server -> localhost:3000
./rebuild-wekan.sh
2 # Dev server
1 # localhost:3000
```
The **Setup -> Build WeKan** step compiles WeKan, and **Dev server -> localhost:3000** starts it in development mode with the `meteor` command, so it detects file changes and tries to rebuild automatically and reload the web browser. Still, sometimes it may need stopping with Ctrl-c and a full **Setup -> Build WeKan** again.
If a dev server is already running, the **Dev server** options now stop it automatically before starting a fresh one — freeing **both** the app port and the rspack dev server's port `8080` (a leftover rspack dev server on 8080 otherwise makes the new server crash with `Error: listen EADDRINUSE ... :8080`), so you don't have to kill the old processes yourself.
The other **Dev server** options run WeKan the same way on different addresses/ports: `localhost:3000 + trace warnings`, `localhost:3000 + bundle visualizer`, `CURRENT-IP:3000`, `CURRENT-IP:3000 + MONGO_URL 27019`, and `CUSTOM-IP:PORT` (which asks you for the IP and port). There is also a **Kill all dev servers** option that frees every dev/test port the script uses at once (3000/3001, 3100/3101, 4000/4001 and 8080) — handy if a previous run left something behind.
And then [register and login](../Login/Adding-users.md) at http://localhost:3000
### OPTIONAL, NOT NEEDED: 5. Add new plugin package
```
@@ -145,19 +162,19 @@ Change to Meteor 3 branch:
```
git checkout feature-meteor3
```
Build wekan:
Build wekan (Setup -> Build WeKan):
```
./rebuild-wekan.sh
2
1 # Setup
2 # Build WeKan
```
If there are errors, try to fix them.
Or try to run wekan:
Or try to run wekan (Dev server -> localhost:3000):
```
./rebuild-wekan.sh
3
2 # Dev server
1 # localhost:3000
```
# Updating
+15 -9
View File
@@ -78,23 +78,29 @@ git clone git@github.com:YourGithubUsername/wekan.git
cd wekan
```
### 3. Select option 1 to install dependencies, and then Enter.
### 3. Run the menu: Setup -> Install dependencies, Setup -> Build WeKan, Dev server -> localhost:3000
`rebuild-wekan.sh` shows a two-level menu (`1) Setup 2) Dev server 3) Tests 4) Docker 5) Tools 6) Quit`); pick a category number, then the item number inside it.
```
# Setup -> Install dependencies
./rebuild-wekan.sh
1 # Setup
1 # Install dependencies
1
# Setup -> Build WeKan
./rebuild-wekan.sh
1 # Setup
2 # Build WeKan
2
# Dev server -> localhost:3000
./rebuild-wekan.sh
3
2 # Dev server
1 # localhost:3000
```
That does: 1 install dependencies, 2 builds wekan, 3 starts wekan in development mode with command `meteor`, so it can detect if some file changes and try to rebuild automatically and reload webbroser. But, still sometimes, it may need stopping with Ctrl-c and full build with option 2.
That does: **Setup -> Install dependencies** installs dependencies, **Setup -> Build WeKan** builds wekan, **Dev server -> localhost:3000** starts wekan in development mode with command `meteor`, so it can detect if some file changes and try to rebuild automatically and reload the web browser. But, still sometimes, it may need stopping with Ctrl-c and a full **Setup -> Build WeKan** again. If a dev server is already running on that port, the Dev server options stop it first and start a fresh one on the same port.
And then [register and login](../Login/Adding-users.md) at http://localhost:4000
And then [register and login](../Login/Adding-users.md) at http://localhost:3000
### OPTIONAL, NOT NEEDED: 5. Add new plugin package
```
+11
View File
@@ -1,3 +1,14 @@
## WeKan Docker compose files (which database?)
Since the default database changed, the compose files in https://github.com/wekan/wekan are:
- **docker-compose.yml** — the default: **FerretDB v1 with embedded SQLite** (from https://github.com/wekan/FerretDB). Light and self-contained, no separate database server. Just `docker compose up -d`.
- **docker-compose-mongodb-v7.yml** — the classic **MongoDB 7** setup. Use it with `docker compose -f docker-compose-mongodb-v7.yml up -d`, or rename/copy it to `docker-compose.yml`.
- **docker-compose-ferretdb-v2-postgresql.yml** — **FerretDB 2 with PostgreSQL** (DocumentDB extension).
- **docker-compose-multitenancy.yml** — MongoDB multitenancy setup.
Note: the older instructions below were written for the MongoDB setup; where they say `docker-compose.yml` for MongoDB-specific things (and the `#L...` line-number links), they now refer to **docker-compose-mongodb-v7.yml**.
## Building custom Docker image
This is only for developers. For normal users, do not add these options, just start with `docker compose up -d`
@@ -118,6 +118,8 @@ sudo kill -9 PID-NUMBER-HERE
## 11) Rebuild Wekan
In the menu, pick **Setup -> Build WeKan** (press `1` then `2`):
```
cd ~/repos
./rebuild-wekan.sh
@@ -69,9 +69,11 @@ git merge upstream/master
cd ~/repos
./rebuild-wekan.sh
```
First with option 1, to install deps.
The menu is two levels: pick a category (`1) Setup 2) Dev server 3) Tests 4) Docker 5) Tools 6) Quit`), then an item inside it.
Then same `./rebuild-wekan.sh` again with option 2, to build Wekan.
First **Setup -> Install dependencies** (press `1` then `1`), to install deps.
Then run `./rebuild-wekan.sh` again and pick **Setup -> Build WeKan** (press `1` then `2`), to build Wekan.
## 5) Developing with Standalone Wekan
@@ -81,7 +83,7 @@ meteor --port 4000
```
Wekan is at http://localhost:4000
When you make changes to files, Meteor automatically notices that, and rebuilds Wekan. If Meteor does not notice change, you need to Ctrl-c and `./rebuild-wekan.sh` option 2.
When you make changes to files, Meteor automatically notices that, and rebuilds Wekan. If Meteor does not notice change, you need to Ctrl-c and run `./rebuild-wekan.sh` -> **Setup -> Build WeKan** (press `1` then `2`).
## 6) Using MongoDB
@@ -106,7 +108,7 @@ https://www.nosqlbooster.com/downloads
When your feature works at Standalone Wekan, you can also test it at Sandstorm.
First build wekan with option 2:
First build wekan with **Setup -> Build WeKan** (press `1` then `2`):
```
cd ~/repos/wekan
./rebuild-wekan.sh
@@ -0,0 +1,395 @@
# WeKan on Sandstorm — Meteor 3.5 / Node.js 24 build + MongoDB 3 → FerretDB migration
Status: **design / not yet implemented**. Nothing here has been built or run end‑to‑end
in a grain yet — every step marked **TEST** must be verified against a real Sandstorm
install (ideally a copy of an existing WeKan grain) before shipping.
This document describes how to build a modern WeKan `.spk` (Meteor 3.5, Node.js 24) that
replaces the packaged MongoDB 3.0 database with **FerretDB v1 (embedded SQLite)**, migrating
any existing grain's MongoDB 3.0 data on first launch — reusing the exact migration logic the
WeKan **snap** already ships.
---
## 1. Why
The current Sandstorm build uses **meteor‑spk 0.6.0** (`https://dl.sandstorm.io/meteor-spk-0.6.0.tar.xz`,
built 2021‑10‑23). Its `meteor-spk.deps` payload is a 2015‑era design:
| Component | meteor‑spk 0.6.0 ships | WeKan needs |
|---|---|---|
| `bin/node` | Node **14.17.5** (stock, from nodejs.org) | **Node 24.x** (Meteor 3.5) |
| `bin/mongod` | MongoDB **3.0.7** (WiredTiger) | keep — read‑only migration source only |
| `bin/niscud` | MongoDB **2.x** (Kenton's Niscu fork) | keep (niscu→3.0 migration) |
| `lib/` | glibc **2.31** (Ubuntu 20.04) | regenerate on 22.04 (glibc 2.35) for node24/ferretdb |
| `start.js` | launches Mongo 3.0 + niscu→3.0 migration | rewrite for FerretDB |
`start.js` in 0.6.0 is functionally identical to 0.5.1 (only reformatted). It still launches
mongod 3.0 with `--nohttpinterface` (a flag **removed in MongoDB 3.6+**), so a newer mongod
can't even be dropped in without changing it.
Note on the Node fork: `sandstorm-io/node` is **not** needed. It is frozen at Node 8.11.4
(2018) and its only real patch is a V8 thread‑table optimization for **node‑fibers** — and
Meteor 3 removed fibers entirely. meteor‑spk already ships **stock** upstream Node (0.6.0's
`bin/node` is the official nodejs.org 14.17.5 build). Use stock **Node 24**.
---
## 2. Target architecture
Steady state after migration: WeKan (Node 24) talks to **FerretDB v1 (SQLite)** over the
MongoDB wire protocol — no MongoDB server runs at all. mongod 3.0 is used **once**, only to
read an existing grain's old data during the one‑time migration.
```
grain (single sandbox, writable = /var)
├─ /var/wiredTigerDb ← EXISTING MongoDB 3.0 data (old grains only; read-only source)
├─ /var/files/ ← WRITABLE_PATH (new)
│ ├─ attachments/ ← GridFS attachments extracted here (Meteor-Files on fs)
│ ├─ avatars/ ← GridFS avatars extracted here
│ └─ db/ ← FerretDB SQLite dir (wekan.sqlite) ← steady-state DB
└─ /var/.migration-to-ferretdb-done ← idempotency marker
```
### Ports (loopback inside the grain)
| Port | Role |
|---|---|
| 4000 | app HTTP (behind `sandstorm-http-bridge`) |
| 4001 | FerretDB v1 (steady state) — `MONGO_URL=mongodb://127.0.0.1:4001/wekan` |
| 4003 | temporary mongod 3.0 (migration read only) |
---
## 3. Sandbox compatibility (verified from the sandstorm source)
Checked `sandstorm/src/sandstorm/seccomp-bpf/filter.s`. The grain seccomp filter is an
allowlist whose **default action is `ENOSYS`, not SIGSYS‑kill**, so Go/glibc gracefully fall
back on missing syscalls. Relevant results:
- **Allowed** (needed by Node 24 / Go FerretDB): `getrandom`, `statfs`/`fstatfs`,
`sched_getaffinity`, `clone`, `futex`, `epoll_*`, `eventfd2`, `fork`, `mmap`, `mprotect`.
- **Denied → ENOSYS** (tolerated via fallback): `membarrier`, `rseq`, `clone3`, `restart_syscall`.
Conclusion: a grain can run Node 24 + FerretDB (Go) + mongod 3.0 concurrently — the same
multi‑process model the current build already uses for mongod+node. Nothing else is needed
from the sandstorm platform repo.
**TEST (highest risk):** Node 24's glibc uses `clone3` for thread creation and relies on the
ENOSYS→`clone` fallback (glibc ≥ 2.34). Verify a trivial Node 24 grain spawns threads before
investing in the rest.
---
## 4. `meteor-spk.deps` payload changes
Start from the 0.6.0 base, then:
- **Replace** `bin/node` with **Node 24** — use the exact build from Meteor 3.5's dev bundle
(`meteor node -e "console.log(process.version)"`) so native‑addon ABIs match the WeKan bundle.
- **Keep** `bin/mongod` (3.0.7) — read‑only migration source.
- **Keep** `bin/niscud` (MongoDB 2.x) **and** the old bundled `node_modules/{mongodb,bson,
mongodb-core,es6-promise,readable-stream}` — used by `start.js`'s **niscu → MongoDB 3.0**
stage (Stage 1) for very old grains. Migration support for old versions is permanent and is
not dropped. (0.6.0 already ships both; nothing extra to add.)
- **Add** `migratemongo/bin/{mongoexport,mongo}` + `migratemongo/lib/` (the old glibc those
3.x CLIs need). The importer reads the 3.0 data with these — the modern Node driver cannot
speak to a 3.0/3.2 server. Reuse the same tools the snap's
[`migratemongo`](https://github.com/wekan/migratemongo) provides (amd64, x86_64).
- **Add** `ferretdb` — the `ferretdb-amd64` binary downloaded directly
(newest release of [wekan/FerretDB](https://github.com/wekan/FerretDB/releases); the same
`ferretdb-amd64` asset `release-all.yml` embeds).
- **Add** `migrate-mongo3-to-ferretdb.mjs` — copy verbatim from
[`snap-src/bin/migrate-mongo3-to-ferretdb.mjs`](../../../../../snap-src/bin/migrate-mongo3-to-ferretdb.mjs);
it is entirely env/path‑driven and needs no changes.
- The **importer** (Stage 2) resolves its `mongodb`/`bson` from the WeKan bundle via
`NODE_PATH=<bundle>/programs/server/node_modules` (the modern driver, separate process from
`start.js`, so it does not clash with the old driver Stage 1 uses).
- **Regenerate `lib/`, `lib64/`, `usr/lib`** on Ubuntu 22.04/24.04 (glibc 2.35) for node24 +
ferretdb. Keep the **old** libs separately under `migratemongo/lib` for mongod3/mongoexport
(dual‑lib pattern, exactly as the snap does with `MM_LIB`).
> The 0.5.1 fork's `lib/x86_64-linux-gnu/*` were **dangling symlinks into
> `/home/user/Lataukset/...`** (a Downloads folder). Do not carry those forward — the tree
> must be self‑contained and regenerated with `gather-deps` on a clean modern base.
amd64 only. (arm64 Sandstorm is out of scope here; the migratemongo 3.x binaries are x86_64.)
---
## 5. `start.js` (rewritten launcher)
The canonical launcher is committed at
[`sandstorm-src/start.js`](../../../../../sandstorm-src/start.js); the spk build copies it into
`meteor-spk.deps/start.js`. It is a CJS launcher, spawned by the pkgdef as `... node start.js`.
On first launch it runs the migration chain for whatever the grain holds —
**niscu (2.x) → MongoDB 3.0** (Stage 1, the preserved legacy path, for very old grains) then
**MongoDB 3.0 → FerretDB** (Stage 2) — then runs WeKan on FerretDB. Fresh grains and
already-migrated grains skip straight to running on FerretDB.
Migration logic is a re‑pathed port of the snap's
[`migration-control`](../../../../../snap-src/bin/migration-control) +
[`migrate-mongo3-to-ferretdb.mjs`](../../../../../snap-src/bin/migrate-mongo3-to-ferretdb.mjs).
All app-payload paths resolve from `__dirname` (the grain mount root), and it waits for
mongod 3.0 to answer a ping before running the importer. Abridged shape:
```js
// meteor-spk.deps/start.js (see sandstorm-src/start.js for the full file)
const { spawn, spawnSync } = require('child_process');
const fs = require('fs');
const path = require('path');
const APP_PORT = process.env.PORT || '4000';
const DB_PORT = '4001'; // FerretDB steady-state
const SRC_PORT = '4003'; // temp mongod 3.0 (migration read)
const FILES_DIR = '/var/files';
const SQLITE_DIR = path.join(FILES_DIR, 'db');
const OLD_MONGO = '/var/wiredTigerDb';
const MARKER = '/var/.migration-to-ferretdb-done';
const STATUS = path.join(FILES_DIR, 'db', 'migration-status.json');
const APPROOT = __dirname; // where .meteor-spk/bundle is mounted
const MM_LIB = path.join(APPROOT, 'migratemongo/lib');
for (const d of [FILES_DIR, SQLITE_DIR,
path.join(FILES_DIR, 'attachments'), path.join(FILES_DIR, 'avatars')]) {
fs.mkdirSync(d, { recursive: true });
}
function startFerret(port) {
return spawn(path.join(APPROOT, 'ferretdb'),
['--handler=sqlite', `--sqlite-url=file:${SQLITE_DIR}/`,
`--listen-addr=127.0.0.1:${port}`, '--telemetry=disable'],
{ stdio: 'inherit',
env: { ...process.env, DO_NOT_TRACK: '1', FERRETDB_TELEMETRY: 'disable' } });
}
function migrateIfNeeded() {
const hasOld = fs.existsSync(path.join(OLD_MONGO, 'WiredTiger'));
if (fs.existsSync(MARKER) || !hasOld) return; // fresh install or already migrated
console.log('** Migrating MongoDB 3 -> FerretDB (one-time) ...');
const oldLibEnv = { ...process.env,
LD_LIBRARY_PATH: `${MM_LIB}:${process.env.LD_LIBRARY_PATH || ''}` };
// 1. old mongod 3.0 serving the existing data (read-only source)
spawnSync('/bin/mongod',
['--dbpath', OLD_MONGO, '--bind_ip', '127.0.0.1', '--port', SRC_PORT,
'--storageEngine', 'wiredTiger', '--fork', '--logpath', '/var/migration-mongod.log'],
{ stdio: 'inherit', env: oldLibEnv });
// 2. FerretDB target (the PERMANENT SQLite dir — no temp/switch needed)
const ferret = startFerret(DB_PORT);
// 3. importer: CLI-read 3.0 -> driver-insert FerretDB; GridFS -> /var/files/{attachments,avatars}
const rc = spawnSync(path.join(APPROOT, 'node'),
[path.join(APPROOT, 'migrate-mongo3-to-ferretdb.mjs')], {
stdio: 'inherit',
env: { ...process.env,
NODE_PATH: path.join(APPROOT, 'programs/server/node_modules'),
MONGO_BIN_DIR: path.join(APPROOT, 'migratemongo/bin'),
MONGO_LIB: MM_LIB,
SRC_PORT, SRC_DB: 'wekan',
TARGET_MONGO_URL: `mongodb://127.0.0.1:${DB_PORT}/wekan`,
FILES_DIR,
MIGRATION_PORT: APP_PORT, // progress dashboard shown at the grain URL
STATUS_FILE: STATUS }, // importer writes final state here (see §6)
}).status;
try { ferret.kill(); } catch {}
spawnSync('/bin/mongo', ['--port', SRC_PORT, '--quiet', '--eval',
'db.getSiblingDB("admin").shutdownServer()'], { env: oldLibEnv });
if (rc === 0) {
fs.writeFileSync(MARKER, new Date().toISOString()); // never re-migrate; old data KEPT
} else {
console.error('** Migration failed; will retry on next grain start. Old data kept.');
process.exit(1);
}
}
function runApp() {
const ferret = startFerret(DB_PORT); // steady-state DB
process.env.MONGO_URL = `mongodb://127.0.0.1:${DB_PORT}/wekan`;
process.env.ROOT_URL = process.env.ROOT_URL || `http://127.0.0.1:${APP_PORT}`;
process.env.PORT = APP_PORT;
process.env.WRITABLE_PATH = FILES_DIR;
process.on('exit', () => { try { ferret.kill(); } catch {} });
setTimeout(() => require('./main.js'), 1500); // let FerretDB start listening
}
migrateIfNeeded();
runApp();
```
Design choices vs the snap:
- **No temp‑then‑switch**: the migration writes straight into the permanent FerretDB SQLite
dir (`/var/files/db`), because in a grain there is only one database going forward.
- **Idempotent**: the marker prevents re‑migration; the old `/var/wiredTigerDb` is **never
deleted automatically** — the admin deletes it explicitly from the UI (§7).
---
## 6. What the migration does (importer)
`migrate-mongo3-to-ferretdb.mjs` (unchanged from the snap):
- **Text collections** — `mongoexport` each (Extended JSON) from mongod 3.0, `insertMany`
into FerretDB via the modern Node driver (batch 200, upsert on conflict).
- **Attachments + avatars** — from CollectionFS GridFS (`cfs_gridfs.<bucket>.{files,chunks}`
+ `cfs.<bucket>.filerecord`): each file is reassembled from its chunks and written to
`/var/files/attachments` or `/var/files/avatars`, and a **Meteor‑Files** record pointing at
that filesystem path is inserted into FerretDB. This is exactly WeKan's "MongoDB → filesystem"
attachment move, done inline.
- **Schema** is left as‑is; WeKan's own Board Settings / Migrations upgrade it on first use.
- **Progress** is served over HTTP at `MIGRATION_PORT` (= the app port), so a user opening the
grain during migration sees a live dashboard.
**Add for the UI (§7):** have the importer also write a final status JSON to
`STATUS_FILE` (`/var/files/db/migration-status.json`) — the `state` object it already builds:
`{ startedAt, finishedAt, phase, success, collections, files, errors }`. One `fs.writeFileSync`
at the end of `run()`.
---
## 7. Admin Panel / Attachments / **Sandstorm** (new, `isSandstorm` only)
**Implemented** — server: [`server/methods/sandstormMigration.js`](../../../../../server/methods/sandstormMigration.js);
client: the **Sandstorm** tab in [`client/components/settings/attachments.jade`](../../../../../client/components/settings/attachments.jade) /
[`.js`](../../../../../client/components/settings/attachments.js); strings in
[`imports/i18n/data/en.i18n.json`](../../../../../imports/i18n/data/en.i18n.json). The importer
writes `migration-status.json` (STATUS_FILE) that the panel reads.
When `isSandstorm === true` (`Meteor.settings.public.sandstorm`, see
[models/settings.js](../../../../../models/settings.js#L19)), a new **Sandstorm** section appears
in Admin Panel / Attachments (next to Backup), showing:
1. **Migration status** — Success / Pending / Failed + timestamp and per‑collection / file
counts, read from `/var/files/db/migration-status.json` and the marker.
2. **Raw MongoDB disk usage** — bytes currently used by the old raw MongoDB 3.0 files under
`/var/wiredTigerDb` (the reclaimable space), plus FerretDB SQLite size and attachments/avatars
size for context.
3. **Delete raw MongoDB files** — a guarded button that removes `/var/wiredTigerDb` to free
grain disk. Enabled **only** when migration succeeded (marker present, `success:true`) and
FerretDB actually holds data.
### Server methods
New file `server/methods/sandstormMigration.js` (server‑only; admin‑gated exactly like
[`server/methods/backup.js`](../../../../../server/methods/backup.js) via `ReactiveCache.getCurrentUser()` + `isAdmin`):
```js
const OLD_MONGO = '/var/wiredTigerDb';
const STATUS = (process.env.WRITABLE_PATH || '/var/files') + '/db/migration-status.json';
const MARKER = '/var/.migration-to-ferretdb-done';
function dirBytes(dir) { // recursive size; tolerant of missing dir
let total = 0;
const walk = d => { for (const e of fs.readdirSync(d, { withFileTypes: true })) {
const p = path.join(d, e.name);
if (e.isDirectory()) walk(p);
else { try { total += fs.statSync(p).size; } catch {} }
} };
try { if (fs.existsSync(dir)) walk(dir); } catch {}
return total;
}
Meteor.methods({
async sandstormMigrationStatus() {
const user = await ReactiveCache.getCurrentUser();
if (!user || !user.isAdmin) return false;
let status = null;
try { status = JSON.parse(fs.readFileSync(STATUS, 'utf8')); } catch {}
return {
isSandstorm: true,
migrationDone: fs.existsSync(MARKER),
status,
rawMongoBytes: dirBytes(OLD_MONGO),
rawMongoExists: fs.existsSync(OLD_MONGO),
ferretBytes: dirBytes(path.dirname(STATUS)),
};
},
async sandstormDeleteRawMongo() {
const user = await ReactiveCache.getCurrentUser();
if (!user || !user.isAdmin) throw new Meteor.Error('not-authorized');
// Safety: only after a confirmed-successful migration.
if (!fs.existsSync(MARKER)) throw new Meteor.Error('migration-not-done');
let ok = false;
try { ok = JSON.parse(fs.readFileSync(STATUS, 'utf8')).success === true; } catch {}
if (!ok) throw new Meteor.Error('migration-not-successful');
const freed = dirBytes(OLD_MONGO);
fs.rmSync(OLD_MONGO, { recursive: true, force: true });
return { deleted: true, freedBytes: freed };
},
});
```
### Client
New tab in [client/components/settings/attachments.{jade,js}](../../../../../client/components/settings/attachments.js),
rendered only when `isSandstorm`. Poll `sandstormMigrationStatus` (like the Backup tab polls
`backupStatus`), render the status + a human‑readable size (`filesize`), and a
**Delete raw MongoDB files** button behind a confirm dialog that calls `sandstormDeleteRawMongo`
and refreshes.
> Deleting the raw files is irreversible. Gate it behind: migration `success:true`, an explicit
> confirm, and (recommended) a typed confirmation. The data still exists in FerretDB + on the
> filesystem after migration, so this only reclaims the now‑redundant Mongo 3.0 copy.
---
## 8. pkgdef / env changes ([sandstorm-pkgdef.capnp](../../../../../sandstorm-pkgdef.capnp))
- `WRITABLE_PATH`: `/var/wekan-uploads` → **`/var/files`**.
- Do **not** set `MONGO_URL` in `environ` (start.js sets it to the FerretDB port).
- Bump `appVersion` and `appMarketingVersion`.
- Keep `argv = ["/sandstorm-http-bridge", "4000", "--", "node", "start.js"]`.
- `SANDSTORM=1` and `METEOR_SETTINGS={"public":{"sandstorm":true}}` are already present — that
drives `isSandstorm` for the new admin panel.
---
## 9. Build / CI ([.github/workflows/sandstorm.yml](../../../../../.github/workflows/sandstorm.yml))
- **Base = upstream meteor‑spk 0.6.0**, downloaded from `https://dl.sandstorm.io/meteor-spk-0.6.0.tar.xz`.
It already contains `bin/mongod` (3.0.7), `bin/niscud` (2.x) and the old `node_modules` the
niscu→3.0 stage needs. **Nothing is needed from the old `projects.7z`** (it only holds
0.4.1/0.5.0/0.5.1, and its swapped node is ancient — we install Node 24 anyway). The dead
`releases.wekan.team/dev/meteor-spk/projects.7z` fetch is removed.
- The assembly script ([`sandstorm-src/build-deps.sh`](../../../../../sandstorm-src/build-deps.sh))
modernizes `meteor-spk.deps`: swap in Node 24, add `ferretdb-amd64` (per-arch asset from the wekan/FerretDB release), add
`migratemongo/{bin,lib}` (`mongoexport` + `mongo` + old libs), copy
[`sandstorm-src/start.js`](../../../../../sandstorm-src/start.js) → `meteor-spk.deps/start.js`
and [`snap-src/bin/migrate-mongo3-to-ferretdb.mjs`](../../../../../snap-src/bin/migrate-mongo3-to-ferretdb.mjs)
→ `meteor-spk.deps/`, **keep `niscud`**, and regenerate the lib tree with `gather-deps` on ubuntu‑24.04.
- Fetch the extra binaries (Node 24, `ferretdb-amd64`, migratemongo CLIs) from **GitHub release
assets** — `releases.wekan.team` no longer exists, so any required build files live on GitHub
releases (e.g. `wekan/wekan` or a dedicated release).
---
## 10. Risks & test checklist
- [ ] **TEST** Node 24 threads under seccomp (clone3→clone ENOSYS fallback). *Highest risk.*
- [ ] **TEST** mongod 3.0.7 opens `/var/wiredTigerDb` inside the grain with the old libs.
- [ ] **TEST** FerretDB (Go) starts and listens in the grain.
- [ ] **TEST** full migration on a **copy** of a real old WeKan grain (text + attachments + avatars).
- [ ] **TEST** fresh install (no `/var/wiredTigerDb`): skips migration, runs on empty FerretDB.
- [ ] **TEST** grain disk headroom — migration transiently holds old Mongo + new SQLite + extracted
files at once, within the grain quota.
- [ ] **TEST** `LD_LIBRARY_PATH` split — node24/ferretdb on the fresh 2.35 libs; mongo‑3.0 CLIs on
the old libs; no cross‑contamination.
- [ ] **TEST** Admin Panel / Attachments / Sandstorm: status accuracy, disk numbers, guarded delete.
---
## 11. Open questions
- FerretDB v1 SQLite filename: **confirmed** — for db `wekan` the backend writes
`<sqlite-dir>/wekan.sqlite` (plus SQLite WAL sidecars `wekan.sqlite-shm` / `wekan.sqlite-wal`).
So the disk-usage sum of the `db/` dir already covers it.
- Bundle mount root in the grain: `sandstorm-src/start.js` resolves app-payload paths from
`__dirname` (so `bin/mongod`, `ferretdb`, `migratemongo/`, `main.js` are all relative to the
launcher). Confirm from the packed spk that the added binaries land where `start.js` expects
(e.g. `migratemongo/` and `ferretdb` at the mount root, CLIs under `migratemongo/bin`).
- Migration support from old versions (niscu 2.x and MongoDB 3.0) is **permanent** — it is not
dropped, so `niscud`, mongod 3.0 and the CLI-based importer stay in the package.
+55 -1
View File
@@ -2,6 +2,59 @@
# Sandstorm at Debian and Ubuntu
### New Sandstorm WeKan at 2026-07
Backup your current Sandstorm first !
1. Please first backup your Sandstorm https://docs.sandstorm.io/en/latest/administering/backups/
2. Please first download all of your grains to .zip files from top menu row down arrow button, just in case.
This new Sandstorm WeKan uses fork of FerretDB v1 SQLite at https://github.com/wekan/FerretDB
- FerretDB is drop-in replacement for MongoDB 7 Server
- FerretDB implements MongoDB 7 server wire protocol
- FerretDB converts MongoDB Javascript queries to SQLite SQL queries
- FerretDB saves data to SQLite database
- Fork has additional MongoDB features
- Fork is maintained by xet7
Migrating old MongoDB 3 data
- If there is old WeKan data, it is automatically migrated when opening old WeKan grain.
Attachments are migrated from MongoDB to files/attachments.
Text data is migrated from MongoDB to SQLite at files/db/wekan.sqlite .
- After migrating, you may get error, that browser can not open that page embedded to other page.
So you need to close WeKan grain and open it again. Sorry, trying to fix it later.
All Boards page
- WeKan starts at All Boards page Favorites
- All your boards are at first at Remaining, until you Star to have your board at Favorites
- You can move boards from Remaining to your personal Workspaces or Sub-Workspaces
After migrating, free some disk space
- If after migrating you would like to free disk space of WeKan grain
by deleting old MongoDB raw database files
- At right top corner, click your WeKan username at WeKan board (not at Sandstorm black backround) /
Member Settings / Admin Panel / Attachments / Sandstorm / Delete raw MongoDB database files.
Cover image
- You can enable it for minicard and card at:
Right Sidebar/Board Settings/Card Settings/Cover Image
(at bottom of Card Settings list).
Download
1. Please wait before there is more testing of new version, and appears to Official Sandstorm Store.
2. Currently newest at [Experimental Sanstorm Store](https://apps.sandstorm.io/app/m86q05rdvj14yvn78ghaxynqz7u2svw6rnttptxx49g1785cdv1h?experimental=true)
3. Later will be at [Official Sandstorm Store](https://apps.sandstorm.io/app/m86q05rdvj14yvn78ghaxynqz7u2svw6rnttptxx49g1785cdv1h)
4. But, if you use CloudFlare, there may be 100 MB file size upload limit,
it prevents uploading wekan.spk as file to your Sandstorm.
5. New experimental wekan.spk install file at WeKan 9.87 or newer
at https://github.com/wekan/wekan/releases
### Sandstorm Radicale: Calendars and Contacts
- 2025-08-05
@@ -141,7 +194,8 @@ Install to your own server. Automatic updates, tested before release. Sandstorm
## Wekan App
Wekan at [experimental](https://apps.sandstorm.io/app/m86q05rdvj14yvn78ghaxynqz7u2svw6rnttptxx49g1785cdv1h?experimental=true) or [official](https://apps.sandstorm.io/app/m86q05rdvj14yvn78ghaxynqz7u2svw6rnttptxx49g1785cdv1h) Sandstorm App Market. Note: Only use official. Experimental versions are broken.
Wekan at [experimental](https://apps.sandstorm.io/app/m86q05rdvj14yvn78ghaxynqz7u2svw6rnttptxx49g1785cdv1h?experimental=true) or
[official](https://apps.sandstorm.io/app/m86q05rdvj14yvn78ghaxynqz7u2svw6rnttptxx49g1785cdv1h) Sandstorm App Market. Note: Only use official. Experimental versions are broken.
Newest Wekap app .spk file download at https://releases.wekan.team/sandstorm/
+168
View File
@@ -0,0 +1,168 @@
# WeKan Snap — CPU platforms and databases
This page documents, **for the WeKan snap**, which CPU architectures are built,
which database binaries each one ships, how new installs choose their database,
and how the one-time MongoDB 3 → FerretDB v1 migration works.
## Summary
- **New installs use FerretDB v1 (SQLite) by default on every CPU architecture.**
FerretDB v1 is the wekan/FerretDB fork with an embedded pure-Go SQLite backend
that speaks the MongoDB wire protocol, so WeKan talks to it exactly like MongoDB.
- **MongoDB 7 *server* binaries (mongod) are included for amd64 and arm64 only.**
The other architectures (s390x, riscv64, ppc64le) have no MongoDB server — they
run FerretDB v1 only.
- **Every Snap platform includes the FerretDB v1 server and the MongoDB Database
Tools** (`mongodump`, `mongorestore`, `mongofiles`, `mongoexport`, …), on every
architecture.
- **`mongosh` is NOT bundled at all.** WeKan already ships Node.js 24 and the
`mongodb` driver, and all scripted database access (readiness checks,
replica-set init, schema migration) uses that via `$SNAP/bin/db-eval` instead of
the MongoDB Shell. This removes a large, CVE-prone binary and works identically
on every architecture. See [MongoDB client binaries](#mongodb-client-binaries-source-and-availability).
- **The MongoDB Database Tools are downloaded from WeKan's own fork, not from the
MongoDB website** — `mongodump-<arch>` etc. from
[wekan/mongo-tools](https://github.com/wekan/mongo-tools/releases).
- **Existing MongoDB 7 data (amd64/arm64) is NOT migrated to FerretDB v1** — that
snap keeps using its existing MongoDB 7.
- **Only the amd64 snap migrates existing MongoDB 3 data to FerretDB v1** (see
[Migration](#mongodb-3--ferretdb-v1-migration-amd64-only) below).
## Per-architecture matrix
| CPU arch | MongoDB 7 server (mongod) | MongoDB Database Tools | FerretDB v1 server | MongoDB 3 → FerretDB migration | Default DB (new install) |
|----------|:------------------------:|:----------------------:|:------------------:|:------------------------------:|:------------------------:|
| amd64 | ✅ | ✅ | ✅ | ✅ (if MongoDB 3 data present) | FerretDB v1 |
| arm64 | ✅ | ✅ | ✅ | ❌ | FerretDB v1 |
| s390x | ❌ | ✅ | ✅ | ❌ | FerretDB v1 |
| ppc64le | ❌ | ✅ | ✅ | ❌ | FerretDB v1 |
| riscv64 | ❌ | ✅ | ✅ | ❌ | FerretDB v1 |
- **MongoDB 7 server (mongod)**: amd64/arm64 only (MongoDB ships no server for the others).
- **MongoDB Database Tools**: every arch — WeKan builds them for all platforms from
[wekan/mongo-tools](https://github.com/wekan/mongo-tools) (they are pure Go).
- **mongosh**: not bundled on any arch — replaced by the bundled Node.js 24 +
`mongodb` driver (`$SNAP/bin/db-eval`).
All architectures default new installs to FerretDB v1 with `DDP_TRANSPORT=sockjs`
and polling reactivity.
## New installs
On a fresh install, every architecture starts on **FerretDB v1 (SQLite)** with
these snap defaults (in [`snap-src/bin/config`](../../../../../snap-src/bin/config)):
- `database` = `ferretdb` — FerretDB v1 is the default backend.
- `ddp-transport` (`DDP_TRANSPORT`) = `sockjs` — maximum proxy compatibility.
- Reactivity = **polling**. FerretDB v1 has no replica-set oplog or change
streams, so WeKan uses polling for live updates (it does this automatically
when the backend is FerretDB).
On amd64/arm64 you can still switch an install to the bundled MongoDB 7 server:
```
sudo snap set wekan database=mongodb # amd64/arm64 only (mongod is bundled there)
sudo snap set wekan database=ferretdb # the default
```
## MongoDB client binaries: source and availability
WeKan does not download MongoDB clients from the MongoDB website:
- **MongoDB Database Tools** come from [wekan/mongo-tools](https://github.com/wekan/mongo-tools/releases).
These are pure Go, so its `build-binaries.yml` workflow cross-compiles **every
architecture** (`bsondump`, `mongodump`, `mongoexport`, `mongofiles`,
`mongoimport`, `mongorestore`, `mongostat`, `mongotop`), including arches MongoDB
never shipped tools for (riscv64, loong64). Every WeKan build (snap, bundle,
Docker, Sandstorm) downloads the one `<tool>-<arch>` it needs from the newest
release.
- **`mongosh` is not used at all.** It is a large Node.js-packaged binary (it
embeds its own Node and drags in a heavy, CVE-prone dependency tree) that cannot
be cross-compiled for s390x/ppc64le/riscv64. Since WeKan already bundles Node.js
24 and the `mongodb` driver, every scripted MongoDB/FerretDB operation the snap
used mongosh for — readiness `ping`, replica-set `initiate`/`status`, the v8.43
schema migration — now runs through `$SNAP/bin/db-eval` (a tiny wrapper around
the bundled Node + driver). This works identically on every architecture and
removed the mongosh binary from the snap entirely.
The `mongo` shell that IS still present is only the legacy MongoDB 3.2 `mongo`
(from `migratemongo`, amd64 only), used at migration time to read old MongoDB 3
data — the modern driver cannot speak to a 3.2 server. It is not used at runtime.
## MongoDB 3 → FerretDB v1 migration (amd64 only)
Only the **amd64** snap ships the MongoDB 3-specific binaries (the legacy MongoDB
3.2 `mongo` shell + `mongofiles`, bundled via `migratemongo`). They are used **at
migration time only** — a one-time conversion of old data — and are **never a
runtime component**: after the migration WeKan runs on FerretDB v1 and the
MongoDB 3 binaries are not used again. No other architecture ships them at all
(s390x/ppc64le/riscv64 never had a MongoDB 3, so there is nothing to migrate).
The migration runs only on amd64, and only when existing **MongoDB 3** data (from
an old WeKan 6.09-era snap) is present. During the migration **both databases run
at the same time on different ports** — MongoDB 3 on its port and FerretDB v1 on
its port — and data moves directly from one to the other:
- **Attachments and avatars** (binary files): read from the MongoDB CollectionFS
GridFS and MongoDB Meteor-Files GridFS collections with the MongoDB 3-specific
`mongofiles` command, and written to:
- `$SNAP_COMMON/files/attachments/`
- `$SNAP_COMMON/files/avatars/`
- **Text data** (all boards and other non-file data — everything that is *not*
attachments or avatars): copied directly from the MongoDB 3 port to the
FerretDB v1 port using the legacy MongoDB 3 `mongo` CLI (mongo shell); the
modern `mongosh` cannot talk to a MongoDB 3 server.
After a successful migration the snap switches to `database=ferretdb`.
Architectures other than amd64 ship no MongoDB server and no MongoDB 3 client, so
there is nothing to migrate from — they are FerretDB v1 from the first boot.
## Where the FerretDB v1 binary comes from
FerretDB v1 is built and released separately in
[wekan/FerretDB](https://github.com/wekan/FerretDB/releases) as one binary per
architecture (`ferretdb-<arch>`; there is no `ferretdb.zip`). Each WeKan build
downloads only the single binary for the platform it targets, e.g.:
```
https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-amd64
https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-arm64
https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-s390x
https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-riscv64
https://github.com/wekan/FerretDB/releases/latest/download/ferretdb-ppc64le
```
For the snap, that binary is embedded inside the `wekan-<version>-<arch>.zip`
bundle the snap's `wekan` part downloads, and staged to `$SNAP/ferretdb`
(started by `ferretdb-control`).
## How the bundled binary versions are kept current
- The **MongoDB 7 server (mongod)** is the one component still fetched from
MongoDB (amd64/arm64 only). The `bump` job in
[`.github/workflows/release-all.yml`](../../../../../.github/workflows/release-all.yml)
runs [`releases/version.sh`](../../../../../releases/version.sh), which probes
upstream and rewrites the pinned MongoDB 7 server version (and the WeKan bundle
version/URLs) in `snapcraft.yaml`.
- The **FerretDB v1** server and the **MongoDB client binaries** are not pinned:
every build fetches the newest per-arch asset from the WeKan forks —
`ferretdb-<arch>` from [wekan/FerretDB](https://github.com/wekan/FerretDB/releases),
`<tool>-<arch>` from [wekan/mongo-tools](https://github.com/wekan/mongo-tools/releases),
and `mongosh-<arch>` from [wekan/mongosh](https://github.com/wekan/mongosh/releases).
## Snap channels
The default `snapcraft.yaml` is built on `base: core24`, which allows the
**candidate** channel (core26 does not). The automated release workflow publishes
it to the **candidate**, **beta**, and **edge** channels; the **stable** channel is
published manually later, once it is proven.
`snapcraft-core26.yaml` is the same WeKan on the newer `base: core26`
(`build-base: devel`, `grade: devel`), kept for testing the next base; it can only
go to Beta/Edge until core26 is a released stable base.
## Related
- FerretDB v1 fork: https://github.com/wekan/FerretDB
- Snap install: [Install.md](Install.md)
- Snap settings keys: [Supported-settings-keys.md](Supported-settings-keys.md)
+2 -2
View File
@@ -10,7 +10,7 @@ This is without container (without Docker or Snap).
Right click and download files 1-4:
1. [wekan-9.84-win64.zip](https://github.com/wekan/wekan/releases/download/v9.84/wekan-9.84-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
1. [wekan-9.89-win64.zip](https://github.com/wekan/wekan/releases/download/v9.89/wekan-9.89-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
2. [node.exe](https://nodejs.org/dist/latest-v24.x/win-x64/node.exe)
@@ -22,7 +22,7 @@ Right click and download files 1-4:
6. Double click `mongodb-windows-x86_64-7.0.34-signed.msi` . In installer, uncheck downloading MongoDB compass.
7. Unzip `wekan-9.84-win64.zip` , inside it is directory `bundle`, to it copy other files:
7. Unzip `wekan-9.89-win64.zip` , inside it is directory `bundle`, to it copy other files:
```
bundle (directory)
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Buat Panel",
"home": "Beranda",
"import": "Impor",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Berlakon sebagai pengguna",
"link": "Pautan",
"import-board": "import papan",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storan",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Skep bord",
"home": "Tuis",
"import": "Invoer",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Verpersoonlik gebruiker",
"link": "Skakel",
"import-board": "invoerbord",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Berging",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Skep bord",
"home": "Tuis",
"import": "Invoer",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Verpersoonlik gebruiker",
"link": "Skakel",
"import-board": "invoerbord",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Berging",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "إنشاء لوحة",
"home": "الرئيسية",
"import": "وارد کردن",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "جعل هویت کاربر",
"link": "رابط",
"import-board": "استيراد لوحة",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Stockage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "إنشاء لوحة",
"home": "الرئيسية",
"import": "وارد کردن",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "جعل هویت کاربر",
"link": "رابط",
"import-board": "استيراد لوحة",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "إنشاء لوحة",
"home": "الرئيسية",
"import": "وارد کردن",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "جعل هویت کاربر",
"link": "رابط",
"import-board": "استيراد لوحة",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "إنشاء لوحة",
"home": "الرئيسية",
"import": "وارد کردن",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "جعل هویت کاربر",
"link": "رابط",
"import-board": "استيراد لوحة",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Şura yaradın",
"home": "Ev",
"import": "İdxal",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Təqlid edən istifadəçi",
"link": "Link",
"import-board": "idxal lövhəsi",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Saxlama",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Şura yaradın",
"home": "Ev",
"import": "İdxal",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Təqlid edən istifadəçi",
"link": "Link",
"import-board": "idxal lövhəsi",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Saxlama",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Şura yaradın",
"home": "Ev",
"import": "İdxal",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Təqlid edən istifadəçi",
"link": "Link",
"import-board": "idxal lövhəsi",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Saxlama",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Създай Табло",
"home": "Начало",
"import": "Импорт",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Увуци се у налог овог корисника",
"link": "Връзка",
"import-board": "Импортирай Табло",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Складиште",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Créer un tableau",
"home": "Accueil",
"import": "Importer",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Utilisateur usurpé",
"link": "Lien",
"import-board": "importer un tableau",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Stockage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crea tauler",
"home": "Inici",
"import": "importa",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Suplantar l'usuari",
"link": "Enllaç",
"import-board": "Importa tauler",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Emmagatzematge",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crea tauler",
"home": "Inici",
"import": "importa",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Suplantar l'usuari",
"link": "Enllaç",
"import-board": "Importa tauler",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Emmagatzematge",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crea tauler",
"home": "Inici",
"import": "importa",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Suplantar l'usuari",
"link": "Enllaç",
"import-board": "Importa tauler",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Emmagatzematge",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "创建板",
"home": "家",
"import": "进口",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "冒充用户",
"link": "关联",
"import-board": "进口板",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "贮存",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Vytvořit tablo",
"home": "Domů",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Napodobit uživatele",
"link": "Propojit",
"import-board": "Importovat tablo",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Vytvořit tablo",
"home": "Domů",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Napodobit uživatele",
"link": "Propojit",
"import-board": "Importovat tablo",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Creu Bwrdd",
"home": "Cartref",
"import": "Mewnforio",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Dynwared defnyddiwr",
"link": "Cyswllt",
"import-board": "bwrdd mewnforio",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storio",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Creu Bwrdd",
"home": "Cartref",
"import": "Mewnforio",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Dynwared defnyddiwr",
"link": "Cyswllt",
"import-board": "bwrdd mewnforio",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storio",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Opret tavle",
"home": "Hjem",
"import": "Importér",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Log ind som bruger",
"link": "Link",
"import-board": "importer tavle",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Lagring",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Board erstellen",
"home": "Home",
"import": "Importieren",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "als Benutzer ausgeben",
"link": "Verknüpfung",
"import-board": "Board importieren",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Speicher",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Board erstellen",
"home": "Home",
"import": "Importieren",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "als Benutzer ausgeben",
"link": "Verknüpfung",
"import-board": "Board importieren",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Speicher",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Board erstellen",
"home": "Home",
"import": "Importieren",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "als Benutzer ausgeben",
"link": "Verknüpfung",
"import-board": "Board importieren",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Speicher",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Board erstellen",
"home": "Home",
"import": "Importieren",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "als Benutzer ausgeben",
"link": "Verknüpfung",
"import-board": "Board importieren",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Speicher",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Δημιουργία Πίνακα",
"home": "Αρχική",
"import": "Εισαγωγή",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersona utente",
"link": "Σύνδεσμος",
"import-board": "Εισαγωγή πίνακα",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Stockage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Δημιουργία Πίνακα",
"home": "Αρχική",
"import": "Εισαγωγή",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersona utente",
"link": "Σύνδεσμος",
"import-board": "Εισαγωγή πίνακα",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Stockage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Create Board",
"home": "Home",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonate user",
"link": "Link",
"import-board": "import board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Krei tavolon",
"home": "Hejmo",
"import": "Importi",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Ligilo",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear Tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonar usuario",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear tablero",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Enlace",
"import-board": "importar un tablero",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Almacenamiento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Loo juhatus",
"home": "Kodu",
"import": "Import",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Kasutajaks kehastumine",
"link": "Link",
"import-board": "impordikomisjon",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Sortu arbela",
"home": "Hasiera",
"import": "Inportatu",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Impersonalizar",
"link": "Esteka",
"import-board": "inportatu arbela",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Biltegiratzea",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "ایجاد برد",
"home": "خانه",
"import": "وارد کردن",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "جعل هویت کاربر",
"link": "ارتباط",
"import-board": "وارد کردن برد",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "ایجاد برد",
"home": "خانه",
"import": "وارد کردن",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "جعل هویت کاربر",
"link": "ارتباط",
"import-board": "وارد کردن برد",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Storage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Luo taulu",
"home": "Koti",
"import": "Tuo",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Esiinny käyttäjänä",
"link": "Linkitä",
"import-board": "tuo taulu",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Kopioidaanko kaikki tekstipohjaiset kokoelmat kohteeseen __db__? Tämä ei vaikuta tiedostojärjestelmässä oleviin liitetiedostoihin ja profiilikuviin. Kohdetietokannan on oltava käynnissä.",
"database-migration-phase": "Vaihe",
"database-migration-done": "Tekstidatan siirto valmistui.",
"sandstorm-migration-description": "Kun WeKan on käynnissä Sandstorm-jyvässä, sen vanha MongoDB 3 -tietokanta siirretään ensimmäisellä käynnistyksellä FerretDB v1:een (SQLite), ja liitetiedostot ja profiilikuvat siirretään tietokannasta jyvän hakemistoihin files/attachments ja files/avatars. Tässä näkyy, onnistuiko siirto ja kuinka paljon levytilaa vanhat raa'at MongoDB-tietokantatiedostot yhä käyttävät jyvässä, ja tästä voit poistaa nuo raakatiedostot vapauttaaksesi tilaa.",
"sandstorm-migration-status": "Siirron tila",
"sandstorm-migration-success": "Onnistui",
"sandstorm-migration-failed": "Epäonnistui",
"sandstorm-migration-pending": "Ei vielä siirretty",
"sandstorm-storage-item": "Tallennustila",
"sandstorm-disk-usage": "Levytilan käyttö",
"sandstorm-raw-mongodb": "Raa'at MongoDB 3 -tietokantatiedostot",
"sandstorm-delete-raw-mongodb": "Poista raa'at MongoDB-tietokantatiedostot",
"sandstorm-delete-raw-mongodb-description": "Onnistuneen siirron jälkeen data sijaitsee FerretDB:ssä ja tiedostojärjestelmässä, joten vanhat raa'at MongoDB 3 -tietokantatiedostot voidaan poistaa jyvän levytilan vapauttamiseksi. Tätä ei voi peruuttaa.",
"sandstorm-delete-raw-mongodb-confirm": "Poistetaanko raa'at MongoDB 3 -tietokantatiedostot levytilan vapauttamiseksi? Data on jo siirretty FerretDB:hen ja tiedostojärjestelmään. Tätä ei voi peruuttaa.",
"sandstorm-raw-mongodb-deleted": "Raa'at MongoDB-tietokantatiedostot poistettu, vapautettu",
"collections": "kokoelmaa",
"features": "Ominaisuudet",
"features-performance": "Suorituskyky",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Créer un tableau",
"home": "Accueil",
"import": "Importer",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Utilisateur usurpé",
"link": "Lien",
"import-board": "importer un tableau",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Stockage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Créer un tableau",
"home": "Accueil",
"import": "Importer",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Utilisateur usurpé",
"link": "Lien",
"import-board": "importer un tableau",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Stockage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Créer un tableau",
"home": "Accueil",
"import": "Importer",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Utilisateur usurpé",
"link": "Lien",
"import-board": "importer un tableau",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Stockage",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Meitsje Board",
"home": "Thús",
"import": "Ymport",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Imitearje brûker",
"link": "Link",
"import-board": "ymportearje board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Opslach",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Meitsje Board",
"home": "Thús",
"import": "Ymport",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Imitearje brûker",
"link": "Link",
"import-board": "ymportearje board",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Opslach",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear taboleiro",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Personificar utilizador",
"link": "Ligação",
"import-board": "importar taboleiro",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Armazenamento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "Crear taboleiro",
"home": "Inicio",
"import": "Importar",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "Personificar utilizador",
"link": "Ligação",
"import-board": "importar taboleiro",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "Armazenamento",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "બોર્ડ બનાવો",
"home": "ઘર",
"import": "આયાત કરો",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "નકલી વપરાશકર્તા",
"link": "લિંક",
"import-board": "આયાત બોર્ડ",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "સંગ્રહ",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
+14
View File
@@ -588,6 +588,8 @@
"headerBarCreateBoardPopup-title": "יצירת לוח",
"home": "בית",
"import": "יבוא",
"imported-member-no-account": "Imported member — no matching account yet",
"inactive-member": "Inactive member",
"impersonate-user": "התחזות למשתמש",
"link": "קישור",
"import-board": "ייבוא לוח",
@@ -1842,6 +1844,18 @@
"database-migration-confirm": "Copy all text-based collections to __db__? Attachments and avatars on the filesystem are not affected. The target database must be running.",
"database-migration-phase": "Phase",
"database-migration-done": "Text-data migration completed.",
"sandstorm-migration-description": "When WeKan runs inside a Sandstorm grain, its old MongoDB 3 database is migrated to FerretDB v1 (SQLite) on first launch, and attachments and avatars are moved from the database to the grain's files/attachments and files/avatars directories. This shows whether that migration succeeded and how much disk space the old raw MongoDB database files still use inside the grain, and lets you delete those raw files to free space.",
"sandstorm-migration-status": "Migration status",
"sandstorm-migration-success": "Succeeded",
"sandstorm-migration-failed": "Failed",
"sandstorm-migration-pending": "Not migrated yet",
"sandstorm-storage-item": "אחסון",
"sandstorm-disk-usage": "Disk usage",
"sandstorm-raw-mongodb": "Raw MongoDB 3 database files",
"sandstorm-delete-raw-mongodb": "Delete raw MongoDB database files",
"sandstorm-delete-raw-mongodb-description": "After a successful migration the data lives in FerretDB and on the filesystem, so the old raw MongoDB 3 database files can be deleted to free grain disk space. This cannot be undone.",
"sandstorm-delete-raw-mongodb-confirm": "Delete the raw MongoDB 3 database files to free disk space? The data has already been migrated to FerretDB and the filesystem. This cannot be undone.",
"sandstorm-raw-mongodb-deleted": "Raw MongoDB database files deleted, freed",
"collections": "collections",
"features": "Features",
"features-performance": "Performance",
Loaded 100 of 250 files, more files were not shown because too many files have changed in this diff. Show more