Community mailing list archives
Re: Dev Adviceby
DevCO Colombia , David Arnold
Hi Nhomar and Daniel,
thanks for your advices. The templating is a good idea, I tried it, however it didn't fit that much in my workflow or let's say it is rather complicated to manage as I would need a well defined template set for most use cases. Else it would be useful only every so often and that would kill the approach. But you're right in the end, this is probably the approach with the most effect. One thought: When I have a lot of templates and are working on different features at the same time, I would like to get the other databases out of the way because at some point I would just accidentally click on the wrong one and mess things up. I know there are domain filters in --db-filter, but can I use wildcards as well? Like this I could prefix databases and when I would have --db-filter "feature_xyz_*" and a --template "tmplt_feature_xyz" and anything else would get out of my way. I think if this doesn't exists it's worth I would start to think about PR to upstream.
To speed up server time loading I would rather bet on CPU or RAM?
Thanks & best
El jue., 9 jun. 2016 a las 14:14, Nhomar Hernandez (<firstname.lastname@example.org>) escribió:
On Thu, Jun 9, 2016 at 2:06 PM, Nhomar Hernandez <email@example.com> wrote:create the db manually from a template.
Sorry i was not clear here:template==A first installed db with your big modules.If you change your module list you will need a -u base after creation.--