Re: [Mayan EDMS: 1949] Re: Help Understanding the Index's

[David Kornahrens]

I second this  With pictures :)

I just don't get it.  I've tried, but perhaps it is just because I'm new to 
the EDMS environment.  

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2015] Re: Upload wizard question

[David Kornahrens]

I second this request.  Not fully understanding the index feature, cabinets 
is our best way to organize data.

On Friday, August 11, 2017 at 10:56:46 AM UTC-4, LeVon Smoker wrote:
>
> Roberto,
>
> Is there a release target date for the document upload wizard refactor? 
> Specifically, I'm looking for the ability to add cabinets during upload.
>
> In the mean time, what's the best way to hack in cabinets on the upload 
> wizard?
>
> Thanks,
> LeVon Smoker
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1878] Re: Mayan EDMS version 2.5.2 released

[David Kornahrens]

Thanks.  I sent you an email to just complete the quote to get this fixed 
the right way.  Our developer doesn't understand the steps I don't believe.

On Sunday, July 9, 2017 at 2:36:24 PM UTC-4, Roberto Rosario wrote:
>
> Yes, the production.py file is part of the distribution and overwritten on 
> upgrades. Use the local.py for user changes or the environments variables 
> to make persistent changes.
>
> On Sunday, July 9, 2017 at 10:13:16 AM UTC-4, David Kornahrens wrote:
>>
>> Roberto,
>> Will upgrading via the Docker method override the 
>> "/usr/local/lib/python2.7/dist-packages/maya/settings/production.py" file?
>>
>> That is the file we put the custom DJANGO in for the DJANGO-STORAGES to 
>> function.
>>
>> Thanks,
>> David
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1879] Re: Web Form Upload; How-To

[David Kornahrens]

Yes sir.  So I want to create a web-form outside of Mayan EDMS.  Hosted on 
our website, that allows people to upload different things to our EDMS.

Thx,
David



On Sunday, July 9, 2017 at 2:12:12 PM UTC-4, Roberto Rosario wrote:
>
> To rephrase, you want to have an upload form separate from Mayan using 
> something like PHP?
>
> If that's the case you can do it using the REST API from a PHP page.
>
> On Sunday, July 2, 2017 at 7:25:04 PM UTC-4, David Kornahrens wrote:
>>
>> I'm looking to see if anyone has information regarding to creating a web 
>> form source and upload documents accordingly.  We want to put this web 
>> form, using php I suppose, on our intranet to allow employees to upload 
>> directly to the system without uploading. 
>>
>> We have our MFP's (Xerox) setup to receive documents, but I'm wanting to 
>> be able to make it easier for the users.
>>
>> Thx,
>> David
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1863] Re: Mayan EDMS version 2.5.2 released

[David Kornahrens]

Roberto,
Will upgrading via the Docker method override the 
"/usr/local/lib/python2.7/dist-packages/maya/settings/production.py" file?

That is the file we put the custom DJANGO in for the DJANGO-STORAGES to 
function.

Thanks,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1861] Re: Document Cache

[David Kornahrens]

Roberto,
In what method would I use to move the cache?  I think the speed shouldn't 
be too much of a problem, being hosted on S3.  I'm curious how the cache 
works though.  Does it only store "X" amount of data in the cache?  Or does 
it basically keep everything in there forever?  It's about the same size as 
my object storage folder, so I'm not seeing what the cap would be for the 
cache folder.

Digital Ocean droplets aren't that large and until they roll out their 
object storage, it's really not going to work, so I'll need to put 
everything on S3 using the DJANGO-STORAGES option to keep our Mayan up and 
running and keep adding files.

Thanks,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1860] Re: Recent Documents

[David Kornahrens]

Thanks Roberto,
Just so I can understand the Workflow idea and the settings behind it, 
could you let me know the steps needed to review all recent docs?

I just created a new Workflow, and I see options for States, Transitions, 
Document Types, Edit, and ACL's.  

Just not really sure where to go from here to accomplish my goal.  I think 
once I understand how this is supposed to look, I can figure it out.

Thanks!

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1905] Re: Mayan EDMS 2.6 released.

[David Kornahrens]

Thank you Roberto!  You are pushing out updates quickly!  Was then Cache 
Size addressed in this update?



On Tuesday, July 18, 2017 at 5:54:34 PM UTC-4, Roberto Rosario wrote:
>
> Mayan EDMS version 2.6 released, Docker image updated as well.
>
> Feature highlights:
>
> *Email*
>
>
>- Support for emailing documents or document links to multiple 
>recipients.
>
>
>
> 
>
>
>
> *Visual changes*
>
>
>- Full width layout. 
>
>
>
> 
>
>
>
>- New list item view.
>
>
>
> 
>
>
> *Search*
>
>
>- Support for searching users and groups via the API. 
>
>
> *Logging*
>
>
>- The logging configuration was improved to create a log for critical 
>errors when running on production mode. The default location for this log 
>file is: /mayan/error.log. This path can be changed with the 
>COMMON_PRODUCTION_ERROR_LOG_PATH setting. This log file will capture 
>application errors and request exceptions.
>
>
> *Cabinets*
>
>
>- The access control for cabinets has been fixed in some regards and 
>improved in others. The permission to add and remove documents can now be 
>applied to individual root cabinets instead of globally for a role. Also, 
>the permission to add or remove documents from cabinets must also now be 
>granted to a document or document type. In other words, to add a document 
>to a cabinet, the user’s role must have the permission to add documents to 
>cabinet, for the cabinet to recieve the document and for the document 
> about 
>to be added.
>
>
> *New permission*
>
>
>- The patch to add a permission to view a document’s version list was 
>backported from the development branch to make it accesible now. Like 
>cabinets, the tag access control now works on two levels. Now to attach a 
>tag to a document, the permission to attach tags must be granted to the 
> tag 
>to attach and to the document that will receive the tag.
>
>
> *ACL changes*
>
>
>- The document type permissions namespace was renamed from “Document 
>setup” to “Document types” for clarity. Along with that change, support 
> was 
>added for granting the document type edit, document type delete, and 
>document type view permissions to individual document type instances 
>instead of just globally.
>
>
> *Testing*
>
>
>- The documents app view tests now test for view access and not just 
>permission. Testing against access is more robust and also tests for 
>permissions implicitly.
>
>
> *Other Changes*
>
>
>- Fix HTML mark up in window title. GitLab #397.
>- Sort setting by namespace label and by global name second.
>- Sort indexes by label.
>- Switch the order of the DEFAULT_AUTHENTICATION_CLASSES of DRF. 
>GitLab #400.
>- Improve code to unbind menu entries.
>- Increase the size of the mailing profile label field to 128 
>characters.
>
>
> For the complete list of changes and a full explanation of the changes 
> mentioned
> above, visit the release notes: 
> http://mayan.readthedocs.io/en/v2.6/releases/2.6.html
>
> Many of the features added in this release were requested by support 
> subscribers.
> Prioritized feature requests, another benefit of the support plans: 
> http://www.mayan-edms.com/providers/
>
> Docker image README https://hub.docker.com/r/mayanedms/mayanedms/
>
> Facebook page: https://www.facebook.com/MayanEDMS/
> Mayan App store: http://www.mayan-edms.com/store/
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1933] Help Understanding the Index's

