Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/nodepit/node-migrate-state-store-mongodb

MongoDB-based state storage implementation for the migrate aka. node-migrate framework
https://github.com/nodepit/node-migrate-state-store-mongodb

migration mongodb nodejs

Last synced: 20 days ago
JSON representation

MongoDB-based state storage implementation for the migrate aka. node-migrate framework

Host: GitHub
URL: https://github.com/nodepit/node-migrate-state-store-mongodb
Owner: NodePit
License: mit
Created: 2018-11-30T14:55:08.000Z (almost 6 years ago)
Default Branch: master
Last Pushed: 2024-08-30T13:26:19.000Z (3 months ago)
Last Synced: 2024-10-26T22:17:28.937Z (20 days ago)
Topics: migration, mongodb, nodejs
Language: TypeScript
Homepage:
Size: 891 KB
Stars: 10
Watchers: 4
Forks: 1
Open Issues: 0
Metadata Files:
- Readme: readme.md
- Changelog: CHANGELOG.md
- License: LICENSE

Awesome Lists containing this project

README

# node-migrate state storage for MongoDB

[![Actions Status](https://github.com/NodePit/node-migrate-state-store-mongodb/workflows/CI/badge.svg)](https://github.com/NodePit/node-migrate-state-store-mongodb/actions)
[![codecov](https://codecov.io/gh/NodePit/node-migrate-state-store-mongodb/branch/master/graph/badge.svg)](https://codecov.io/gh/NodePit/node-migrate-state-store-mongodb)
[![npm version](https://badge.fury.io/js/%40nodepit%2Fmigrate-state-store-mongodb.svg)](https://badge.fury.io/js/%40nodepit%2Fmigrate-state-store-mongodb)

This is a [state storage implementation](https://github.com/tj/node-migrate#custom-state-storage) for the [`node-migrate`](https://github.com/tj/node-migrate) framework. It will store your migation state in a MongoDB collection called `migrations` which contains a single document.

In case you’re using `node-migrate` for migrating your MongoDB, it makes sense to keep the state within the database itself, instead of a separate file which is used by `node-migrate` per default.

## Installation

```shell
$ yarn add @nodepit/migrate-state-store-mongodb
```

## Usage

Either create a wrapper script such as `run-migrations.ts` which calls the migration API like so:

```javascript
import * as migrate from 'migrate';
import { MongoStateStore } from '@nodepit/migrate-state-store-mongodb';

migrate.load({
stateStore: new MongoStateStore(MONGODB_HOST),
// further configuration …
}, (err, set) => {
// your code …
});
```

Per default, the migrations are stored in a collection called `migrations`. If you want to customize the collection name, instantiate the `MongoStateStore` with an object instead:

```javascript
new MongoStateStore({ uri: MONGODB_HOST, collectionName: 'custom-migrations-collection' });
```

## Synchronization

If you’re running in a clustered environments with more than one node, there will likely be concurrency issues when more than one node tries to run a migration (also see [here](https://github.com/NodePit/node-migrate-state-store-mongodb/issues/30)). The plugin provides a locking mechanism which ensures that only one node can run migrations at a given time (and other ones will just wait until the migration has finished). For this, initialize `MongoStateStore` with a `lockCollectionName`:

```javascript
new MongoStateStore({
uri: MONGODB_HOST,
collectionName: 'migrations',
lockCollectionName: 'migrationlock'
});
```

… then use the `synchronizedUp` function instead of calling `migrate.load` and `set.up` directly to ensure that the migration is only run on one instance at a time:

```javascript
import { MongoStateStore, synchronizedUp } from '@nodepit/migrate-state-store-mongodb';

await synchronizedUp({ stateStore: mongoStateStore });
```

## CLI Usage

Alternatively, you can also pass the store on the `migrate` CLI using the `--store` flag. For that, create a a file which has as default export a configured subclass with a zero-arg constructor of the `MongoStateStore`. See [here](https://github.com/NodePit/node-migrate-state-store-mongodb/issues/9#issuecomment-658018332) for details. You can then call `migrate up --store=./my-store.js`. Locking is not available in this case.

## Development

Install NPM dependencies with `yarn`.

To execute the tests, run the `test` task.

For the best development experience, make sure that your editor supports [ESLint](https://eslint.org/docs/user-guide/integrations) and [EditorConfig](http://editorconfig.org).

## Releasing to NPM

Commit all changes and run the following:

```shell
$ npm login
$ npm version
$ npm publish --access public
```

… where `` is one of `patch`, `minor`, or `major`. This will update the `package.json`, and create a tagged Git commit with the version number.

## Contributing

Pull requests are very welcome. Feel free to discuss bugs or new features by opening a new [issue](https://github.com/NodePit/node-migrate-state-store-mongodb/issues).

- - -