mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 03:55:58 +03:00
[GH-ISSUE #135] setup.py is missing out package 'admin' #103
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @Lucki on GitHub (Sep 23, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/135
I've installed papermerge through
setup.pybut the resulting package is missing out 'admin' and isn't starting.A workaround to for this is to copy
papermerge/contribintobuild/lib/papermergebefore runningpython setup.py buildandpython setup.py install --root="$pkgdir" --optimize=1 --skip-buildlater.@ciur commented on GitHub (Sep 23, 2020):
Hi @Lucki,
thank you for trying Papermerge.
In theory it sounded to me as if it is a great idea to have a pypi package for papermerge.
But in practice - I never use papermerge pypi package.
I always end-up cloning from the repo - even in production environments.
This explains why "admin" is missing (papermerge.contrib.admin was introduced since about 2 months ago).
Thank you for bringing up this issue, I will take care of it!
@Lucki commented on GitHub (Sep 23, 2020):
I actually did create all necessary PKGBUILDs for Arch Linux but currently I'm not happy with Papermerge after some fiddling around so I think I'm not going to push them into the AUR.
@ciur commented on GitHub (Sep 23, 2020):
Maybe you can list points which you didn't like about Papermerge here. I would gladly consider your feedback and improve application in future.
@amo13 commented on GitHub (Sep 24, 2020):
I was just looking for a nice PKGBUILD in the AUR, so I can only encourage you to publish it there and maybe really state the issues you are having. Sometimes, solutions can be found unexpectedly easily ;)
@Lucki commented on GitHub (Sep 24, 2020):
I'll do but I need to figure out the exact points first. In general it's that the whole usage feels really clunky and I doubt they aren't already mentioned somewhere around here.
I don't want to maintain these without using them so I won't publish them there. But I drop them here in case someone wants to pick them up.
The main PKGBUILD with the associated sysusers, service unit and tmpfiles needs some general polish. I was in the process of hooking gunicorn between django and nginx but my OCR broke while doing that. That's the current state.
papermerge
papermerge-worker.service
papermerge-gunicorn.service
papermerge.sh
papermerge.sysusers
papermerge.tmpfiles
python-django-celery-results
python-django-modelcluster
python-django-mptt
python-django-polymorphic-tree
python-django-rest-knox
python-django-tag-parser
python-mgclipboard
python-mglib
@ciur commented on GitHub (Sep 26, 2020):
@Lucki, thank you for your hard work!
I will leave this ticket open maybe someone volunteers to continue your effort.
@amo13 commented on GitHub (Sep 26, 2020):
I might continue this but don't count on it just yet, since I have no experience with packaging yet and I also need to try papermerge first to see if I'm actually going to use it
Anyway, thank you for leaving this here!
@Lucki commented on GitHub (Sep 27, 2020):
I'm coming from Paperwork and while I'm still happy with it I wanted to look into similar project with multi user capability.
So here's a list with things which aren't ideal IMHO:
@ciur commented on GitHub (Sep 27, 2020):
Hi @Lucki,
thank you very much for your feedback. I really appreciate it, because I heavily rely on this sort of feedback to improve the application. I am sort of "blindly" in love with Papermerge, which makes me unable to see many of its problems. I will open a separate enhancement ticket to keep track of your remarks.
The only thing that I want comment is regarding this point:
this is not true anymore (well, at least in master branch :) ). In couple of weeks I will release newer version which will introduce tag management (I realized just very recently how useful tags really are!).
@amo13 commented on GitHub (Sep 27, 2020):
The apparent contra for paperwork ist that is appears to be only a desktop and no web based application. In that manner, it is simply not comparable with papermerge.
Docspell though could actually inspire further ideas for papermerge I guess.
@ciur commented on GitHub (Sep 29, 2020):
thanks @amo13, I will have a look at docspell project for inspiration.
@amo13 commented on GitHub (Sep 29, 2020):
Awesome! I am still trying to figure out which software I want to go for, considering papermerge, docspell and teedy, which appear to be the web-based candidates that are open-source and self-hostable.
About docspell: I like a lot the idea of having automatic correspondent identification and automatic tagging according to the content of a document. These would be awesome features in papermerge too. But I think I'm not going to install docspell because of the reliance on apache solr for full text search. I don't feel like spinning up and running this colossus just for full text search.
About teedy: what draws me to teedy is the simple fact that the project is already 7 years old, which makes me hope that it will not get abandoned in a year or so. Unfortunately, the drawback of young and innovative projects is that a lot of them end up abandoned before having the chance to actually flourish...
@ciur commented on GitHub (Sep 30, 2020):
My plans with papermerge span over several decades. It takes time to build a good product.
@amo13 commented on GitHub (Mar 31, 2021):
Though I don't know exactly how, the admin package seems to be better integrated now and does not need to be moved in place any more. Therefore, I guess, this issue can be closed.