Hello, thanks for the quick reply.
Well, the page (frontend) is dynamic and not static. That means I use Strapi here to maintain and exchange my content so that I don’t have to manually edit the code again or other people who are not familiar with code can maintain the website content afterwards. I absolutely agree with your statement if it were a static page but then I wouldn’t actually use Strapi because it wouldn’t be of any use to me. Here is an example of how I would like it:
In the frontend, I have a landing section that says, for example: “Hello user. Welcome”
In Strapi it would be the same because the page gets the content from there.
If I now change the content “Hello user. Welcome” to “Hello user. Welcome to my page”
Then, after the 4-hour cache from Cloudflare has expired, the content in the frontend should change to “Hello user. Welcome to my page”.
Unfortunately, this is not yet the case. In order for the content to change again, I currently have to rebuild my entire page, but this is not the desired behavior.
And as I said, to simulate the production mode, I started the page locally in a Docker container and everything worked fine just as intended.
Here is my Dockerfile
# build stage frontend
FROM node:18.16.0-alpine as build-stage-frontend
WORKDIR /frontend
COPY mb-sauna-website .
ARG STRAPI_URL
ENV VITE_VUE_APP_STRAPI_API_URL=$STRAPI_URL
RUN npm install
RUN npm run build
# Production stage
FROM node:18.16.0-alpine
WORKDIR /app
COPY --from=build-stage-frontend /frontend/.output /app
ARG STRAPI_URL
ENV VITE_VUE_APP_STRAPI_API_URL=$STRAPI_URL
ENV NODE_ENV=production
CMD node ./server/index.mjs