Custom data directory not working

[ks-dipeshc]

I am using 1.4.10 version in my NestJs (node) project.

I run my project using the docker.

When i execute update command inside docker and restart the container, the data will lose.

So I read the documentation they mention here to use env variable. https://github.com/geoip-lite/node-geoip?tab=readme-ov-file#environment-variables
but Some how it is not working. they always use directory of the the node_modules.

Is that something I missed?
Thank you.

[bluesmoon]

If you are installing inside docker, your data upgrades will be ephemeral - you will need to download them every time you start the container.

A better option is to create a docker volume that has the data files. Whenever you upgrade the files, you commit the volume to create a new image. This only needs to be done once a month. You can mount this volume into other docker containers as read-only to be used as needed.

[ks-dipeshc]

A better option is to create a docker volume that has the data files. Whenever you upgrade the files, you commit the volume to create a new image. This only needs to be done once a month. You can mount this volume into other docker containers as read-only to be used as needed.

@bluesmoon Thanks.
How Can I inform geoip-lite package to use that volume for data instead of node_modules/geoip-lite/data/? As I mention env variable is not helping.

[bluesmoon]

Mount the volume into that location

[ks-dipeshc]

Mount the volume into that location

Can you please elaborate the steps. As i am new in Docker.

FROM node:18.16-alpine AS development
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run build

RUN npm explore geoip-lite -- npm run-script updatedb license_key=mykey

CMD [ "node", "dist/main.js" ]

My yml file for project

version: '3.8'

services:
  app:
    build:
      context: .
      dockerfile: Dockerfile
    container_name: geoip2
    ports:
      - '3001:3000'
    volumes:
      - .:/app

[victimsss]

I also use NestJS, but I don't mount the database file. Instead, I first update it when building the image, and then dynamically update it within the service on a weekly/monthly basis.
The reason for not mounting is that I have the following concerns:
The author changes the path
Inconsistent behavior of yarn, pnpm, and npm

My approach, for your reference

Dockerfile

COPY package.json pnpm-lock.yaml ./
RUN pnpm install

RUN pnpm run build

RUN pnpm prune --prod

#update
RUN cd node_modules/geoip-lite && npm run-script updatedb -- license_key=xxxx

# You can use docker exec to enter the container and check the log file.
RUN touch /app/node_modules/geoip-lite/geoip-updatedb.log
RUN echo $(date +%s) > /app/node_modules/geoip-lite/geoip-updatedb.log

dynamically update , using Task Scheduling https://docs.nestjs.com/techniques/task-scheduling

autoUpdateGeoIP

import { Injectable, Logger } from '@nestjs/common';
import {
  HealthCheckService,
  HealthCheck,
  TypeOrmHealthIndicator,
} from '@nestjs/terminus';

import { ConfigService } from '@nestjs/config'; 
import { Cron, CronExpression } from '@nestjs/schedule';

import { execSync } from 'child_process';

import { reloadDataSync } from 'geoip-lite'

@Injectable()
export class InternalService {
  constructor(
    private health: HealthCheckService,
    private db: TypeOrmHealthIndicator,
    private configService: ConfigService,
    
  ) {}

  @HealthCheck()
  check() {
    return this.health.check([async () => this.db.pingCheck('database')]);
  }

  @Cron(CronExpression.EVERY_WEEK)
  async autoUpdateGeoIP() {
    try {
      Logger.log('Updating GeoIP database');
      const licenseKey = this.configService.get('MAXMIND_LICENSE_KEY');
      execSync(`npm run-script updatedb license_key=${licenseKey}`);
      reloadDataSync();
      Logger.log('GeoIP database updated');
    } catch (error) {
      Logger.error(error.message);
      
    }
  }
}

import

import { Logger, Module } from '@nestjs/common';
import { TerminusModule, TypeOrmHealthIndicator } from '@nestjs/terminus';
import { ScheduleModule } from '@nestjs/schedule';
import { InternalController } from './internal.controller';
import { InternalService } from './internal.service';

@Module({
  imports: [ScheduleModule.forRoot(), TerminusModule],
  controllers: [InternalController],
  providers: [InternalService, Logger, TypeOrmHealthIndicator],
})
export class InternalModule {}

[bluesmoon]

That's a good idea.