How to use env file on docker image and have a persistent JSON file

[dan]

@rangaka

Is there a way around this?

Well, you’d need to define persistent storage for your software, and store the JSON file there. As to the .env file, the easiest way to do that IMO is to use the Dockge app, and then use that to manage any other containers:

Dockge

The other possibility is by including other files in your custom app definition, as described here:

Electric Eel - How I am using Dockerfile, .env files, compose files

So, an earlier discussion noted the limitations of Eel regarding not being able to edit after uploading them via create custom app, inability to use .env files, and, needing to keep Dockerfiles elsewhere via a full path build context. I have solved all that, for the way I want to do it at least. Let’s see if anyone likes. Here is a caddy reverse proxy setup with custom plugins (porkbun dns and labels) where I illustrate: Dockerfile: FROM caddy:2-builder AS builder RUN xcaddy build \ --with …