[David Kornahrens]

Roberto & community,
I'm having issues after using Myan for about a month, understanding the 
indexes and using them correctly.  

Can someone point me in the right direction?  Possibly step by step 
understanding of what it does and how it should help us.

Thank you,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1882] Re: Disable Thumbnails in list view

[David Kornahrens]

Or, disable the thumbnail view for specific users.  We may not want some 
interns and such seeing all the data within the portal.

On Tuesday, July 11, 2017 at 5:26:05 PM UTC-4, Lutz Findeisen wrote:
>
> Hi Roberto,
> just seen your answer today - wanted to say thanks though. Works like a 
> charm, maybe you might want to think about exposing the thumbnails 
> disabling via a setting.
>
> cheers,
> Lutz
>
> Am Mittwoch, 19. April 2017 17:19:26 UTC+2 schrieb Roberto Rosario:
>>
>> There is no exposed way to disabled thumbnail display but it can be 
>> disabled manually by removing or remarking the following lines in 
>> mayan/apps/documents/apps.py
>>
>> Thumbnails for documents:
>>
>>
>>  SourceColumn(
>> source=Document, label=_('Thumbnail'),
>> func=lambda context: document_thumbnail(
>> context['object'], gallery_name='documents:document_list',
>> size=setting_thumbnail_size.value,
>> title=getattr(context['object'], 'label', None),
>> )
>> )
>>
>> The thumbnails for the deleted documents.
>>
>>
>> SourceColumn(
>> source=DeletedDocument, label=_('Thumbnail'),
>> func=lambda context: document_thumbnail(
>> context['object'],
>> gallery_name='documents:delete_document_list',
>> size=setting_thumbnail_size.value,
>> title=getattr(context['object'], 'label', None),
>> disable_title_link=True
>> )
>> )
>>
>>
>> The purpose of the SourceColumn class is to show a table column with a 
>> specific `label` and the result of a function (func) when the presence of a 
>> `source` class instance is detected in a table.
>>
>> On Tuesday, April 4, 2017 at 11:02:03 AM UTC-4, Lutz Findeisen wrote:
>>>
>>> Hi,
>>> I'm using Mayan on a Raspberry PI, due to the limited performance of the 
>>> PI the loading of the document list page takes quite long, particularly due 
>>> to the thumbnail generation. Is there a way to disable/hide thumbnails on 
>>> the documents list page maybe via a setting?
>>>
>>> Thanks in advance,
>>> Lutz
>>>
>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1824] SANE Scanner

[David Kornahrens]

I see the new addition to using a SANE Scanner.

Where will it put these files once we get this setup?  On the other 
sources, we select a Document Type, even though I think we should just have 
a staging folder until someone adds tags or document types to it.

Thx,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1825] Digital Ocean Volumes

[David Kornahrens]

Roberto --
We are looking at adding a DO volume to our Droplet as we are running out 
of storage.

How would we go about adding a volume and making the EDMS system utilize 
that volume for storage?

Thank you,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1834] Re: Digital Ocean Volumes

[David Kornahrens]

We use the Docker version.  I just sent you an email about moving over our 
storage to S3 and setting up on our current Docker container.

Thx,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1845] Re: Digital Ocean Volumes

[David Kornahrens]

Hey Roberto,
I wrote you back, but was having difficulties with our O365 auto encrypting 
then emails.  DIdn't like some of the terminology we used, I guess.



On Saturday, July 1, 2017 at 2:17:26 PM UTC-4, Roberto Rosario wrote:
>
> Hi David,
>
> sent you an email regarding this.
>
> On Wednesday, June 28, 2017 at 8:48:28 PM UTC-4, David Kornahrens wrote:
>>
>> We use the Docker version.  I just sent you an email about moving over 
>> our storage to S3 and setting up on our current Docker container.
>>
>> Thx,
>> David
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1846] Web Form Upload; How-To

[David Kornahrens]

I'm looking to see if anyone has information regarding to creating a web 
form source and upload documents accordingly.  We want to put this web 
form, using php I suppose, on our intranet to allow employees to upload 
directly to the system without uploading. 

We have our MFP's (Xerox) setup to receive documents, but I'm wanting to be 
able to make it easier for the users.

Thx,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1847] Document Cache

[David Kornahrens]

So, I have moved over my main directory to S3.  After confirming it was 
working fine, I deleted the "document_storage" contents.  

However, I still see 11gb of data in the "./mayan_data/_data/document_cache" 
location.

Is this something that can also be moved to S3?  My point of the move was 
to lower data consumption on my server and move everything to S3.  How much 
data is stored as page cache in this folder?

Thx,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1822] Re: Mayan EDMS version 2.4 released

[David Kornahrens]

Just updated to the latest Docker image, 2.4.  

After reviewing the changes from this release as well as 2.3, I'm not 
seeing any update that would help with the server load, but 2.4 seems to be 
running a lot better for us.

We have Mayan EDMS deployed on a Digital Ocean Droplet, 4GB RAM / 2vCPU. 
 2.2 was pegging out CPU's sometimes at 2.10 and up.  RAM usually was 
