[FEATURE] [QUESTION] Make MBOX Export non-interactive so it can be used with cron

Open
  • Is something wrong?
#274 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

Start by finding the bichon-cli export command and tracing where it prompts during MBOX export. The issue gives an example with --account-id and --output-dir; check how those options are parsed and what input still requires interaction. Done means the export can run unattended for scheduled backups and the example command works without prompts.

Written by the indexing model from the issue text.

Description

enhancement

Please write and communicate in English.

Description

Make the export non-interactive so it can be used with/as cronjob

eg.:

bichon-cli export
--account-id 1
--output-dir /data/bichon-data/exports \

Purpose / Use Case

simple backup shedules

Additional Information (optional)

Would be great to add a Discussion Board, so users can help user with Q&A.

edit: i am using TrueNas Scale 25.10 with Bichon

App Version:
1.3.0
Version:
1.1.12

Dominant language
Rust
Stars
2.1k
Forks
91
Avg merge
14h 54m
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustmailer/bichon

All issues in rustmailer/bichon

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.