On 02/10/24 05:02, Eric Morgan wrote:
My workflow with beangulp is that I have a script that runs import.py for each bank
Why one script for each bank? The framework is written with the intent of allowing multiple types of transactions sources to be processed at the same time.
The script then copies the imported files to an folder for imported files.
This is automated by the framework, just use the 'archive' command.
I'm sure this workflow is not ideal. Is there any repo that showcases a better workflow when using beangulp?
I'm not sure what you mean. beangulp does not try to impose any particular workflow. However, if you are sure that what you are doing is not idea, you most likely have identified shortcomings in your approach. If you can explain what you would like to do more efficiently, we may be able to suggest a way to do it. Otherwise, it is hard to provide any hint.
Cheers, Dan -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/938407a2-c1eb-4196-bef4-f222f478c179%40grinta.net.
