Filesystem in User Space for Favro.
takunomi-build-bot
2efec7ef83
All checks were successful
Test Python / Test (push) Successful in 34s
This commit was automatically generated by a script: https://gitfub.space/Jmaa/repo-manager |
||
---|---|---|
.gitea/workflows | ||
favro_sync | ||
test | ||
.gitignore | ||
LICENSE | ||
README.md | ||
requirements_test.txt | ||
requirements.txt | ||
ruff.toml | ||
setup.py |
Favro Sync.
Filesystem in User Space for Favro.
Synchronize your local notes and your Favro.
Uses the Favro API. Rate limiting depends upon your organization's payment plan.
Uses python-fuse
library.
Features:
- Local access to cards in todolist.
- Read card features:
- Title
- Description
- Tags
- Assignees
- Dependencies
- Change card features:
- Title
- Description
- Obsidian compatibility:
- Mountable within your vault.
- Link to cards by either card number or card title.
- Tags and dependencies are integrated.
Limitations:
- Only cards in todolist is fetched at the moment.
- Tasks (checklists on cards) cannot be updated or changed.
- Images cannot be updated or changed.
- You cannot create new cards, nor any other files.
Usage
- Install dependencies
pip install -r requirements.txt
- Setup secrets:
FAVRO_ORGANIZATION_ID
,FAVRO_USERNAME
,FAVRO_PASSWORD
. - Run
python -m favro_sync <MOUNT_DIR>
. Use the--help
argument to get an overview of all supported flags (there is a lot, becausepython-fuse
implements a whole bunch automatically.)
Architecture
FavroFuse
- Markdown Parser/Renderer
FavroClient
CardCache
Work in Progress
Following features are work in progress:
- Frontmatter: Update Tags
- Frontmatter: Updated assigned members
- Frontmatter: Arbitrary structured data? Read-only.
- Frontmatter: Dependencies. As vault links in Obsidian mode.
- Allow users to toggle Obsidian mode, instead of being default.
- Get the correct last-modified date.
- Improve cache behaviour. User and tags can have much longer cache times.
Dependencies
All requirements can be installed easily using:
pip install -r requirements.txt
Full list of requirements:
License
MIT License
Copyright (c) 2024 Jon Michael Aanes
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.