A way to provide schema migration in dev startup about generator-jhipster-nodejs HOT 6 CLOSED

Remember that, according the answer, it will be a prod db connection with sqlite (or mongodb)..

``
const defaultOptions = {
type: 'postgres',
port: 5432,
username: 'user',
password: 'password',
database: 'db',
synchronize: true,
};

@module({
imports: [
TypeOrmModule.forRoot({
...defaultOptions,
host: 'photo_db_host',
entities: [Photo],
})
``
So, according the environment (dev or prod), the connection must be changed. Please attention that in dev mode there is always the sqlite db.

from generator-jhipster-nodejs.

The issue is not more an optional, because we have to provide a migration with typeORM for scripts in dev mode running for sqlite

from generator-jhipster-nodejs.

Consider feature/migration-db and this src/ormconfig.ts:

import { ConnectionOptions } from 'typeorm'; const config: ConnectionOptions = {  type: 'postgres',  host: process.env.POSTGRES_HOST,  port: Number(process.env.POSTGRES_PORT),  username: process.env.POSTGRES_USER,  password: process.env.POSTGRES_PASSWORD,  database: process.env.POSTGRES_DB,  entities: [    __dirname + '/../**/*.entity{.ts,.js}',  ],  cli: {    migrationsDir: 'src/migrations',  }}; export = config;

from generator-jhipster-nodejs.

from generator-jhipster-nodejs.

Hi @deepu105,
now for this blueprint, in the server generator there are only two questions: serverPort and mongoProdDatabase . The other prompts questions for the server generation are been delated, because in this blueprint they haven't sense to be due to their java spring meaning. So if you answer to yes for the mongoProdDatabase there will generated the config for this, otherwise the sqlite is the default. So be sure that there aren't other database questions. For this I have renamed the issue. If it is not clear, feel free to ask me.

from generator-jhipster-nodejs.

from generator-jhipster-nodejs.