decent.

Now we are running around 1vCPU usage.

Good work!!!

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1858] Recent Documents

[David Kornahrens]

I'm having a hard time understanding the recent document section.

I'm the master user, so is there a setting where I can change "recent 
documents" to display truly the recent documents for all users?

I would like this as a review of what information is loaded into the system.

Thanks,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1952] Re: Database is locked

[David Kornahrens]

I would start by restarting the instance.  Did you deploy through Docker?

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2035] Re: Mayan EDMS's immediate future

[David Kornahrens]

Roberto,
I have sent you some emails in regards to also helping out with funding for 
the project.  I have teamed up with a few people here locally and we are 
interested in doing what we need to do to encourage and help the 
development of your system.

Thanks,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 1816] Where do I adjust the size limit on uploads

[David Kornahrens]

Robert,
I cannot find where the Docker location is for the php.ini file.  We run 
NGINX and are hosted on Digital Ocean.  Any ideas?

Thanks,
David

On Wednesday, April 19, 2017 at 11:13:50 AM UTC-4, Roberto Rosario wrote:
>
> This is the NGINX configuration file used in the Mayan Docker image. The 
> max file size is set to 50 megabytes and the max upload wait time is 30 
> seconds. Both can be increased by any amount.
>
> server {
> listen 80;
>
> location / {
> include uwsgi_params;
> uwsgi_pass unix:/run/mayan.sock;
>
> client_max_body_size 50M;  # Increase if your plan to upload 
> bigger documents
> proxy_read_timeout 30s;  # Increase if your document uploads take 
> more than 30 seconds
> }
>
> location /static {
> alias /usr/local/lib/python2.7/dist-packages/mayan/media/static;
> expires 1h;
> }
>
> location /favicon.ico {
> alias 
> /usr/local/lib/python2.7/dist-packages/mayan/media/static/appearance/images/favicon.ico;
> expires 1h;
> }
> }
>
>
> On Friday, March 24, 2017 at 5:26:02 AM UTC-4, Jesaja Everling wrote:
>>
>> You might also have to adjust the corresponding setting in your wsgi 
>> (e.g. uwsgi) config.
>>
>>
>> On Fri, Mar 24, 2017 at 9:35 AM, Mathias Behrle > > wrote:
>>
>>> * Mark Phillips: " [Mayan EDMS: 1557] Where do I adjust the size limit on
>>>   uploads" (Thu, 23 Mar 2017 13:05:02 -0700):
>>>
>>> > I tried, as the default admin user, to upload a tiff file as a new
>>> > document. I had a document type of Picture defined. I got an error 
>>> that the
>>> > image is too big. Please see the attached screen shot, as the error is 
>>> a
>>> > little weird in its presentation.
>>> >
>>> > Where do I change the size limit on file uploads?
>>> >
>>> > Thanks,
>>> >
>>> > Mark
>>> >
>>>
>>> Since you seem to run behind nginx consider increasing
>>>
>>> client_max_body_size
>>>
>>> in your nginx configuration.
>>>
>>> HTH,
>>> Mathias
>>>
>>> --
>>>
>>> Mathias Behrle
>>> PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
>>> AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google 
>>> Groups "Mayan EDMS" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to mayan-edms+...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 1817] Re: Document uploaded, shown in server but not shown on website

[David Kornahrens]

We are running a 4GB / 2vCPU plan from DO.  The 2GB plan wasn't cutting it 
for some uploads, so we had to increase the size.

Thanks,
David

On Tuesday, June 20, 2017 at 12:56:41 AM UTC-4, Lan Nguyen wrote:
>
> Hi Jeseja,
>
> No worry my friend. I was able to fully run Mayan EDMS through Docker by 
> simply upgrade my Droplet by two tier.
> From this incident, I assume that my initial Droplet did not have enough 
> computing capacity to handle the app itself thus lead to front end error. 
> However, I am more than happy to try out some solution you are willing to 
> provide in order to solve this issue for lower tier of DigitalOcean's 
> Droplet.
>
> Best Regards,
> Lan Nguyen
>
> On Monday, June 19, 2017 at 7:34:42 AM UTC-5, Jesaja Everling wrote:
>>
>> Hi Lan,
>>
>> sorry for the late reply. How are you running the setup? Using Docker or 
>> manual install?
>>
>> On Tue, Jun 13, 2017 at 5:07 PM, Lan Nguyen <gbnserv...@gmail.com> wrote:
>>
>>> Hi Jesaja,
>>>
>>> Thank you for your response. Can you instruct me on how to check if the 
>>> Celery worker is working?
>>>
>>> Regards,
>>> Lan Nguyen
>>>
>>> On Tuesday, June 13, 2017 at 10:03:13 AM UTC-5, Jesaja Everling wrote:
>>>>
>>>> The problem might also be due to the Celery worker that processes 
>>>> uploaded files. Make sure that worker is running, without it the documents 
>>>> will not be shown in the frontend.
>>>>
>>>> Best Regards,
>>>>
>>>> Jesaja Everling
>>>>
>>>>
>>>> On Jun 13, 2017 4:56 PM, "David Kornahrens" <david.ko...@gmail.com> 
>>>> wrote:
>>>>
>>>>> Check the document type you uploaded to and see if any documents are 
>>>>> showing in there.
>>>>>
>>>>> -- 
>>>>>
>>>>> --- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "Mayan EDMS" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to mayan-edms+...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> -- 
>>>
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Mayan EDMS" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to mayan-edms+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1747] Re: Mayan EDMS Docker image updates

[David Kornahrens]

Hello Roberto.  We are new to your project, but have spun up a Docker image 
of Myan.  We are attempting to run this in a production environment.

Few questions here:

-Even though we are on the latest right now (we believe), what is the 
command to update the docker image without losing our data?
-Is this ready for primetime?

Thanks,
David

