[GH-ISSUE #2173] [bug]: Deployment issues #736

New issue

Closed

opened 2026-03-16 16:56:45 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 16:56:45 +03:00

Owner

Originally created by @juandl on GitHub (Mar 17, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2173

Is there an existing issue for this?

I have searched the existing issues

Current behavior

Is not possible to use "docker image hub" because the env is already set on build time, I think the best way to allow users who want to use "docker" in production is to move nuxt.config.js to use env on runtime and also update the docker file to build using an example env but allow nuxt.js to read on runtime too.

I believe you can specify "publicRuntimeConfig" all envs variables to catch envs on runtime

Steps to reproduce

docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest

Environment

Production

Version

Cloud

Originally created by @juandl on GitHub (Mar 17, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2173 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior Is not possible to use "docker image hub" because the env is already set on build time, I think the best way to allow users who want to use "docker" in production is to move [nuxt.config.js](https://github.com/hoppscotch/hoppscotch/blob/main/packages/hoppscotch-app/nuxt.config.js) to use env on runtime and also update the docker file to build using an example env but allow nuxt.js to read on runtime too. I believe you can specify "publicRuntimeConfig" all envs variables to catch envs on runtime ### Steps to reproduce 1. docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest ### Environment Production ### Version Cloud

kerem

2026-03-16 16:56:45 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 16:57:08 +03:00

Author

Owner

@TheBeachMaster commented on GitHub (Mar 18, 2022):

I got this to work by manually copying my own .env file into packages/hoppscotch-app using Docker

@TheBeachMaster commented on GitHub (Mar 18, 2022): I got this to work by manually copying my own `.env` file into `packages/hoppscotch-app` using Docker

kerem commented

2026-03-16 16:57:13 +03:00

Author

Owner

@juandl commented on GitHub (Mar 18, 2022):

I got this to work by manually copying my own .env file into packages/hoppscotch-app using Docker

That's great, but I think it should be implemented instead of workaround 😕

@juandl commented on GitHub (Mar 18, 2022): > I got this to work by manually copying my own `.env` file into `packages/hoppscotch-app` using Docker That's great, but I think it should be implemented instead of workaround 😕

kerem commented

2026-03-16 16:57:18 +03:00

Author

Owner

@juandl commented on GitHub (Nov 28, 2022):

@liyasthomas this should not be closed, at this point, there's no wait to use a custom env if you use "docker-compose" example.

version: "3"

services:
  hoppscotch:
    image: hoppscotch/hoppscotch:latest
    container_name: hoppscotch
    pull_policy: always
    ports:
      - "4000:3000"
    restart: on-failure
    volumes:
      - ./app/.env:/app/packages/hoppscotch-app/.env

@juandl commented on GitHub (Nov 28, 2022): @liyasthomas this should not be closed, at this point, there's no wait to use a custom env if you use "docker-compose" example. ``` version: "3" services: hoppscotch: image: hoppscotch/hoppscotch:latest container_name: hoppscotch pull_policy: always ports: - "4000:3000" restart: on-failure volumes: - ./app/.env:/app/packages/hoppscotch-app/.env ```

kerem referenced this issue

2026-03-17 00:30:01 +03:00

[PR #736] [MERGED] chore(deps): bump nuxt-i18n from 6.8.0 to 6.8.1 #2830