MokoConsulting/MokoJoomBackup
1
0
Fork 0
Code Issues 22 Pull Requests 1 Packages Projects Releases 1 Wiki Activity

Feature: S3-compatible storage backend #16

New Issue
Open
opened 2026-06-02 20:29:30 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-02 20:29:30 +00:00
Owner
Copy Link
Copy Source

Add S3-compatible remote storage (AWS S3, Wasabi, Backblaze B2, MinIO).

Description

Many hosting setups use S3-compatible storage for offsite backups. Add an S3 uploader that works with any S3-compatible API.

Requirements

  • New RemoteUploaderInterface implementation: S3Uploader
  • Profile fields: endpoint URL, access key, secret key, bucket, path prefix, region
  • Multipart upload for large files
  • No SDK dependency (use cURL with AWS Signature V4)
  • Support custom endpoints (Wasabi, B2, MinIO)
  • Connection test method
Add S3-compatible remote storage (AWS S3, Wasabi, Backblaze B2, MinIO). ## Description Many hosting setups use S3-compatible storage for offsite backups. Add an S3 uploader that works with any S3-compatible API. ## Requirements - [ ] New RemoteUploaderInterface implementation: S3Uploader - [ ] Profile fields: endpoint URL, access key, secret key, bucket, path prefix, region - [ ] Multipart upload for large files - [ ] No SDK dependency (use cURL with AWS Signature V4) - [ ] Support custom endpoints (Wasabi, B2, MinIO) - [ ] Connection test method
jmiller added the type: featurepriority: mediumcomponent: remotestatus: ready labels 2026-06-02 20:29:30 +00:00
jmiller commented 2026-06-02 20:29:30 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan

TC-F3.1: AWS S3 upload

  1. Configure with AWS S3 credentials
  2. Run backup
  3. Verify file appears in S3 bucket

TC-F3.2: Custom endpoint (Wasabi/MinIO)

  1. Configure with custom endpoint URL
  2. Run backup
  3. Verify upload to custom S3-compatible service

TC-F3.3: Large file multipart

  1. Create backup > 100 MB
  2. Upload to S3
  3. Verify multipart upload completes

TC-F3.4: Connection test

  1. Run testConnection()
  2. Verify bucket is accessible

TC-F3.5: Invalid credentials

  1. Use wrong access key
  2. Verify clear error message
  3. Verify local backup preserved
## Testing Plan **TC-F3.1: AWS S3 upload** 1. Configure with AWS S3 credentials 2. Run backup 3. Verify file appears in S3 bucket **TC-F3.2: Custom endpoint (Wasabi/MinIO)** 1. Configure with custom endpoint URL 2. Run backup 3. Verify upload to custom S3-compatible service **TC-F3.3: Large file multipart** 1. Create backup > 100 MB 2. Upload to S3 3. Verify multipart upload completes **TC-F3.4: Connection test** 1. Run testConnection() 2. Verify bucket is accessible **TC-F3.5: Invalid credentials** 1. Use wrong access key 2. Verify clear error message 3. Verify local backup preserved
Sign in to join this conversation.
Labels
Clear labels
component: admin
Admin UI and views
 component: api
REST API
 component: engine
Backup/restore engine
 component: remote
Remote storage (FTP/GDrive)
 component: scheduler
Scheduled tasks
 priority: critical
Must fix before release
 priority: high
Important for release
 priority: low
Nice to have
 priority: medium
Normal priority
 status: blocked
Blocked by dependency
 status: ready
Ready for development
 type: bug
Something is broken
 type: docs
Documentation
 type: feature
New feature or enhancement
 type: testing
Testing and QA
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels component: remote priority: medium status: ready type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomBackup#16
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?