On Thursday, May 18, 2017 at 2:02:21 AM UTC-4, Roberto Rosario wrote:
>
> As part of the round of improvements to the next version of the Docker 
> image, a production stack using Docker compose has been included.
> This stack will launch 4 containers:
>
> - A database container using Postgres
> - A Celery broker container using RabbitMQ
> - A Celery results container using Redis
> - A Mayan EDMS container that uses the above service containers
>
> If you have experience building Docker images and using Docker compose, 
> please help test this stack on your hardware.
>
> Other improvements added:
>
> Allowing changing the database backend using the environment variables:
>
> - MAYAN_DATABASE_DRIVER, default: None
> - MAYAN_DATABASE_NAME, default : 'mayan'
> - MAYAN_DATABASE_USER, default: 'mayan'
> - MAYAN_DATABASE_PASSWORD, default: ''
> - MAYAN_DATABASE_HOST, default: None
> - MAYAN_DATABASE_PORT, default: None
>
> The Celery broker and Celery results backend can also be changed using the 
> environment variables:
>
> - MAYAN_BROKER_URL, default: 'redis://127.0.0.1:6379/0'
> - MAYAN_CELERY_RESULT_BACKEND, default: 'redis://127.0.0.1:6379/0'
>
> If the MAYAN_BROKER_URL and MAYAN_CELERY_RESULT_BACKEND are specified, the 
> built in
> REDIS server is disabled in favor of the external Celery result backend.
>
> A new dedicated image converter worker was added to supervisor. This 
> allows for previews to be generated
> and displayed even during high loads (such as when doing OCR on large 
> documents).
>
> The installation process was simplified and reduced to a single step:
>
> docker run -d --name mayan-edms --restart=always -p 80:80 -v 
> mayan_data:/var/lib/mayan mayanedms/next
>
> Gone is the initialization step. The image now keeps track of the state of 
> the data in the volume to determine whether to initialize and run 
> or upgrade and run when launched.
>
> The volume setup was also simplified and reduced to a single volume. The 
> settings and document storage files now co-exists in a single tree
> inside a sngle volume.
>
> The NGINX web server limits for uploading files were increased to a max 
> file size of 500 MB and the upload timeout was increased to
>  600 seconds (10 minutes). These are web server settings and don't affect 
> the overall memory usage of the container.
>
> If an external database is used, database connection keepalive is 
> automatically enabled with a default of 60 seconds.
> This Django settings allows reusing database connections instead of 
> closing and opening database connection for each
> HTTP request/response cycle. 
>
> Finally a health check was added to allow other Docker images like reverse 
> proxies or load balancers to know when the Mayan EDMS container
> is ready for traffic.
>
> To follow and test these improvements follow the 'development' branch of 
> the Docker repository at: 
> https://gitlab.com/mayan-edms/mayan-edms-docker/tree/development 
>
> Please help test these changes to move them to the stable master branch as 
> soon as possible.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1747] Re: Paid support

[David Kornahrens]

Was this ever resolved?  I'm thinking about getting a support account, but 
want to make sure it's actually being utilized and available.

On Wednesday, May 10, 2017 at 3:57:14 PM UTC-4, Cédric MARCOUX wrote:
>
> Hello,
>
> i have paid the support with paypal but not receive any further 
> instruction.
> I have sent a mail to i...@mayan-edms.com but not receive any answer.
>
> How can I join the paid support? Thanks for your help
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1754] Multifunctional Printer Config (Xerox)

[David Kornahrens]

I have seen in the support documents that Multi-functional printers are 
accepted as a source for gathering documents.  

We have EDMS deployed in the cloud, how would we go about setting up a MF 
printer to serve our needs?

Thx,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1753] Re: Mayan EDMS Docker image updates

[David Kornahrens]

Roberto - Is there a method in your program to verify we are on the latest 
product?  And how do we check this via command line or some other interface?

Thx,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1751] Re: Mayan EDMS Docker image updates

[David Kornahrens]

Thank you Roberto.  We have spun up a Docker image with your product and 
have been building out our instance to fit our needs.  We are impressed 
with the product so far.  I'm sure I'll have some other questions.  Once we 
get everything up and running, we plan to purchase a support contract with 
you for business use as we will most likely need some assistance.

On Thursday, May 18, 2017 at 2:02:21 AM UTC-4, Roberto Rosario wrote:
>
> As part of the round of improvements to the next version of the Docker 
> image, a production stack using Docker compose has been included.
> This stack will launch 4 containers:
>
> - A database container using Postgres
> - A Celery broker container using RabbitMQ
> - A Celery results container using Redis
> - A Mayan EDMS container that uses the above service containers
>
> If you have experience building Docker images and using Docker compose, 
> please help test this stack on your hardware.
>
> Other improvements added:
>
> Allowing changing the database backend using the environment variables:
>
> - MAYAN_DATABASE_DRIVER, default: None
> - MAYAN_DATABASE_NAME, default : 'mayan'
> - MAYAN_DATABASE_USER, default: 'mayan'
> - MAYAN_DATABASE_PASSWORD, default: ''
> - MAYAN_DATABASE_HOST, default: None
> - MAYAN_DATABASE_PORT, default: None
>
> The Celery broker and Celery results backend can also be changed using the 
> environment variables:
>
> - MAYAN_BROKER_URL, default: 'redis://127.0.0.1:6379/0'
> - MAYAN_CELERY_RESULT_BACKEND, default: 'redis://127.0.0.1:6379/0'
>
> If the MAYAN_BROKER_URL and MAYAN_CELERY_RESULT_BACKEND are specified, the 
> built in
> REDIS server is disabled in favor of the external Celery result backend.
>
> A new dedicated image converter worker was added to supervisor. This 
> allows for previews to be generated
> and displayed even during high loads (such as when doing OCR on large 
> documents).
>
> The installation process was simplified and reduced to a single step:
>
> docker run -d --name mayan-edms --restart=always -p 80:80 -v 
> mayan_data:/var/lib/mayan mayanedms/next
>
> Gone is the initialization step. The image now keeps track of the state of 
> the data in the volume to determine whether to initialize and run 
> or upgrade and run when launched.
>
> The volume setup was also simplified and reduced to a single volume. The 
> settings and document storage files now co-exists in a single tree
> inside a sngle volume.
>
> The NGINX web server limits for uploading files were increased to a max 
> file size of 500 MB and the upload timeout was increased to
>  600 seconds (10 minutes). These are web server settings and don't affect 
> the overall memory usage of the container.
>
> If an external database is used, database connection keepalive is 
> automatically enabled with a default of 60 seconds.
> This Django settings allows reusing database connections instead of 
> closing and opening database connection for each
> HTTP request/response cycle. 
>
> Finally a health check was added to allow other Docker images like reverse 
> proxies or load balancers to know when the Mayan EDMS container
> is ready for traffic.
>
> To follow and test these improvements follow the 'development' branch of 
> the Docker repository at: 
> https://gitlab.com/mayan-edms/mayan-edms-docker/tree/development 
>
> Please help test these changes to move them to the stable master branch as 
> soon as possible.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1755] Re: Mayan EDMS Docker image updates

