bluehotdog / sails-migrations Goto Github PK
View Code? Open in Web Editor NEWThe missing, migrations, arm of the octopus
License: MIT License
The missing, migrations, arm of the octopus
License: MIT License
Currently the migrator doesn't validate that it receives migrations without duplicate names and duplicate versions.
consider allowing the following syntax:
exports.up: function(done) {
this.drop("tableName",done)
}
need to consider how it will work for nested operations
Perhaps a similar problem to #41
I get the following output when doing an npm install:
~$ npm install sails-migrations
-
> [email protected] install /Users/pivotal/node_modules/sails-migrations/node_modules/pg
> node-gyp rebuild || (exit 0)
CXX(target) Release/obj.target/binding/src/binding.o
SOLINK_MODULE(target) Release/binding.node
SOLINK_MODULE(target) Release/binding.node: Finished
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "sails-migrations"
npm ERR! node v0.10.33
npm ERR! npm v2.1.8
npm ERR! path /Users/pivotal/node_modules/sails-migrations/bin/cli.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! enoent ENOENT, chmod '/Users/pivotal/node_modules/sails-migrations/bin/cli.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /Users/pivotal/npm-debug.log
And here's that log: https://gist.github.com/camelpunch/34afbb57f1d5ea3af488
Perhaps I've missed an installation step? Annoying that npm install won't tell me what's up apart from the missing file or dir.
A new feature that I think might be useful for sails migrations:
The ability to auto-generate a migration based on a model file. It wouldn't consistently auto-generate migrations for changes, as this seems like it would be difficult and require managing state. The thought is more of a one-time per model time saver. You define your model then call:
sails-migrations generate:model [name of model]
It then parses the model file and creates a migration file based on that model. It doesn't have to parse everything in attributes, if there is some non-standard or in-depth attribute we can just rely on the user updating the migration file to handle that attribute. In my mind the low hanging fruit are:
I'm happy to take a hack at it, but it will just be weekend time which itself is a bit limited right now for me.
Seems that my grunt or something in sails is creating a bunch of connections before the reset tries to run and therefore the reset cannot complete. To me, it looks like sails is being run and creating 6 connections (that is what it complains about) to my 6 models, before the db:reset tries to happen.
Run
grunt db:create -v
//console output
Running "db:setup" task
Running "db:loadConfig" task
Running "db:createVersionTable" task
Verifying property migration.config exists in config...OK
Creating version table
Warning: Invalid connection name specified Use --force to continue.
But the Database is created.
Use Sails.js 0.10.4, sails-mysql 0.10.6
When running any of the commands, I'm getting a "There is no pool defined on the current client" error.
I'm trying to use migration for my app which is lifted on heroku.
I've installed sails-migrations and trying to create db.
I got this error when I trying create db here...and I don't know what I should do..
Is there any help?? TT
grunt db:create
>> Tasks directory "./grunt/tasks" not found.
Running "db:loadConfig" task
Running "db:createInternalTask" task
Trying to create a new database
Fatal error: Command failed: createdb: could not connect to database template1: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
I'm using [email protected] [email protected].
Thanks.
Just did a clean install
vagrant@vagrant-ubuntu-trusty-64:/vagrant/server$ sails --version
0.11.0
vagrant@vagrant-ubuntu-trusty-64:/vagrant/server$ sails-migrations --version
sails_migrations CLI version: 2.0.7
Local sails_migrations version: 2.0.7
vagrant@vagrant-ubuntu-trusty-64:/vagrant/server$ sails-migrations db:create
Error: ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"myDbName"' at line 1
at Query.Sequence._packetToError
developmentMysqlServer: {
adapter: 'sails-mysql',
host: 'localhost',
user: 'root',
password: '',
database: 'api'
},
I'd like to look at an example migration file so I can see how to best use sails-migrations. Would be great if there was an example file!
This is more a knex issue than sails-migrations issue, but wanted to have the issue documented for future users. http://knexjs.org/#Schema-timestamps
table.timestamps()
creates created_at
and updated_at
while sails is expecting createdAt
and updatedAt
table.timestamps()
:table.timestamp('createdAt');
table.timestamp('updatedAt');
table.timestamps()
:Create a migration for fixing the erroneous columns (sails-migrations generate fix_timestamps
)
'use strict';
exports.up = function(knex, Promise) {
function renameUp(table) {
table.renameColumn('created_at', 'createdAt')
.renameColumn('updated_at', 'updatedAt');
}
Promise.all([
knex.schema.table('myTable', renameUp)
]);
};
exports.down = function(knex, Promise) {
function renameDown(table) {
table.renameColumn('createdAt', 'created_at')
.renameColumn('updatedAt', 'updated_at');
}
Promise.all([
knex.schema.table('myTable', renameDown)
]);
};
@BlueHotDog Danni, as you probably remember, we're using sails-migrations in production at Treeline. I think we still need to find someone who can help push the project further forward (e.g. as far as documentation), but I'd like to offer to help if we can in the mean time in the case of any immediate term emergencies or bugs that come up.
I'd also like to see manual migrations make their way into the Sails core CLI in the future. This would need to be specced out further into a proper proposal, and I think the first step to getting there is for more folks to start using this module (hopefully incorporating ideas from sails-db-migrate).
So in the mean time, please feel free to ping any of the Sails core team on Twitter for any high-priority patches in sails-migrations and we'll do our best to help. Thanks everyone!
it would be great to bump up version of knex lib to support typescript migration files
Currently drop/create works in a weird way, of executing a special query against the db directly, without using waterline(since waterline does not support that yet).
Hi!
This was reported earlier by @sposmen (#24), so we're creating a new issue as you suggested.
We're getting the following error when doing npm install sails-migrations while running Sails 0.10.0-RC4:
npm ERR! peerinvalid The package sails does not satisfy its siblings' peerDependencies requirements!
Thank you!
Currently we're only supporting the sails-mysql adapter.
db:create hangs with:
grunt db:create
Running "db:loadConfig" task
Running "db:createInternalTask" task
Trying to create a new database
verbose mode doesn't show additional info
On Ubuntu 14.04, I get the following...
root@f32dcd67fa99:/app# npm install sails-migrations
npm ERR! tar.unpack untar error /root/.npm/sails-migrations/2.0.7/package.tgz
npm ERR! Linux 4.0.9-boot2docker
npm ERR! argv "node" "/usr/bin/npm" "install" "sails-migrations"
npm ERR! node v0.12.7
npm ERR! npm v3.3.3
npm ERR! path /app/node_modules/.staging/sails-migrations-8f658b2f782b7fad6532770007846687/tasks/db:status.coffee
npm ERR! code EPROTO
npm ERR! errno -71
npm ERR! EPROTO, open '/app/node_modules/.staging/sails-migrations-8f658b2f782b7fad6532770007846687/tasks/db:status.coffee'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /app/npm-debug.log
Turns out, I get a similar error (EPROTO) if I do the following...
root@f32dcd67fa99:/app# tar -xvf /root/.npm/sails-migrations/2.0.7/package.tgz
package/package.json
package/README.md
package/LICENSE
package/index.js
package/bin/cli.js
package/bin/run_tests.js
package/lib/sails-migrations.js
package/lib/sails-migrations/create_database.js
package/lib/sails-migrations/current_version.js
package/lib/sails-migrations/drop_database.js
package/lib/sails-migrations/errors.js
package/lib/sails-migrations/generate.js
package/lib/sails-migrations/migrate_to_latest.js
package/lib/sails-migrations/rollback.js
package/lib/sails-migrations/status.js
package/lib/sails-migrations/helpers/config_loader.js
package/lib/sails-migrations/helpers/database_tasks.js
package/lib/sails-migrations/helpers/migrator_loader.js
package/lib/sails-migrations/helpers/sails_integration.js
package/tasks/db:status.coffee
tar: package/tasks/db\:status.coffee: Cannot open: Protocol error
tar: Exiting with failure status due to previous errors
Not exactly sure why this is happening.
Running the following migration creates the sails_migrations
table, adds a row to it, but does not create the inventoryAccounts
table. Perhaps I'm missing something obvious...
'use strict';
exports.up = function(knex, Promise) {
knex.schema.createTable('inventoryAccounts', function (table) {
table.increments();
table.text('name');
table.text('slug');
table.boolean('allowNegativeBalance');
});
};
exports.down = function(knex, Promise) {
knex.schema.dropTable('inventoryAccounts');
};
I can't figure out a way to make db:create work on Postgresql.
I am running on Ubuntu, installed postgres using the standard apt-get package and have configured it to allow md5 login and gave my user (alvaro) permissions to create databases.
The database does get created, the process fails on creating the version table.
This is the error:
alvaro: (master) ~/Projects/SailsTestProject$ grunt db:create
Running "db:loadConfig" task
Running "db:createInternalTask" task
Trying to create a new database
Password:
>> Database created successfully
Running "db:createVersionTable" task
Creating version table
Warning: undefined is not a function Use --force to continue.
Aborted due to warnings.
By tracking this down, I believe it's happening on line 29 of the schema_migration.coffee file: "new SchemaMigration(options, cb)"
I am using "sails": "~0.10.2" which might not be supported.
Any clues onto what could be done here would be greatly appreciated.
I did get a repo up what has the problem just in case: https://github.com/oliveiraa/sails-migrations-test
Thanks,
Alvaro Oliveira.
In attempting to migrate new changes into the production DB for the first time, it was realized that the environment information isn't handled properly.
A workaround for the issue is:
NODE_ENV=production sails-migrations migrate
The issue appears to be that the configuration pulls in the default configuration under the assumption that the environment is development, not production, despite whether or not someone is using the '--env' flag. This was confirmed by running the following script to print out what the application is seeing:
const SailsIntegration = require('./node_modules/sails-migrations/lib/sails-migrations/helpers/sails_integration');
const path = require('path');
var modulesPath = path.join(process.cwd(), 'node_modules');
SailsIntegration.loadSailsConfig(modulesPath, function(err, cache) {
console.log(cache);
});
For me, this was resulting in a connection refused error (ECONNREFUSED).
I'm setting up my initial app and trying to create the initial empty database, and it's failing when running grunt db:create
bloggy$ grunt db:create
Running "db:loadConfig" task
Error creating a connection to Postgresql: error: database "bloggy_develpment" does not exist
Error creating a connection to Postgresql: error: database "bloggy_develpment" does not exist
error: Hook failed to load: orm (error: database "bloggy_develpment" does not exist)
error: Error encountered while loading Sails core!
error: error: database "bloggy_develpment" does not exist
at Connection.parseE (/Users/jeremy/Sites/bloggy/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:561:11)
at Connection.parseMessage (/Users/jeremy/Sites/bloggy/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:390:17)
at null.<anonymous> (/Users/jeremy/Sites/bloggy/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:98:18)
at Socket.emit (events.js:95:17)
at Socket.<anonymous> (_stream_readable.js:748:14)
at Socket.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:410:10)
at emitReadable (_stream_readable.js:406:5)
at readableAddChunk (_stream_readable.js:168:9)
at Socket.Readable.push (_stream_readable.js:130:10)
Warning: database "bloggy_develpment" does not exist Use --force to continue.
Aborted due to warnings.
"version": "0.0.4"
with sails 0.9.16
UPDATE
I added the grunt.loadNpmTasks('gake')
to my Gruntfile.js, so it no longer fails, but it sits there during Running "db:loadConfig" task
and does nothing. I let it run for several minutes. It seems any grunt command I do now just hangs. I'm not sure if I need to run that loadNpmTasks('gake') or not. The instructions on https://www.npmjs.org/package/sails-migrations don't mention it.
I tried as tutorial, even clone sails-migrations-testapp at https://github.com/itayadler/sails-migrations-testapp and try with the test app.
When I try grunt -h
, there is no migration tasks. What is going on, how can I fix this?
Hello
Can't make it work, Getting following error. Do I need to create some config file to get started? Any help will be appreciated. Thanks
codevarun@ubuntu:/var/www/botrovert$ grunt migration:generate --name="my migration name" --force -v Initializing Command-line options: --name=my migration name, --force, --verbose Reading "Gruntfile.js" Gruntfile...OK Registering Gruntfile tasks. Registering "node_modules/sails/node_modules/grunt-contrib-clean/tasks" tasks. Loading "clean.js" tasks...OK + clean Registering "node_modules/sails/node_modules/grunt-contrib-copy/tasks" tasks. Loading "copy.js" tasks...OK + copy Registering "node_modules/sails/node_modules/grunt-contrib-concat/tasks" tasks. Loading "concat.js" tasks...OK + concat Registering "node_modules/sails/node_modules/grunt-sails-linker/tasks" tasks. Loading "scriptlinker.js" tasks...OK + sails-linker Registering "node_modules/sails/node_modules/grunt-contrib-jst/tasks" tasks. Loading "jst.js" tasks...OK + jst Registering "node_modules/sails/node_modules/grunt-contrib-watch/tasks" tasks. Loading "watch.js" tasks...OK + watch Registering "node_modules/sails/node_modules/grunt-contrib-uglify/tasks" tasks. Loading "uglify.js" tasks...OK + uglify Registering "node_modules/sails/node_modules/grunt-contrib-cssmin/tasks" tasks. Loading "cssmin.js" tasks...OK + cssmin Registering "node_modules/sails/node_modules/grunt-contrib-less/tasks" tasks. Loading "less.js" tasks...OK + less Registering "node_modules/sails/node_modules/grunt-contrib-coffee/tasks" tasks. Loading "coffee.js" tasks...OK + coffee Reading package.json...OK Parsing package.json...OK Initializing config...OK Registering "sails-migrations" local Npm module tasks. Reading /var/www/botrovert/node_modules/sails-migrations/package.json...OK Parsing /var/www/botrovert/node_modules/sails-migrations/package.json...OK Loading "db.coffee" tasks...OK + db:create, db:createInternalTask, db:drop, db:dropInternalTask, db:reset Loading "db:generate.coffee" tasks...OK + migration:generate, migration:generateInternalTask Loading "db:migrate.coffee" tasks...OK + db:migrate, db:migrateTask, db:rollback, db:rollbackTask Loading "db:status.coffee" tasks...OK + db:status, db:status:validateTableExists, db:statusTask Loading "helpers.coffee" tasks...OK >> No tasks were registered or unregistered. Loading "load_config.coffee" tasks...OK + db:loadConfig Loading "Gruntfile.js" tasks...OK + build, compileAssets, default, linkAssets, prod Running tasks: migration:generate Running "migration:generate" task Running "db:loadConfig" task Running "migration:generateInternalTask" task Verifying property migration.config exists in config...Warning: Maximum call stack size exceeded Used --force, continuing. Done, but with warnings.
How can we integrate this project with sails so migrations run when we run sails lift
?
I tried setting this in config/bootstrap.js
:
var sailsMigrations = require('sails-migrations');
module.exports.bootstrap = function(cb) {
console.log('Performing Database Migrations');
sailsMigrations.migrate();
// It's very important to trigger this callback method when you are finished
// with the bootstrap! (otherwise your server will never lift, since it's waiting on the bootstrap)
cb();
};
but I get these errors:
error: The bootstrap function threw an error after its callback was called :: TypeError: Cannot read property 'http' of undefined
at Sails.getHost (/Users/josh/src/project/node_modules/sails/lib/app/private/getHost.js:11:43)
at Sails.bound [as getHost] (/Users/josh/src/project/node_modules/lodash/dist/lodash.js:729:21)
at Sails.getBaseurl (/Users/josh/src/project/node_modules/sails/lib/app/getBaseurl.js:19:20)
at Sails.bound [as getBaseurl] (/Users/josh/src/project/node_modules/lodash/dist/lodash.js:729:21)
at _printSuccessMsg (/Users/josh/src/project/node_modules/sails/lib/app/lift.js:63:56)
at sailsReady (/Users/josh/src/project/node_modules/sails/lib/app/lift.js:43:5)
at /Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:251:17
at /Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:154:25
at /Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:248:21
at /Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:612:34
at afterBootstrap (/Users/josh/src/project/node_modules/sails/lib/app/private/initialize.js:57:5)
at bootstrapDone (/Users/josh/src/project/node_modules/sails/lib/app/private/bootstrap.js:51:14)
at Object.module.exports.bootstrap (/Users/josh/src/project/config/bootstrap.js:22:2)
at Sails.runBootstrap (/Users/josh/src/project/node_modules/sails/lib/app/private/bootstrap.js:44:25)
at Sails.bound [as runBootstrap] (/Users/josh/src/project/node_modules/lodash/dist/lodash.js:729:21)
at Sails.initialize (/Users/josh/src/project/node_modules/sails/lib/app/private/initialize.js:48:9) [TypeError: Cannot read property 'http' of undefined]
/Users/josh/src/project/node_modules/sails/lib/hooks/cors/index.js:113
if (sails.config.cors.securityLevel > sails.hooks.cors.SECURITY_LEVEL_NORMAL) {
^
TypeError: Cannot read property 'SECURITY_LEVEL_NORMAL' of undefined
at Sails.<anonymous> (/Users/josh/src/project/node_modules/sails/lib/hooks/cors/index.js:113:63)
at emitNone (events.js:72:20)
at Sails.emit (events.js:166:7)
at Sails.emitter.emit (/Users/josh/src/project/node_modules/sails/lib/app/private/after.js:50:11)
at Router.flush (/Users/josh/src/project/node_modules/sails/lib/router/index.js:336:9)
at Router.bound (/Users/josh/src/project/node_modules/lodash/dist/lodash.js:729:21)
at Router.load (/Users/josh/src/project/node_modules/sails/lib/router/index.js:115:8)
at Array.bound (/Users/josh/src/project/node_modules/lodash/dist/lodash.js:729:21)
at listener (/Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:490:46)
at /Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:441:17
at _each (/Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:46:13)
at Immediate.taskComplete (/Users/josh/src/project/node_modules/sails/node_modules/async/lib/async.js:440:13)
at processImmediate [as _immediateCallback] (timers.js:368:17)
maybe set a flag on the exports object?
I am tring to use sails-migration and it does not work and i dont have any error. The grunt task just proceed infinitly.
here is my input when i try db:create
Running "db:loadConfig" task
js-bson: Failed to load c++ bson extension, using pure JS version
Running "db:createInternalTask" task
Trying to create a new database
I've followed carefully the docs from this version:
https://github.com/BlueHotDog/sails-migrations/tree/v0.10
I run:
albert$ grunt migration:generate --name="test"
And I get:
/*
* Sails migration
* Created at 2014-11-22T21:48:17+00:00
* */
exports.up = function(adapter, done) {
console.log('Yo!');
done();
};
exports.down = function(adapter, done) {
done();
};
Then I run and get:
albert$ grunt db:migrate
Running "db:loadConfig" task
Running "db:migrateTask" task
Warning: undefined is not a function Use --force to continue.
Aborted due to warnings.
Following exact steps from the docs. Do you know what could be wrong?
More things I tried:
grunt db:create
Running "db:loadConfig" task
Running "db:createInternalTask" task
Trying to create a new database
Fatal error: Error: Command failed: createdb: database creation failed: ERROR: database "albert" already exists
albert$ grunt db:status
Running "db:loadConfig" task
Running "db:status:validateTableExists" task
Checking if sails_schema_migrations exists
Warning: undefined is not a function Use --force to continue.
Aborted due to warnings.
When running 'sudo npm install sails-migrations -g':
npm ERR! Error: ENOENT, chmod '/usr/lib/node_modules/sails-migrations/bin/cli.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Linux 3.13.0-30-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "sails-migrations" "-g"
npm ERR! cwd /home/vagrant/sails
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! path /usr/lib/node_modules/sails-migrations/bin/cli.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! not ok code 0
Note: I run this within a vagrant box where sails is up and running
instead of:
exports.up = (adapter, done) ->
adapter.drop('myTable', done);
done()
exports.down = (adapter, done) ->
# ...
done()
I would prefer to do:
class ICanHasMigration extends SailsMigration
up: ->
@drop('myTable')
down: ->
# ...
class SailsMigration
initilize: (adapter, done_cb)->
handle_up: ->
# delegate all calls to adapter and append the done_cb as the last argument
handle_down: ->
#....
When I attempt to migrate it succeeds in creating my table but outputs an error at the command line. The error and the code for my migration are below.
Warning: .then() only accepts functions but was passed: [object Undefined], [object Undefined]
at SchemaBuilder_PG.Target.then (../node_modules/sails-migrations/node_modules/knex/lib/interface.js:27:33)
'use strict';
exports.up = function(knex, Promise) {
return knex.schema.createTable('user', function (table) {
table.increments();
table.datetime('createdAt');
table.datetime('updatedAt');
})
};
exports.down = function(knex, Promise) {
return knex.schema.dropTable('user');
};
The docs are not to explanatory about how to start using and examples (broken link).
I've manually downloaded and installed (npm broken) the latest version but I wonder if you could throw a line or two about how to actually use it?
Thank you
Heya, this is just a friendly note to let you know that a new version of Liftoff and some of the dependencies commonly used in conjunction with it have been released. This release adds better support for situations where your user's configuration files are written using features behind a v8 flag (e.g. --harmony
). Windows users and io.js
users should see less issues if you upgrade!
Some helpful links:
https://github.com/tkellen/node-liftoff/blob/master/UPGRADING.md#100---200
https://github.com/tkellen/node-v8flags/blob/master/README.md#example
https://github.com/tkellen/node-hacker/blob/master/bin/hacker.js#L10-L14
Thanks!
Please, provide a few examples of usage of your plugin. Link in README file is outdated
Maybe I'm wrong about this entirely, but I believe db:create requires that it be able to create a new database, rather than just a new table. On Heroku, with the basic Postgresql DB, you can't create a new database, only new tables.
If using url: 'postgresql://user:pw@localhost:5432/dbName?ssl=false' in connections.js
There is an error when attempting to connect to the database. It is attempting to connect to 'dbName?ssl=false' instead of dbName, I believe there should be a handler in place to check for the query ssl.
on database reset we should check what models sails has defined and maybe create the table definition for them
When using Heroku Postgres with sails, you have to add a property for ssl:
connections: {
postgres: {
url: 'postgres://CONNECTION_STRING',
ssl: true
}
}
However, this does not work for sails-migrations. You have to explicitly add ssl to the connection string:
connections: {
postgres: {
url: 'postgres://CONNECTION_STRING?ssl=true'
}
}
why do I need "--name=" for generating a migration?
why can't it be just a parameter which follows 'migration:generate' (a la Rails)?
Path is 'null' while running sails-migrations in Node 6
Not sure what's going on here but every other module installs perfectly on my setup. I use nvm.
albert$ npm install -g sails-migrations
/
> [email protected] install /usr/local/opt/nvm/v0.10.32/lib/node_modules/sails-migrations/node_modules/pg
> node-gyp rebuild || (exit 0)
/bin/sh: pg_config: command not found
gyp: Call to 'pg_config --libdir' returned exit status 127. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpEx (/usr/local/Cellar/nvm/0.17.2/v0.10.32/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:343:16)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Darwin 13.4.0
gyp ERR! command "node" "/usr/local/Cellar/nvm/0.17.2/v0.10.32/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/Cellar/nvm/0.17.2/v0.10.32/lib/node_modules/sails-migrations/node_modules/pg
gyp ERR! node -v v0.10.32
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm ERR! Error: ENOENT, chmod '/usr/local/opt/nvm/v0.10.32/lib/node_modules/sails-migrations/bin/cli.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Darwin 13.4.0
npm ERR! command "/usr/local/opt/nvm/v0.10.32/bin/node" "/usr/local/opt/nvm/v0.10.32/bin/npm" "install" "-g" "sails-migrations"
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! path /usr/local/opt/nvm/v0.10.32/lib/node_modules/sails-migrations/bin/cli.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! not ok code 0
Once I do an export of the postgresql path, I get these:
albert$ npm install -g sails-migrations
> [email protected] install /usr/local/opt/nvm/v0.10.32/lib/node_modules/sails-migrations/node_modules/pg
> node-gyp rebuild || (exit 0)
CXX(target) Release/obj.target/binding/src/binding.o
SOLINK_MODULE(target) Release/binding.node
SOLINK_MODULE(target) Release/binding.node: Finished
npm ERR! Error: ENOENT, chmod '/usr/local/opt/nvm/v0.10.32/lib/node_modules/sails-migrations/bin/cli.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Darwin 13.4.0
npm ERR! command "/usr/local/opt/nvm/v0.10.32/bin/node" "/usr/local/opt/nvm/v0.10.32/bin/npm" "install" "-g" "sails-migrations"
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! path /usr/local/opt/nvm/v0.10.32/lib/node_modules/sails-migrations/bin/cli.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! not ok code 0
Hi! I'm trying to use this with sails v0.11. I've done really basic stuff so far without any problem. Do you know of any issue that may arise later on? Is the README to be updated (it indicates support up to 0.10.5)? Not sure whether the v0.10 to v0.11 upgrade has affected any of the aspects this lib relies on...
Do you have a plan to develop sails-migrations for waterline 0.10.0? On 'rc' version actually i have this error:
npm ERR! peerinvalid The package sails does not satisfy its siblings' peerDependencies requirements!
Thanks!
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.