anyproto / anyproto/any-sync-dockercompose

Instructions for Portainer

Open
#164 10 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
941
Forks
134
Avg merge
2d 21h
Merged PRs (30d)
3

Description

Have you read a contributing guide?
  • I have read CONTRIBUTING.md
  • I have searched the existing requests and didn't find any that were similar
  • I have considered creating a pull request instead and want to proceed
Clear and concise description of the problem

I'm trying to setup AnyType for Personal use in my local home network in Portainer.
I already got the Custom Template which pulls the docker-compose.yml from here basically:
https://github.com/anyproto/any-sync-dockercompose/blob/main/docker-compose.yml

The Git Settings look like this:
Image

But when I try to deploy a Stack from the Template, it looks like this:
Image

I'm assuming I'll have to add environment variables for the Volume Z mentioned in the compose-file, but to be completely honest with you, I don't get the Instructions in the Wiki nor do I get the instructions on how to use the env.override file, especially when not setting this up in the Terminal but in Portainer. I can give it an .env file or configure variables manually, but I do not see an option to add or configure .env.override files.

Suggested solution

Can you please add instructions on what variables are mandatory to set and how to set them when using any GUI Frontend for Docker-Compose like Portainer Template and Stacks or the Synology Container Manager Projects?

Alternative

Any alternative solution that would enable me to deploy a working stack of AnyType on my local home server using a template pulled from github like you can see above in the "Clear and concise description of the problem" Section.

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docker-compose.yml and the existing Wiki instructions, then compare how Portainer Templates and Stacks and Synology Container Manager Projects accept environment variables. Done means documenting the mandatory variables and explaining how to provide the env.override settings through these GUI workflows, or documenting a working alternative deployment path.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.