[David Kornahrens]

Outstanding.  If the commit hasn't been packaged yet, me running the 
command will not do anything correct?

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1757] Re: Mayan EDMS Docker image updates

[David Kornahrens]

One more question Roberto -- Because I used the Docker deploy method, do I 
still update the same way "pip search mayan-edms" ?

THank you,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1763] Upgrading Method with Docker

[David Kornahrens]

Looking to see if someone can help with the update process in the right 
order for Docker.  

I want to make sure I'm not losing any data during the upgrade.

Thank you,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1769] Re: Upgrading Method with Docker

[David Kornahrens]

Thanks.  So if I follow that tutorial, that will not remove the volumes 
then?

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1775] Cabinet Permissions

[David Kornahrens]

I'm having a slight problem understanding the workflow in terms of 
restricting data.

So I have a user "Test" that I have assigned to "Group A".  

"Group A" has been granted a role of "standard users" with permissions to 
view cabinets (but only because I want them to see Cabinet "A" and see the 
structure.  Then I selected to allow that role to "view documents".

However, it appears they can now see each cabinet and all the documents 
within.

What am I missing here?  How can I get Cabinet A to only be viewable to 
"Cabinet A".   Cabinet B to only be viewable by Cabinet B and so forth?

Of course, Admin's will be able to view across cabinets.  If this is not a 
possibility, this extremely limits our ability to utilize this platform.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1777] Re: Search for document content not OCRed within Mayan

[David Kornahrens]

Makes sense to me.  We have a few documents that weren't scanned by OCR, 
but I do not see anything in the logs to represent that.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1770] After 5 Documents; Not able to Upload Files

[David Kornahrens]

We have an intern working on building out our EDMS platform.  

So, we have setup everything and are now uploading files.  We are able to 
upload a few files, without issue.  However, now we are having an issue 
where we are not getting any warning (and also get a successful check mark 
upon an upload).  However, it's not found in the database and doesn't 
appear in the "recent" uploads.  

Any idea?  We have a 1095 day retention policy setup on this particular 
Document Type.

THanks,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1771] Re: After 5 Documents; Not able to Upload Files

[David Kornahrens]

We are able to upload documents on other Document Types, just having an 
issue with this one.

On Monday, June 5, 2017 at 3:48:22 PM UTC-4, David Kornahrens wrote:
>
> We have an intern working on building out our EDMS platform.  
>
> So, we have setup everything and are now uploading files.  We are able to 
> upload a few files, without issue.  However, now we are having an issue 
> where we are not getting any warning (and also get a successful check mark 
> upon an upload).  However, it's not found in the database and doesn't 
> appear in the "recent" uploads.  
>
> Any idea?  We have a 1095 day retention policy setup on this particular 
> Document Type.
>
> THanks,
> David
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1772] Re: After 5 Documents; Not able to Upload Files

[David Kornahrens]

Weird.  I took a snapshot of the droplet, just in case something went 
wrong.  I checked for an upgrade using the Docker upgrade steps.  No dice. 
 Then, I updated the Droplet to a 2GB plan, and it appears that has fixed 
the problem.

However, I'm getting some weird things going on.  When I visit "Recent 
Documents" it's showing me a total of 6 documents.  However, I have 
uploaded 9 documents in just a few days that should be appearing. 
 Secondly, I uploaded three files back to back to back.  Two of them are 
appearing in the "Recent" list, then other is not.  When I navigate to the 
correct location within the Cabinet, I can find all three files.

Lastly,  these PDF's are loaded in, but they are sideways (landscape).  I 
noticed that the Mayan EDMS engine cannot read the text within those PDF's 
like is has on other PDF's I have loaded.   Is there a method to get it to 
research the text?  Or something else I can do?

Thanks,
David



On Monday, June 5, 2017 at 3:48:22 PM UTC-4, David Kornahrens wrote:
>
> We have an intern working on building out our EDMS platform.  
>
> So, we have setup everything and are now uploading files.  We are able to 
> upload a few files, without issue.  However, now we are having an issue 
> where we are not getting any warning (and also get a successful check mark 
> upon an upload).  However, it's not found in the database and doesn't 
> appear in the "recent" uploads.  
>
> Any idea?  We have a 1095 day retention policy setup on this particular 
> Document Type.
>
> THanks,
> David
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2129] Re: Transformations Auto Rotate (bug)

[David Kornahrens]

Thanks for the response.  We are using the standard Xerox "email to" to 
merge the PDF's.  If we put 10 pages into the document feeder for "1" 
document, it merges all of them into one PDF when sending to our email as 
our source.

Thx,
DAvid

