db:seed in Vagrantfile  / also, reduce VM .memory and .cpus

This tests out so far as it goes. There is still a setup problem because the twinge/ruby_pg Docker image needs an update, but that's unrelated.
No, per this, db:setup only does the schema load and seed:
http://stackoverflow.com/questions/10301794/difference-between-rake-dbmigrate-dbreset-and-dbschemaload


--Mark

On Fri, Oct 3, 2014 at 10:51 AM, Josh Starcher <notifications@github.com>
wrote:

> In Vagrantfile:
>
> > @@ -18,7 +18,7 @@ docker run -d -p 3000:3000 -v /app:/app --link redis:redis --link postgres:db --
> >  cp -n /app/config/database.example.yml /app/config/database.yml
> >  cp -n /app/config/redis.example.yml /app/config/redis.yml
> >  cp -n /app/.env.example /app/.env
> > -docker run -i -t -v /app:/app --link redis:redis --link postgres:db  --rm twinge/ruby_pg bash -c "cd /app && bundle exec rake db:create db:migrate"
> > +docker run -i -t -v /app:/app --link redis:redis --link postgres:db  --rm twinge/ruby_pg bash -c "cd /app && bundle exec rake db:create db:setup"
>
> Is the db:create part still needed? or will db:setup do the create?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/CruGlobal/global_registry/pull/31/files#r18398950>.
>