kato/warpbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
49 Commits 2 Branches 10 Tags
fbeff3f6c0a6b8fc630b698c0b55375e20c3ed1d
Commit Graph
8 Commits
Author SHA1 Message Date
kato fbeff3f6c0 feat/security
Build and Publish Docker Image / deploy (push) Successful in 1m44s
Details 
Reviewed-on: #2
 2026-05-04 00:00:36 +03:00
kato 1cf38d126d refactor(storage): standardize size limits to use GB units 2026-05-01 02:14:05 +03:00
kato d0aa86205f feat(setting): Implemented the settings administrative menu 2026-05-01 01:51:06 +03:00
kato f0b723e35d refactor(code): Cleaned-up the code base 2026-04-30 11:05:56 +03:00
kato a729b641b2 feat(one-time-downloads): add expiry and retry configuration 
Introduce new environment variables to control the behavior of one-time download boxes:
- `WARPBOX_ONE_TIME_DOWNLOAD_EXPIRY_SECONDS`: Sets the lifetime of a one-time box after uploads are complete.
- `WARPBOX_ONE_TIME_DOWNLOAD_RETRY_ON_FAILURE`: Determines whether a box remains available if the ZIP creation or transfer fails.

To support these settings, the ZIP delivery process was refactored to use a temporary file. This ensures that a one-time box is only marked as consumed after the file has been successfully transferred to the client, preventing data loss on network interruptions.

Additionally, added a `DecorateFiles` helper in the box store to reduce code duplication.
 2026-04-30 04:24:49 +03:00
kato 7d70a0c2ed feat(boxstore): add configurable expiry for one-time downloads 
Introduces a new configuration setting `one_time_download_expiry_seconds` to allow administrators to define a default expiration period for one-time downloads.

The retention logic in `boxstore` has been updated to use this global expiry value when a box is marked as a one-time download and no specific retention period is defined in the manifest.
 2026-04-30 03:54:50 +03:00
kato 6035ea1eb2 feat(config): support *_MB env vars for upload size limits 
- Add `applyMegabytesOrBytesEnv` to accept size settings in either bytes or MB
- Prefer `*_BYTES` when set, otherwise convert `*_MB` to bytes with overflow guard
- Add coverage for MB-based environment overrides
- Introduce `static/js/upload-popups.js` to lazy-load and cache popup templatesfeat(config): support *_MB env vars for upload size limits

- Add `applyMegabytesOrBytesEnv` to accept size settings in either bytes or MB
- Prefer `*_BYTES` when set, otherwise convert `*_MB` to bytes with overflow guard
- Add coverage for MB-based environment overrides
- Introduce `static/js/upload-popups.js` to lazy-load and cache popup templates
 2026-04-29 01:42:41 +03:00
kato a5d6d69be0 docs: expand configuration docs for admin and BadgerDB 
Update README to explain startup config precedence (defaults/env/admin overrides),
document admin/bootstrap and feature toggles, and clarify storage locations under
WARPBOX_DATA_DIR including BadgerDB metadata. Also refresh project layout to
include new config and metastore packages.docs: expand configuration docs for admin and BadgerDB

Update README to explain startup config precedence (defaults/env/admin overrides),
document admin/bootstrap and feature toggles, and clarify storage locations under
WARPBOX_DATA_DIR including BadgerDB metadata. Also refresh project layout to
include new config and metastore packages.
 2026-04-28 21:11:37 +03:00