On Sunday, September 3, 2017 at 5:18:55 AM UTC-4, Roberto Rosario wrote:
>
> I ran the file through the command `pdfinfo` and it reports that the pages 
> are rotate by 270 degrees. Mayan is adding a 90 degrees rotation 
> transformation to compensate. However when I view the PDF with xpdf and 
> evince or extract the PDF pages by hand using pdftoppm or ghoscript, they 
> are not rotated, they come out straight (portrait). I tried the same with 
> the PDF you included in issue 387 (
> https://gitlab.com/mayan-edms/mayan-edms/issues/387) which also reports a 
> rotation of 270 degrees. With this document, viewed or extracted pages have 
> indeed a rotation of 270 degrees and show in landscape format. 
>
> I'm uncertain if the PDF metadata reporting a 270 degrees rotation in the 
> latest PDF (AUGUST 30 2017 2017-01042.pdf) is incorrect or that the 
> extraction and viewers tools are all compensating automatically. Both PDF 
> seem to be produced by the same equipment: Xerox WorkCentre 7845 but the 
> first document (2016_Pumper_Test_Records.pdf) appears to be single pages 
> that were later merged using a PDF merge tool.
>
> More tests using different tools is required to determine which situation 
> is the correct one: 1) the rotation information is wrong, 2) the tools all 
> compensate for rotation when extracting images or viewing and it is not 
> necessary for Mayan to add a transformation, 3) the merge tool used to 
> compose the first PDF document scrambled the rotation metadata or rotated 
> the pages without updating the rotation metadata.
>
> On Friday, September 1, 2017 at 8:21:55 AM UTC-4, David Kornahrens wrote:
>>
>> Roberto,
>> Here is one of the documents.  I've noticed they are rotating coming from 
>> the source (we use printer to IMAP email to pick up the files).
>>
>> Thanks,
>> David
>>
>> On Tuesday, August 29, 2017 at 12:05:32 PM UTC-4, David Kornahrens wrote:
>>>
>>> We are having documents self-rotate themselves 90 degrees and I'm not 
>>> sure why.  I'm having to manually remove the transformations from each 
>>> document and then resubmit them for OCR.
>>>
>>> Any ideas?
>>>
>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2160] Re: searching 'All Documents'

[David Kornahrens]

Can you let me know what code you are using for transformations?  I'm 
having a difficulty with one of my Xerox's and Mayan auto rotating.

Thx,
David

On Thursday, October 5, 2017 at 4:43:23 PM UTC-4, Douglas Van Es wrote:
>
> hello all. 
>
> i have a quick question: 
>
> we are scanning invoices here. the user walks up to our scanner and types 
> in the number of the invoice as a filename. the sacanner dumps a pdf into 
> a watch folder on our fileserver. i have a transformation set up to 
> rotate 270 degress because our users scan in landscape...this is all 
> working perfectly. 
>
> is there a way to search 'All Documents' for a given file? i can't seem 
> to find this and feel that i must be missing something... 
>
> i searched through the posts on this group, and see references to a 
> search function in past versions. is it not present? 
>
> tia 
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2147] Roberto; Hope all is well

[David Kornahrens]

Roberto,
Just wanted to let you know that some of us in the community are thinking 
about you and hoping all is well for you and your family.

Puerto Rico will build back and stronger than ever.  You have my thoughts 
and prayers.

-David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2045] Transformations Auto Rotate (bug)

[David Kornahrens]

We are having documents self-rotate themselves 90 degrees and I'm not sure 
why.  I'm having to manually remove the transformations from each document 
and then resubmit them for OCR.

Any ideas?

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2198] Document Orientation

[David Kornahrens]

When users are uploading documents to Mayan directly via it's upload 
interface, the documents are rotated 90 clockwise.  

Any idea where to change that or fix whatever it is causing it?

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2193] Re: Document Cache

[David Kornahrens]

Robert,
What method would I need to use to limit the cache?  Also, what can I do to 
flush the cache that is currently built up?  We store all files on S3, but 
our disk is still growing.

THanks,
David

On Sunday, July 9, 2017 at 2:41:34 PM UTC-4, Roberto Rosario wrote:
>
> The cache can be moved to S3 with the same process used to move the 
> document storage to S3.
> In version 2.5.2 support was added to disable the cache, partially or 
> completely.
> Limiting the cache to a certain amount of space is a good idea, and a good 
> solution without having to migrate the cache to S3. I'll add an issue to 
> track this.
>
>  
>
> On Saturday, July 8, 2017 at 10:09:10 AM UTC-4, David Kornahrens wrote:
>>
>> Roberto,
>> In what method would I use to move the cache?  I think the speed 
>> shouldn't be too much of a problem, being hosted on S3.  I'm curious how 
>> the cache works though.  Does it only store "X" amount of data in the 
>> cache?  Or does it basically keep everything in there forever?  It's about 
>> the same size as my object storage folder, so I'm not seeing what the cap 
>> would be for the cache folder.
>>
>> Digital Ocean droplets aren't that large and until they roll out their 
>> object storage, it's really not going to work, so I'll need to put 
>> everything on S3 using the DJANGO-STORAGES option to keep our Mayan up and 
>> running and keep adding files.
>>
>> Thanks,
>> David
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2194] Cache - Large Amount of Space

[David Kornahrens]

I just noticed that my DO droplet was getting low on HD space.  I have 
offloaded all files to S3, so I was curious about what would cause the 
problem.

Apparently the cache is nearly 25GB of data.  This is CRAZY.

Does anyone know how to limit the cache capacity?  I saw somewhere that it 
was a possibility but I'm not even sure where to begin with it.

-David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2443] Re: Mayan EDMS NG merge progress

[David Kornahrens]

Touche' Glad to have you back Roberto!

On Thursday, April 5, 2018 at 5:27:18 PM UTC-4, Raul wrote:
>
> Amazing. Good to have you back :)
> Thanks a lot
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2442] Re: Mayan EDMS version 3.0 beta 1 available for testing

[David Kornahrens]

Hello Roberto --
Glad to see you back around.

I'm interested in testing out too.  Could you create a Docker upgrade for 
this, as that is how I'm deployed with Django Storages for offloading files.

Thanks,
David



