gray flame Apr 1, 2024, 7:28 PM

#

I'm having an issue with the apis in my docker and apis. in my confg i have
adapter: node({
mode: "standalone",
output: "server",

I have the .env file in the docker compose files. for example im using umami for analytics in a file called umami.astro. i've added this to the main layout. i also have a livechat with using the same approach

const UMAMI_ANALYTICS_KEY = import.meta.env.UMAMI_ANALYTICS_KEY;
const PUBLIC_UMAMI_URL = import.meta.env.PUBLIC_UMAMI_URL;

const PUBLIC_TIDIO_KEY = import.meta.env.PUBLIC_TIDIO_KEY;

Then i have both google autofill for addresses and web3forms for forms

const { GOOGLE_AUTOFILL, WEB_3_FORMS_ACCESS_KEY } = import.meta.env;

I've tried everything to get this to work and it shows in the docker image that those variables have been added but nothing is working...

cerulean cliff Apr 1, 2024, 7:41 PM

#

is the .env file available at build-time?

#

for context, neither astro not node automatically read .env files at runtime

gray flame Apr 1, 2024, 7:42 PM

#

Base stage for shared environment setup

FROM node:lts-slim as base

Set the working directory

WORKDIR /app

RUN mkdir -p /app/src

Install essential tools

RUN apt-get update && apt-get install -y curl && rm -rf /var/lib/apt/lists/*

COPY package.json package-lock.json ./

Install dependencies, then remove unnecessary packages to keep the image slim

FROM base as dependencies
RUN npm install && npm cache clean --force
RUN npx <@&1055234544183287879>/upgrade

Dependencies installation for production

FROM base AS prod-deps
RUN npm install --production

Building the application

FROM base AS build
COPY . .
RUN npm install
RUN npm run build

Final stage for the production environment

FROM node:lts-slim as runtime
WORKDIR /app

Copy production dependencies

COPY --from=prod-deps /app/node_modules ./node_modules

Copy built files necessary for running the application

COPY --from=build /app/dist ./dist

Copy the config.yaml file to the expected location within the Docker image

COPY src/config.yaml /app/src/config.yaml

Set environment variables for the host and port, if necessary

ENV HOST=0.0.0.0
ENV PORT=4321

Expose the port the app runs on

EXPOSE 4321

Command to run the application

CMD ["node", "./dist/server/entry.mjs"]

#

I dont think so?

cerulean cliff Apr 1, 2024, 7:44 PM

#

the only treatment files named .env is where all occurrences of import.meta.env.X are replaced in the compiled code with the value of X in that file

#

so you would have to make sure that it is abailable to astro at compile-time

gray flame Apr 1, 2024, 7:45 PM

#

how do i do this

#

im sorry im so confused about the whole process

#

im new to astro

#

i spent the better half of two weeks developing the site and now this is the final issue haha

cerulean cliff Apr 1, 2024, 7:45 PM

#

how are copying the .env file into the docker image now?

gray flame Apr 1, 2024, 7:45 PM

#

i use docker compose

#

version: '3.8'

services:
web:
restart: always
container_name: web
image: ghcr.io/devkolt/epw-web:latest
ports:
- "4321:4321"
env_file:
- .env
labels:
- com.centurylinklabs.watchtower.enable=true
networks:
- cloudflared_tunnel

networks:
cloudflared_tunnel:
external: true

cerulean cliff Apr 1, 2024, 7:46 PM

#

at what stage (prod-deps, build, final) is it copied in?

gray flame Apr 1, 2024, 7:46 PM

#

final

cerulean cliff Apr 1, 2024, 7:46 PM

#

it would have to be build

gray flame Apr 1, 2024, 7:47 PM

#

build

#

but then it would be in the docker image?

#

i thought this was during the docker compose stage

cerulean cliff Apr 1, 2024, 7:48 PM

#

yes, if you want the variables to be read from the file at runtime and only during runtime, you will use node's --env-file flag

#

and refer to the variable using process.env instead of import.met.env

gray flame Apr 1, 2024, 7:49 PM

#

oh

#

so ill i do is switch the import.met.env to process.env and keep everything else the same

cerulean cliff Apr 1, 2024, 7:49 PM

#

code-wise, yes

#

build-script-wise, you also add the flag to node cli i mentioned earlier

gray flame Apr 1, 2024, 7:50 PM

#

in the dockerfile?

cerulean cliff Apr 1, 2024, 7:50 PM

#

.env files are not read by node by default

cerulean cliff Apr 1, 2024, 7:50 PM

#

gray flame in the dockerfile?

yes, it seems to be the last line

gray flame Apr 1, 2024, 7:51 PM

#

just after this? ENV HOST=0.0.0.0
ENV PORT=4321

cerulean cliff Apr 1, 2024, 7:53 PM

#

no, a couple of lines after it, inside the CMD line

gray flame Apr 1, 2024, 7:53 PM

#

do i need to flag the actual .env with api values or create an example

cerulean cliff Apr 1, 2024, 7:54 PM

#

this might help
https://nodejs.org/en/learn/command-line/how-to-read-environment-variables-from-nodejs

Node.js — How to read environment variables from Node.js

Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.

gray flame Apr 1, 2024, 7:54 PM

#

kk

#

thx!!

cerulean cliff Apr 1, 2024, 7:54 PM

#

good luck!

gray flame Apr 1, 2024, 8:04 PM

#

import path from "path";
import { fileURLToPath } from "url";

const __dirname = path.dirname(fileURLToPath(import.meta.url));

/** */
export const getProjectRootDir = (): string => {
const mode = import.meta.env.MODE;

return mode === "production"
? path.join(__dirname, "../")
: path.join(__dirname, "../../");
};

const __srcFolder = path.join(getProjectRootDir(), "/src");

/** */
export const getRelativeUrlByFilePath = (filepath: string): string => {
return filepath.replace(__srcFolder, "");
};
do i need to add or change the import.meta.env from this file directories.ts to process.env

#

and should i be installing dotenv

cerulean cliff Apr 1, 2024, 8:06 PM

#

gray flame import path from "path"; import { fileURLToPath } from "url"; const __dirname =...

no, because mode is not provided by the env file, its provided by astro

gray flame Apr 1, 2024, 8:07 PM

#

okay

cerulean cliff Apr 1, 2024, 8:07 PM

#

gray flame and should i be installing dotenv

no, because the --env-file flag is basically dotenv's functionality recently built right into node

#

if you have a recent version of node, dotenv is no longer necessary

gray flame Apr 1, 2024, 8:08 PM

#

okay okay

#

so for the docker file i changed it to # Set environment variables for the host and port, if necessary
ENV HOST=0.0.0.0
ENV PORT=4321

Expose the port the app runs on

EXPOSE 4321

Command to run the application

CMD ["node", "--env-file=.env", "app.js"]

FROM

#

Expose the port the app runs on

EXPOSE 4321

Command to run the application

CMD ["node", "./dist/server/entry.mjs"]

#

And i changed the files to ---
const UMAMI_ANALYTICS_KEY = process.env.UMAMI_ANALYTICS_KEY;
const PUBLIC_UMAMI_URL = process.env.PUBLIC_UMAMI_URL;

cerulean cliff Apr 1, 2024, 8:09 PM

#

gray flame # Expose the port the app runs on EXPOSE 4321 # Command to run the application ...

im guessing you would --env-file for this CMD as well

gray flame Apr 1, 2024, 8:10 PM

#

?

#

im so confused sorry

cerulean cliff Apr 1, 2024, 8:11 PM

#

you pasted two dockerfiles

#

one that runs app.js

#

another that runs dist server entry.mjs (astro's compiled code)

#

you had the flag in the first dockerfile but not in the second

#

im guessing you would need the variables from .env file in both, not just the first

gray flame Apr 1, 2024, 8:13 PM

#

this is the current one

#

Base stage for shared environment setup

FROM node:lts-slim as base

Set the working directory

WORKDIR /app

RUN mkdir -p /app/src

Install essential tools

RUN apt-get update && apt-get install -y curl && rm -rf /var/lib/apt/lists/*

COPY package.json package-lock.json ./

Install dependencies, then remove unnecessary packages to keep the image slim

FROM base as dependencies
RUN npm install && npm cache clean --force
RUN npx <@&1055234544183287879>/upgrade

Dependencies installation for production

FROM base AS prod-deps
RUN npm install --production

Building the application

FROM base AS build
COPY . .
RUN npm install
RUN npm run build

Final stage for the production environment

FROM node:lts-slim as runtime
WORKDIR /app

Copy production dependencies

COPY --from=prod-deps /app/node_modules ./node_modules

Copy built files necessary for running the application

COPY --from=build /app/dist ./dist

Copy the config.yaml file to the expected location within the Docker image

COPY src/config.yaml /app/src/config.yaml

Set environment variables for the host and port, if necessary

ENV HOST=0.0.0.0
ENV PORT=4321

Expose the port the app runs on

EXPOSE 4321

Command to run the application

CMD ["node", "--env-file=.env", "./dist/server/entry.mjs"]

#

i changed it to entry.mjs because it was not working in docker-compose after

#

docker is saying docker run --env-file .env.production -p 4321:4321 web:latest
node: .env: not found

cerulean cliff Apr 1, 2024, 8:18 PM

#

that means the env file (wherever it was) was not copied into the container

#

or maybe copied into a differnet folder

gray flame Apr 1, 2024, 8:19 PM

#

if i copy it to the container does that not mean the file could be compromised?

#

do i need to add something to this line # Copy built files necessary for running the application
COPY --from=build /app/dist ./dist

#

cerulean cliff Apr 1, 2024, 8:24 PM

#

gray flame if i copy it to the container does that not mean the file could be compromised?

yes, but you have to evaluate how realistic of a risk that is

#

because no matter how much you lock down the env file, ultimatelet it goes onto process.env and if theres a vulnerability process.env could itself become accessible

gray flame Apr 1, 2024, 8:25 PM

#

Do you know what needs to change specifically in the dockerfile because i asked gpt and its not going me a correct answer

cerulean cliff Apr 1, 2024, 8:25 PM

#

the typical way it is handled is by not putting it in the part of image

#

but by putting it inside the container everytime it is started

gray flame Apr 1, 2024, 8:26 PM

#

right, so usually i have it in the same directory as the docker compose file

cerulean cliff Apr 1, 2024, 8:26 PM

#

that could be done through a virtual mount (docker cli's -v flag) for example

gray flame Apr 1, 2024, 8:27 PM

#

but again its not reading the files correctly

#

So i've changed the dockerfile now but its not building correct

cerulean cliff Apr 1, 2024, 8:31 PM

#

i cant say about how it would be done docker compose, i havent used it

gray flame Apr 1, 2024, 8:32 PM

#

Okay

#

i'll try a few things

echo wasp Apr 5, 2024, 11:03 AM

#

Hi everybody ! Let me ask, does anyone know clearly about the partytown issue to optimize GTM loading?
But https://tagmanager.google.com/ preview mode cannot track datalayer

Google Analytics

Google Analytics lets you measure your advertising ROI as well as track your Flash, video, and social networking sites and applications.

coral eagle Jun 11, 2024, 10:37 PM

#

This should be more documented... I'm also new to Astro and having the same issues with Docker and ENV variables. I managed to deploy the Astro with docker and Kamal, but the ENV variables are missing...

#

docker run --detach --restart unless-stopped --name docker_image --hostname 10.x.x.x-f9658aad28a4 -e --env-file .env
The docker file runs with the --env-file

blazing zephyr Jun 11, 2024, 11:00 PM

#

I think the --env-file flag is only available in Node 20+ right? Is there an alternative method when one is stuck on v18?
Also, how would this work exactly when running Astro in dev mode (npm run dev)?

blazing zephyr Jun 11, 2024, 11:01 PM

#

coral eagle This should be more documented... I'm also new to Astro and having the same issu...

I agree that the documentation could be more extensive on this. I'm having trouble understanding the fundamentals of what's going on here as well.

coral eagle Jun 11, 2024, 11:10 PM

#

The ENV variables worked fine in development but still I'm still struggling to make them available during the build process. If I run printenv in the docker container, I can see the ENV variables are pushed inside the container.

#

I added these inside the Dockerfile

ENV API_KEY=$(cat /run/secrets/API_KEY) <----
ENV PASS=$(cat /run/secrets/PASS) <----
ENV HOST=0.0.0.0
ENV PORT=3000

EXPOSE 3000
CMD ["node", "$API_KEY", "$PASS", "./dist/server/entry.mjs"]

However, I'm getting this error:

ERROR: failed to solve: Syntax error - can't find = in "/run/secrets/API_KEY)". Must be of the form: name=value

coral eagle Jun 11, 2024, 11:43 PM

#

That didn't worked so I'm trying this...

RUN --mount=type=secret,id=API_KEY \
  API_KEY=$(cat /run/secrets/API_KEY)

RUN --mount=type=secret,id=PASS \
  PASS=$(cat /run/secrets/PASS)

ENV HOST=0.0.0.0
ENV PORT=3000

EXPOSE 3000
CMD ["node", "API_KEY=$API_KEY", "PASS=$PASS", "./dist/server/entry.mjs"]

Running docker buildx build --push --platform linux/amd64,linux/arm64 --builder 
  kamal-astro-multiarch -t registry.redacted.com/redacted/astro:redacted -t 
  registry.redacted.com/redacted/astro:latest 
  --label service="astro" --secret id="API_KEY" --secret id="PASS" --file Dockerfile . as user@localhost

#

The container is unhealthy with these settings... but the build was sucessfull

#

This worked. The secrets are pushed at build with docker secrets:
https://docs.docker.com/build/building/secrets/

FROM node:lts-alpine AS base
WORKDIR /app

# By copying only the package.json and package-lock.json here, we ensure that the following `-deps` steps are independent of the source code.
# Therefore, the `-deps` steps will be skipped if only the source code changes.
COPY package.json yarn.lock ./

RUN apk add --no-cache curl

FROM base AS prod-deps
RUN npm install --omit=dev

FROM base AS build-deps
RUN npm install

FROM build-deps AS build
COPY . .
RUN npm run build

FROM base AS runtime
COPY --from=prod-deps /app/node_modules ./node_modules
COPY --from=build /app/dist ./dist

RUN --mount=type=secret,id=API_KEY \
  API_KEY=$(cat /run/secrets/API_KEY)

RUN --mount=type=secret,id=PASS \
  PASS=$(cat /run/secrets/PASS)

ENV HOST=0.0.0.0
ENV PORT=3000

EXPOSE 3000
CMD API_KEY=$API_KEY PASS=$PASS node ./dist/server/entry.mjs

coral eagle Jun 12, 2024, 12:20 AM

#

pages/contact.astro

 const email = new Email({
      apiKey: process.env.API_KEY || import.meta.env.API_KEY,
      apiSecret:  process.env.PASS || import.meta.env.PASS,
 });

#

Everything works now... 🙂

turbid wagon Jun 24, 2024, 3:29 PM

#

coral eagle `pages/contact.astro` ``` const email = new Email({ apiKey: process.env.A...

I already hotfixed my astro project this way but like.. this cannot be the fix, right?

#.env file in docker dont working

const UMAMI_ANALYTICS_KEY = import.meta.env.UMAMI_ANALYTICS_KEY; const PUBLIC_UMAMI_URL = import.meta.env.PUBLIC_UMAMI_URL;

const PUBLIC_TIDIO_KEY = import.meta.env.PUBLIC_TIDIO_KEY;

const { GOOGLE_AUTOFILL, WEB_3_FORMS_ACCESS_KEY } = import.meta.env;

Base stage for shared environment setup

Set the working directory

Install essential tools

Install dependencies, then remove unnecessary packages to keep the image slim

Dependencies installation for production

Building the application

Final stage for the production environment

Copy production dependencies

Copy built files necessary for running the application

Copy the config.yaml file to the expected location within the Docker image

Set environment variables for the host and port, if necessary

Expose the port the app runs on

Command to run the application

Expose the port the app runs on

Command to run the application

Expose the port the app runs on

Command to run the application

And i changed the files to --- const UMAMI_ANALYTICS_KEY = process.env.UMAMI_ANALYTICS_KEY; const PUBLIC_UMAMI_URL = process.env.PUBLIC_UMAMI_URL;

Base stage for shared environment setup

Set the working directory

Install essential tools

Install dependencies, then remove unnecessary packages to keep the image slim

Dependencies installation for production

Building the application

Final stage for the production environment

Copy production dependencies

Copy built files necessary for running the application

Copy the config.yaml file to the expected location within the Docker image

Set environment variables for the host and port, if necessary

Expose the port the app runs on

Command to run the application

const UMAMI_ANALYTICS_KEY = import.meta.env.UMAMI_ANALYTICS_KEY;
const PUBLIC_UMAMI_URL = import.meta.env.PUBLIC_UMAMI_URL;

And i changed the files to ---
const UMAMI_ANALYTICS_KEY = process.env.UMAMI_ANALYTICS_KEY;
const PUBLIC_UMAMI_URL = process.env.PUBLIC_UMAMI_URL;