Hi Mathias,

The contrib section will be kept, I just removed outdated sample 
configuration files ie: Apache using mod_python (mod-proxy-uwsgi is a 
better choice).

I will add new contrib files based in this new deployment document to help 
those building containers or deploying straight from a Git clone.

I agree, it can be improved in a lot of ways and RabbitMQ is much better, 
that is why I emphasize that this is a minimal and quick production deploy, 
is not recommended for enterprise or work-groups of more than 2-3 users. 
The idea in including this chapter is to allow for production deployments 
(not leaving users in the dark about ./manage runserver vs. NGINX), but for 
anything else bigger I still recommend users to get paid professional 
consulting.

On Thursday, October 22, 2015 at 5:40:11 AM UTC-4, Mathias Behrle wrote:
>
> * Roberto Rosario: " [Mayan EDMS: 1136] Official method for production 
>   deployment" (Wed, 21 Oct 2015 16:24:13 -0700 (PDT)): 
>
> > As promised this is the officially recommended way to do a simple 
> > production deployment. A setup like this should scale to several hundred 
> > thousand documents and 2 to 3 concurrent users. This setup should cover 
> > most people wanting to use Mayan EDMS for personal and home office use, 
> any 
> > more than that I recommend you seek consulting/support for your use 
> case. 
> > 
> > http://mayan.readthedocs.org/en/development/topics/deploying.html 
>
> Great document merging in contrib files! Will test and review those next 
> days. 
>
> After the deletion of the contribs section I am still a little bit in 
> doubt 
> where information about alternative setups should be put? There are for 
> sure 
> people using apache, rabbitmq, ... Any thoughts? 
>
> -- 
>
>     Mathias Behrle 
>     PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 
>

-- 

--- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to