On Tuesday, April 10, 2018 at 9:21:03 PM UTC-4, Roberto Rosario wrote:
>
> This version is meant for users experienced with Mayan EDMS. Please do not 
> in production. The purpose of this release is get feedback on all the 
> changes and testing and bugs reporting. If want to test against real data, 
> please make a separate copy of your documents and database first and use 
> this copy for testing.
>
> Almost all the changes of Mayan EDMS NG 2.8 and Mayan EDMS NG 3.0 have 
> been merged.
>
> The release notes summary is as follows:
>
>
>- Turning Mayan EDMS into a single page app. Views are rendered using 
>partial templates. On the first render a root template containing the 
>menus, JavaScript and stying is sent to the browser. On subsequent usage 
>only the area below the menu is refreshed. This results is a big speed 
>boost and much less bandwidth consumption.
>- Project moved to Django 1.11.
>- Event notification. It is possible to subscribe to an event type for 
>the entire system or to the event type of a specific document. If any of 
>these subscribed events occur an entry will be added to the notification 
>menu entry. The default for this menu entry is to display a bell icon and 
> a 
>badge with the number of unread notifications.
>- All the Python dependencies have been upgraded to their latest 
>version.
>- The logic for searching documents is now different. Before, all the 
>documents that matched at least one of the search terms were returned. Now 
>only the documents that match all the terms are returned. This is in 
>essence an "AND" style logic. To allow the previous behavior, the "OR" 
>search syntax was added. The syntax must be added in uppercase and between 
>the optional terms.
>- Normally the resolution for the display modes of documents was 
>specified as a string containing the width and height concatenated with 
> the 
>character 'x'. The display resolution settings have been separated into 
>distinctive width and height settings. Instead of 
> DOCUMENTS_THUMBNAIL_SIZE, 
>the settings are now DOCUMENTS_THUMBNAIL_WIDTH and 
>DOCUMENTS_THUMBNAIL_HEIGHT. The same applies to the preview, display and 
>print resolutions.
>- The upload wizard now features dynamic steps. The steps are defined 
>by a new class called WizardStep. This allows integrators to customize the 
>upload wizard to add their own steps without having to modify the core 
>code. This change also add the capability of disabling existing wizard 
>steps form third party apps without having to make core code modifications.
>- A new default step was added to the upload wizard to specify the 
>cabinets of new documents.
>- The code that detect the automatic orientation of PDF has been 
>disabled by default. It can be enabled via the 
>DOCUMENTS_FIX_ORIENTATION=True setting.
>- A new proposal system has been added via the Mayan EDMS Request for 
>Comment (or MERC for short) documents. The first two MERCs have been 
>approved. MERC-1 which documents the process itself and MERC-2 which 
>documents how API tests are to be written. Other MERCs are in review 
>process.
>- If the duplicates of a document were deleted the original document 
>would still show up in the duplicated document list with a duplicate count 
>of 0. This has been fixed.
>- Support was added to pass arguments to the storage drivers. This 
>removes the need to subclass a storage driver to change its behavior. This 
>also means that passing global variables via the  local.py file to use S3 
>style object storages is no longer required. These storage drivers can be 
>configure by passing their arguments in the new 
>DOCUMENTS_STORAGE_BACKEND_ARGUMENTS as a YAML string.
>- If is possible to list only the system events executed by one user. 
>This can be accomplished via the user list view in the setup menu. Or by 
>clicking on the user name of the event list view.
>- The checkbox behavior in all the views that display a list items has 
>been improved. A "check all" checkbox was added that will auto select all 
>items. The submit button from dropdown list of actions was removed. 
> Instead 
>the action of selecting an item from the action dropdown will trigger the 
>action. The checkbox also allow block selection. Clicking on the checkbox 
>of the first item, later on the checkbox of the fifth item while holding 
>down the shift key will cause the checkboxes of items 1 to 5 to be 
>selected. The same applies to deselection.
>- A JavaScript library manager was added. This means that third party 
>

[Mayan EDMS: 2467] Re: Version 3.0 beta 2 out

[David Kornahrens]

Hey Roberto --
Was this error for new installs?  Will we be fine to upgrade from an 
existing installation?

Thanks,
David

On Friday, May 11, 2018 at 3:18:39 PM UTC-4, Roberto Rosario wrote:
>
> The Python package will also be released too. The update is to allow us to 
> release Docker images faster too but those won't substitute the Python 
> package. 
>
> Thank you for the feedback and supporting the project.
>
> On Friday, May 11, 2018 at 11:05:51 AM UTC-4, Victor Zele wrote:
>>
>> Will there still be a standard PIP install method for these packages or 
>> should I figure out how to change my installation from PIP to docker?
>>
>> thanks for the hard work!
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2331] Re: Docker image for Mayan EDMS NG available

[David Kornahrens]

Hey Eric,
Nice work.  I just finished looking over some of your commits in the 
gitlab.  We currently are running the latest MayanEDMS and have a rather 
large inventory loaded in.  Couple of questions.

1.  Are we able to upgrade to NG without losing the data?  Anyway to 
migrate the data?  
2.  We have offloading media to S3 using the Django offload method from 
Mayan.
3.  We haven't heard from Roberto in awhile, are you going to be taking 
over the development of Mayan?

Thanks,
David

On Thursday, March 8, 2018 at 7:20:32 PM UTC-5, ericr...@gmail.com wrote:
>
> 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, 8. März 2018 19:09:57 UTC+1 schrieb Raul:
>>>
>>> I just tried to start run that image. However, it stucks in a rebooting 
>>> loop.
>>> Do you know what I can do?
>>> Is the image working?
>>>
>>> Thanks
>>>
>>> Am Donnerstag, 1. März 2018 09:45:37 UTC+1 schrieb ericr...@gmail.com:

 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 image has is that is includes a fourth worker to 
 handle the OCR and parsing queues. This worker is run with the lowest 
 possible process priority (19). Therefore OCR results might take longer 
 than with the upstream image. The advantage is that the OCR will not 
 slowdown the execution of the rest of the program. The total image layers 
 were reduced from 54 to 44. Total image size remained the same 1.32GB and 
 490.8MB compressed (the actual download).

 Other changes according to Docker's best practices were made (pinning 
 installs to a specific version, not running dist-upgrade, etc).

 The repository for this image is here: 
 https://gitlab.com/e.riggs/mayan-edms-docker/commits/master

 I will continue working on getting the size of the image down. I'll 
 also keep trying using other base images instead of Ubuntu and or update 
 to 
 a more recent version of Ubuntu, as time allows.




-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2404] Re: Situation update

[David Kornahrens]

Glad to hear you are doing well, considering.  Look forward to you getting 
100% back on your feet.

