Make decider git hub work with Portainer

[KenK73]

I am having an issue trying to deploy a decider container using Portainer. I am using the repository option and selecting refs/tags/3.0.0 as the repository reference. I have to change the compose path to docker-compose.yaml (defaults to .yml) and things appear to go smoothly until it starts looking for the .env file. The docker-compose.yaml is set to .env and that does not exist. I dont know how to override that and make it use the .env.docker file or if thats even possible.

As it is right now, I just get a deployment error:

failed to deploy a stack: Failed to load /data/compose/45/2cb162c6dfa6444e4f2571424bfe9cefa98aa907/.env: open /data/compose/45/2cb162c6dfa6444e4f2571424bfe9cefa98aa907/.env: no such file or directory

[damionmounts]

Hello!
I have not used Portainer myself - but this should point you in the right direction.

Instead of using the 3.0.0 tag, just use the develop branch, it is the latest stable code.

Portainer has a facility around setting environment variables.

Take .env.docker and fill in DB_ADMIN_PASS, DB_KIOSK_PASS, CART_ENC_KEY, APP_ADMIN_PASS - that is what you'll need to recreate in the env setting feature. (Those fields can all be set to a even, just the simplest thing for testing now)

[KenK73]

Hello and thanks for the reply.

I have tried a couple different branches, including the develop. I also have pulled down the project and uploaded the contents of env.docker file to fill in all of the variables. I still have the issue where it complains about the missing ,env file. I think as long as that file is referenced in the docker-compose.yaml, it's going to fail deployment.

I see 3 paths:

1. Create the .env file
2. Set the docker-compose.yaml to use env.docker
3. Set the docker compose to use stack.env so it uses the variables uploaded in Portainer

Since all of these options require editing files in the project, I am guessing I will need a fork of my own to make it work. Unless someone can tell me how to get Portainer to override a setting.

[damionmounts]

Before I forget - You need to copy the default_config folder contents into the config folder before docker launch. (see docker instructions in readme). Honestly a fork may be the easiest way to do it (unless somebody jumps in here). Please keep me posted!

…

On Thu, Feb 8, 2024, 11:44 AM KenK73 ***@***.***> wrote: Hello and thanks for the reply. I have tried a couple different branches, including the develop. I also have pulled down the project and uploaded the contents of env.docker file to fill in all of the variables. I still have the issue where it complains about the missing ,env file. I think as long as that file is referenced in the docker-compose.yaml, it's going to fail deployment. I see 3 paths: 1. Create the .env file 2. Set the docker-compose.yaml to use env.docker 3. Set the docker compose to use stack.env so it uses the variables uploaded in Portainer Since all of these options require editing files in the project, I am guessing I will need a fork of my own to make it work. Unless someone can tell me how to get Portainer to override a setting. — Reply to this email directly, view it on GitHub <#75 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHP2K7MZU226M4V3TD625WDYST6IBAVCNFSM6AAAAABC7DWRKWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMBZHA2DA> . You are receiving this because you commented.Message ID: ***@***.***>

[KenK73]

Well thanks for your continued interest in my problem.

What I ended up doing was copying the project to our internal Gitlab server and making the changes I needed there. To start, I moved the .env.docker to .env and edited it with my settings. On the decider-web container I mounted a volume where I had already copied the default_config contents. After that it built fine on my primary portainer server, but there is some issue when trying to build decider-web on a portainer running an agent. Once I had the image built on the primary, I just exported it to the secondary and replaced all the build: info on the decider-web with the image name.

Not as painless as I had hoped, but it's working. I am curious as to why there is no .env? Even an empty file with just a comment in it or all the settings commented out would make this a non-issue.

[damionmounts]

As it stands - having no .env by default, and .gitignoring it, 100% ensures that somebody won't accidentally commit their credentials.

While it sadly clashes with some other tooling at times, creating .env is (mostly) simple as copying .env.[manual, docker] and filling fields.

It would be nice to create a baseline .env as you suggested - but git can be hairy with ignoring changes to an existing file. Tracked files still have changes tracked, even if they get added to a .gitignore. There are also git update-index --assume-unchanged and git update-index --skip-worktree, but these don't automatically apply on clone for others. Deliberate separation of provided defaults and user-edited files/folders has worked well so far.

I am interested if you have a solution to this problem (that doesn't rely on manual user actions).

Glad it ended up working out for you in the end though!