[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: 1831] Re: Backing up the docker data container while mayan-edms is running

[Roberto Rosario]

It seems there is an API for live backups of SQLite 
(https://www.sqlite.org/backup.html), so in theory it is possible with 
other tools.

The link https://www.sqlite.org/howtocorrupt.html mentions:

Systems that run automatic backups in the background might try to make a 
> backup copy of an SQLite database file while it is in the middle of a 
> transaction. The backup copy then might contain some old and some new 
> content, and thus be corrupt.


I agree, the best and simplest approach is to stop Mayan and then do the 
backup. 

On Thursday, June 22, 2017 at 11:34:53 PM UTC-4, Hans Fritz wrote:
>
> Can it potentially corrupt the backup if the mayan-edms docker container 
> isn't stopped while the backup is being made? I'm using the sqlite3 
> datastore.
>
> My instincts tell me that it can get corrupted if Mayan writes to the 
> sqlite database while it's being archived, but I'd like to make sure.
>

-- 

--- 
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: 1830] Re: SANE Scanner

[Roberto Rosario]

The SANE source uploads the document directly to Mayan from the scanner. 
This is my setup for the EPSON Workforce WF-3640 I'm using. The 'device 
name' "epson2:net:192.168.11.122" is returned by scanning the network with 
SANE's command:

scanimage -L

when SANE's Python library improve in the future this can be made from 
Mayan itself.




When uploading documents I just use the same steps as when using the 
webform.


In this window I select 'Epson', then place the document to scan in the 
scanner's flatbed and press "Scan". Mayan accesses the scanner, scans the 
paper document and makes it available as a Mayan document directly without 
having to store it in a folder. The process is still synchronous so the UI 
will block or "freeze" while scanning. As more users test and provide 
feedback it can be made asynchronous and much faster (like when using paper 
feeders for bulk scanning). The SANE source eliminates the need to scan 
documents using other software prior to upload them to Mayan. The drawback 
is that USB or IP access is required. If using Mayan in the cloud that 
means a VPN or tunnel to access the on-site scanner from the cloud.


On Wednesday, June 28, 2017 at 2:26:14 PM UTC-4, David Kornahrens wrote:
>
> 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: 1828] Re: Mayan EDMS version 2.4 released

[Roberto Rosario]

Excellent! Glad to hear that!

On Wednesday, June 28, 2017 at 12:41:10 PM UTC-4, David Kornahrens wrote:
>
> 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: 1828] Re: Digital Ocean Volumes

[Roberto Rosario]

Haven't use Digital Ocean volumes. If they emulate S3 protocol you can use 
django-storages to access them. There are threads in the group getting that 
to work.

https://groups.google.com/forum/#!searchin/mayan-edms/S3|sort:relevance/mayan-edms/tZjmn5u4y2A/qXxW6cigx9MJ

https://groups.google.com/forum/#!searchin/mayan-edms/S3|sort:relevance/mayan-edms/vLrCA6zoIIQ/5hiTd-NUCQAJ

On Wednesday, June 28, 2017 at 4:22:23 PM UTC-4, David Kornahrens wrote:
>
> 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.

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

[Roberto Rosario]

Go inside the running container with:

docker exec -ti mayan-edms /bin/bash

This executes a bash shell inside the container. The command prompt should 
display something like this:

root@9210b0c7f945:/# 

Now do a:

cat /etc/nginx/sites-enabled/mayan-edms

You should see the file contents.

There are no editors included in the container to cut size. To edit the 
file you need to install one using:

apt-get update && apt-get install vim -y

Afterwards use vi /etc/nginx/site-enabled/mayan-edms

Enter insert mode pressing the key .
Make the changes.
Increase client_max_body_size (It's set at 500M = 500 megabytes).
Increase proxy_read_timeout (maximum time an upload can take before it 
timesout. It's set at 600s = 600 seconds = 10 minutes).
Leave insert mode pressing 
Save pressing <:> and then 
Exit the editor using <:> and then 

Restart the NGINX server using:

supervisorctl restart nginx

I'll check if NGINX supports environment variables, and make these settings 
configurable at runtime without having to edit this file.
This is not directly related to Mayan and therefore lower in the priority 
schedule, so it can take a while.

On Wednesday, June 28, 2017 at 2:16:36 PM UTC-4, David Kornahrens wrote:
>
> Roberto,
> Apologize for asking this.  Feels like I'm beating a dead horse, but I 
> used the docker install method and I cannot even find the NGINX folder at 
> all.
>
> I have navigated to /etc with no NGINX folder available.  
>

-- 

--- 
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: 1826] Re: Uploading pdf files with mayan-api_client not working

[Roberto Rosario]

Never seen this issue before and don't have a Windows machine or VM readily 
available for testing. 

Could be a content type or HTTP encoding issue. Try uploading the PDF 
zipped. If the PDF file is corrupted, it is being introspecting/changed in 
transit and not just mangled by the HTTP/IP stack.

Make sure the PDFs are not infected with a malware and something is 
"cleaning" them up.

Turn off any antivirus or antimalware in Windows. Also make sure nothing is 
filtering or throttling the IP port of the API.

Test with PDFs created with other software and with others from a know good 
source.

Upload them from another computer in case the computer you are using for 
the client is infected and infecting the PDF on transit or when being 
opened.

Try uploading the PDF files via the API client from a Linux distro to see 
if the problem is at the sending or receiving end.

On Tuesday, June 27, 2017 at 4:21:54 PM UTC-4, Ben wrote:
>
> I want to use the mayan-api_client to upload documents( to automate file 
> uploads from a windows machine ) 
> On a Linux machine it works as expected but on a Windows machine ( Win 7, 
> Mayan on Ubuntu 16.04) it doesn't upload PDFs. 
> I'm using this command: 
>
> api = API(host='http://192.168.1.6', username='admin', 
> password='something')
> with open('c:\Users\User\Documents\test.pdf') as file_object:
> response = api.documents.documents.post({'document_type': 2}, 
> files={'file': file_object})
>
> All other file types are working, except PDF. The file is corrupted on the 
> server - only a few bytes are there, therefor it cannot be proceeded and it 
> gives me this error:
>
> converter.backends.python <12314> [ERROR] "get_page_count() Exception 
> determining PDF page count; Unexpected EOF".
>
> I have no problems to upload the same file using the web interface.
>
> It seems there is a problem with the file transfer to the server. But why 
> only PDFs?
>
> Any ideas where the problem could be?
>
>
>
>

-- 

--- 
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: 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: 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.