On Saturday, March 31, 2018 at 2:41:49 AM UTC-4, Roberto Rosario wrote:
>
> Big thank you to everybody that has reached out, sent first necessity 
> items, and donated. You have made a situation without precedent much more 
> bearable. 
>
> This is the situation at the moment (without going into politics or 
> corruption, that has gone to a whole new level of insanity).
>
> Utilities are mostly working. There are still a several outages per week 
> but in comparison with having no power, it is a much better situation. Now 
> we can purchase groceries knowing the chances of it spoiling are much 
> lower. 
>
> Internet and cell phone service are still spotty. We get 1Mbit of download 
> speed. Using heavy ad filtering and compression browsing experience is 
> tolerable but trying to watch streaming content is painful. The same goes 
> for VOIP and video calls. Remote work takes patience.
>
> Driving around is still an adventure. A lot of traffic lights are still 
> out. Intersections are like a gauntlet. Patience in the streets is low and 
> people are very prone to road rage. Traffic jams last hours. In those 
> situations phone navigation is useless as there are still many connectivity 
> dark zones.
>
> Like most people in the island, my income sources have been gravely 
> affected. Spending now the same amount of time I used to spend on Mayan and 
> my other free projects is a luxury I can't afford. I hope to be able to 
> take some time soon to revise all the work done by the Mayan EDMS NG team 
> and start merging. Since their fork has moved quite a bit ahead of Mayan 
> EDMS, this revision and merge process will be mostly manual. To make the 
> most of the time, I'll focus on bug fixes and outdated version updates 
> (Django, packages, etc), before going into features. From what I've seen so 
> far, they have done a very good job. Their job quality will make mine 
> easier.
>
> This has been the worst natural disaster in generations and one of the 
> worse experiences I've had to go through. But we survived it and that's all 
> that matters. We rebuilt our island. And we will rebuild this, our project.
>
> Thank again to everybody.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2405] Upgrading from 2.7.3 to NG Versions

[David Kornahrens]

Hello community,
We are currently on 2.7.3, deployed through Docker.  I am interested in 
updating to the latest NG version, if it's supported to upgrade through 
Docker.

The only concern, we deployed Django Storages and offload media to Amazon 
S3.  We need to ensure this stays offloaded to S3 and that our documents 
can still be viewed when updated.  We currently have ~5K files.

Is this able to be upgraded via Docker?  Or do we need to wait for official 
support from the Mayan repository?

Thanks,
David

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Mayan EDMS: 2414] Announcing Mayan EDMS NG version 2.8

[David Kornahrens]

Michael - I wrote you to your email i...@papperator.com account.  Not sure 
if it was caught in our filters or not.

On Sunday, April 1, 2018 at 5:22:41 PM UTC-4, Michael Price wrote:
>
> Found these, from the master himself :)
>
> Packaging Django projects for PyPI by Roberto Rosario
> https://www.youtube.com/watch?v=bkeIE90hl3Q
>
> Roberto Rosario - Dockerizing Django projects
> https://www.youtube.com/watch?v=A3zKZmB9l64
>
>
> On Sun, Apr 1, 2018 at 5:07 PM,  wrote:
>
>> 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 
>>> suggestion. I've got my service build working now, and was even able to add 
>>> a new analyzer function (from GIT repo  
>>> https://gitlab.com/startmat/document_analyzer.git) to an extension of 
>>> the docker image. I'd rather see a focus on cleanup and new features, 
>>> rather than on my obscure docker needs.
>>>
>>> On Tue, Mar 6, 2018 at 5:22 AM,  wrote:
>>>
 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 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 run reliably in business settings. Alpine was a bit 
> faster but 
> > is missing too many things like language files and fonts (our multi 
> > language Office test document doesn't render using Alpine). There 
> are 
> > problems with Ubuntu too. Ubuntu 16.04, the recommended version for 
> Mayan, 
> > is rather old and missing a recent kernel. Moving to a newer version 
> breaks 
> > too many things. Ubuntu is not careful when it comes to backwards 
> > compatibility. RedHat, Fedora and CentOS were a disaster. Many basic 
> > libraries are missing and the official recommendation is to use 
> third party 
> > repositories. No thanks. I'm going to try Debian next, which is very 
> secure 
> > but also very stable in terms of release continuity (as opposed to 
> Ubuntu). 
>
> JFTR if size matters there are also the *-slim flavors of Debian 
> images 
> removing some files usually not needed inside containers. 
>
> https://hub.docker.com/_/debian/ 
>
>
>
> -- 
>
> Mathias Behrle 
> PGP/GnuPG key availabable from any keyserver, ID: 
> 0xD6D09BE48405BBF6 
> AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6 
>
 -- 

 --- 
 You received this message because you are subscribed to the Google 
 Groups "Mayan EDMS" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to mayan-edms+...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>> -- 
>>
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Mayan EDMS" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/mayan-edms/Fx8rz4kxPCw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> mayan-edms+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 2414] Re: Upgrading from 2.7.3 to NG Versions

[David Kornahrens]

Thanks Michael.  

Since I'm not currently running any of your versions, I'll wait to submit a 
bug request, but right before Roberto went offline, I reported that our 
Xerox machines were rotating some of our uploads (we use SMTP folder watch 
for submittals).  We still are having to manually log in, rotate the 
document and then place in the correct cabinet.

I understand there are some work flow features, but I don't enough about 
either the language or the program to make this run efficiently.  I'm 
excited, beyond excited, that a group of people are picking up and helping 
Roberto.  

Thanks,
David

On Sunday, April 1, 2018 at 4:56:12 PM UTC-4, Michael Price wrote:
>
> Mayan EDMS NG performs initial installation procedures on new databases 
> and performs upgrades if it detects existing data. However, now that 
> Roberto is back and has started merging our work I would suggest you wait 
> for an official release. Both, the official and our Docker image have 
> django-storages included out-of-the-box.
>
> On Sunday, April 1, 2018 at 4:13:06 PM UTC-4, David Kornahrens wrote:
>>
>> Hello community,
>> We are currently on 2.7.3, deployed through Docker.  I am interested in 
>> updating to the latest NG version, if it's supported to upgrade through 
>> Docker.
>>
>> The only concern, we deployed Django Storages and offload media to Amazon 
>> S3.  We need to ensure this stays offloaded to S3 and that our documents 
>> can still be viewed when updated.  We currently have ~5K files.
>>
>> Is this able to be upgraded via Docker?  Or do we need to wait for 
>> official support from the Mayan repository?
>>
>> Thanks,
>> David
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.