Community mailing list archives
Re: Dev Adviceby
Vauxoo S.A. de C.V., Nhomar Hernandez
On Thu, Jun 9, 2016 at 4:02 PM, David Arnold <email@example.com> wrote:
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.
The point of dbfilter is avoid the error.
What I do is that I have a folder with several configfiles and I simply call the specific configfile with the environement an need per feature.
That + a proper branch management is enought.
We use runbot also, with runbot_travis2docker you car create an environment directly from the CI without move a finger (even with ssh access.
The problema is that for such deal you need to have a proper machine in the cloud because it is not feasible have that in the machine you described.