Thursday, May 11, 2017
Hi, Hassan Schroeder,
-- Appreciate the advice, but it doesn't solve the problem. When you deploy to the "global" staging, you'd still have same problem.
I'm coming to think that creating "structure.sql" wasn't meant to be part of feature branch, but only be created after deployment to production.
On Wednesday, May 10, 2017 at 9:00:26 PM UTC+3, Hassan Schroeder wrote:
On Wednesday, May 10, 2017 at 9:00:26 PM UTC+3, Hassan Schroeder wrote:
On Wed, May 10, 2017 at 10:21 AM, Ilya Kaplan <kapla...@gmail.com> wrote:
> The problem starts when there are more than one project with migration in
> staging environment. When deploying developers always have conflicts with
> each other, mainly because of migrations list at the bottom.
>
> Is there any common solution to this problem?
The startup where I'm working now has a "global" staging system
plus separate staging systems for each developer.
If you're using AWS or equivalent, you can spin up instances when
you need them, if you don't want them running all the time...
HTH!
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/de20bd50-86e1-4448-8a36-e6c4b7a2527c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment