Sure thing. Still the named volume issue is like a thorn. I just want to
fix it but I still don't get a few things about the way Mayan is packaged
for Docker.
On Tuesday, March 6, 2018 at 6:48:51 AM UTC-4, RW Shore wrote:
>
> Actually, the whole volume stuff should be taken as a low-priority
>
>From what I've seen it is usually a problem connecting to the database. Be
it hosted or in another docker image. Make sure you specify the database
driver, the host, user, database name and password correctly. Most of these
have to be specified for the database container AND the Mayan container
This is great news!
>From what I've been seeing on the net, things are still very bad there.
I speak for myself but I'm sure others feel the same way, you are an
inspiration. Not only for your work on Mayan, but for all you've
accomplished, before and after the hurricane. All the sh*t and haras
That branch's work was completed merged into versions/next
=> https://gitlab.com/Michael.Price/mayan-edms/commits/versions/next
On Tuesday, March 6, 2018 at 10:09:31 AM UTC-4, LeVon Smoker wrote:
>
> Michael,
>
> Is it possible to get read access to
> https://gitlab.com/Michael.Price/mayan-edms
If you a client that supports HTTP sessions, you can also log via Mayan's
web interface and all API requests will be authenticated.
On Tuesday, March 13, 2018 at 1:32:15 AM UTC-4, ericr...@gmail.com wrote:
>
> Request a token from /api/auth/token/obtain/ and include it in your
> request headers.
Request a token from /api/auth/token/obtain/ and include it in your request
headers.
On Wednesday, March 7, 2018 at 3:31:39 PM UTC-4, RW Shore wrote:
>
> Ignore the last posting. I had the authentication configured incorrectly.
> It's rolling now.
>
--
---
You received this message because y
Awesome! Thanks!
On Saturday, March 10, 2018 at 6:34:55 AM UTC-4, RW Shore wrote:
>
> I've successfully written a Java program that adds EXIF values as metadata
> to images stored in Mayan. The program also adds any metadata fields that
> don't exist, processes only images with a special 'unpro
Git blame show that Michael was working on that a few days ago.
e88050747a mayan/apps/metadata/models.py (Michael Price 2018-03-10
13:18:55 -0400 165) class Meta:
e88050747a mayan/apps/metadata/models.py (Michael Price 2018-03-10
13:18:55 -0400 166) ordering = ('metadata_type',)
I think metadata types are already sorted. I'll take a look.
On Saturday, March 10, 2018 at 6:41:17 AM UTC-4, RW Shore wrote:
>
> The ordering of metadata tags is not consistent from page to page. In
> particular, the display on the document-type setup page where one specifies
> the allowed meta
Sweet! I gonna give it a try.
On Saturday, March 10, 2018 at 11:27:42 AM UTC-4, RW Shore wrote:
>
> I have created an external, Java application that adds EXIF metadata as
> metadata fields to Mayan-maintained images. The app is on GitHub at
>
> https://github.com/shorero/ExifExtractor.git
>
>
>
When you use the "Tag" search box, whatever you type will be search against
all available tags.
On Monday, March 12, 2018 at 7:21:03 AM UTC-4, Costi Budai wrote:
>
> Somebody? Any idea how to "Advance Search" using multiple Tags?
> Thanks in advance!
>
> On Thursday, March 8, 2018 at 11:03:43 AM
I'm not use I understand. I think you are mixing several concepts.
* Document types are classes of documents: receipts, statements, invoices.
* Documents are instances of document types. You can upload many for each
but each document can only be of one type.
* Metadata is just user data that yo
The db.sqlite3 file is created and used only when using SQLite. Since you
used the docker compose, the database backend being used is PostgreSQL.
Execute: docker ps
You should have two containers. One for the project and another for the
database.
On Sunday, March 11, 2018 at 5:53:17 AM UTC-4,
Hi.
There are database changes between our release and version 2.7.3 of Mayan
upstream. The database changes in our release correspond to unpublished
changes already in Mayan upstream. But, if you migrate your database and
Mayan EDMS version 2.8 doesn't pull all of our changes you could end up
Awesome! Make sure you use Docker named volumes for the data. It is a
current limitation that I hope to correct soon.
On Thursday, March 8, 2018 at 2:45:59 PM UTC-4, Raul wrote:
>
> I was able to get it working by building it by myself with docker-compose.
> Nice jobs guys :)
>
>
> Am Donnerstag,
Try Mayan EDMS NG. Michael has done a lot of work on the API. Adding more
than a lot of new tests and fixing some bugs in the API while keeping it
100% compatible.
On Thursday, November 30, 2017 at 3:01:43 AM UTC-4, Tony Nys wrote:
>
> note that the api documentation is not perfect; especially t
We are keeping the project alive and released a new version based on direct
input and guidance from Roberto. It was released as Mayan EDMS NG 2.8. NG
as in Next Generation. It is a 100% compatible fork. We are working right
now on version 3.0.
On Thursday, November 30, 2017 at 10:44:16 AM UTC-4
I've timed the loading and the fancybox intialization to provide the popup
previews take a good chunk. Been thinking about removing that feature now
that the document are displayed in a list item view instead of a vertical
list view. The Open Paperless fork removed it and works great.
On Wednes
We added this fix to Mayan EDMS NG version 2.8.
On Thursday, December 21, 2017 at 10:19:48 PM UTC-4, littlez...@gmail.com
wrote:
>
> Hi, I had the same issue and fixed it adding a "select all" checkbox at
> the top of the document list.
>
> You can see the screenshot here:
> https://raw.githubu
Mayan keeps the aspect ratio of the original image. I've been exploring
ways to fix this. One is to shrink the image and display white or black
borders. This keeps the aspect ratio intact but if the image is long it
will be rendered very small. The other way is to sacrifice the aspect ratio
and
The problem is Docker. The named volumes initialize in a different way,
Mayan relies on that behavior for writing the initial setting files. I see
the merit in changing that but it requires changing the way Mayan itself
works. For the moment we are trying to keep the major functionality intact
Thanks, I'm trying out Debian as the base image and liking it so far.
On Friday, March 2, 2018 at 9:47:41 AM UTC-4, Mathias Behrle wrote:
>
> * ericr...@gmail.com : " Re: [Mayan EDMS: 2288] Announcing
> Mayan EDMS NG
> version 2.8" (Wed, 28 Feb 2018 17:49:27 -0800 (PST)):
>
> > I managed to g
Haven't worked with version 3 of docker compose files. Sounds interesting,
I'll give it a go.
On Thursday, March 1, 2018 at 7:11:26 PM UTC-4, Michael Price wrote:
>
> I'll leave that up to Eric out resident Docker expert. But if the file
> format is the same I don't see much problem with support
Hi Dave. I'm working on the changes to make Mayan behave like a single page
app. Right now every click causes a complete window refresh. This is the
"old" way of doing web apps. On one hand it is robust and stands the test
of time in term of compatibility on the other hand is slow and only one
The Docker image is available from the Docker Hub at:
https://hub.docker.com/r/mayanedmsng/mayanedmsng/
Every procedure is the same as with the upstream version with the only
change that the repository reference must be mayanedmsng/mayanedmsng
instead of mayanedms/mayanedms.
Once change this i
I managed to get Mayan running using Alpine Linux but the final image size
was almost the same using Ubuntu. There were too many path and
configuration file changes and while Alpine runs well it is not LSB
compliant. I don't think it is a fit for something like as complex as Mayan
and needs to
I'm interested in this feature too. How to better implemented it? Make tags
more intelligent or create a workflow action that tags documents based on a
criteria field.
On Thursday, December 28, 2017 at 8:43:17 PM UTC-4, David Reagan wrote:
>
> Is there a way to automatically tag a document based
27 matches
Mail list logo
