We might need to document how the logs are gathered inside our images and how this can be configured or integrated in a docker landscape.

Related: webdevops/Dockerfile#242

The .env file is by default ignored in git therefore it usually requires manual process when D4D is updated.

In my case the only thing that stays the same is project name and base url, everything else could easily be replaced and revisioned in git.

Should we find a more optimal way to deal with this or do you have some alternatives?

This is not so much a bug as it is a modest suggestion.
The documentation mentioned Configure Domains almost in passing. Should be more strongly emphasized. The .env file for example lists mariadb as here in it's definitions:
DB_NAME=wordpress
DB_USER=wordpress
DB_PASSWORD=w

what

When using Teleport tsh login to connect to a cluster, although kubectl works fine, kops does not, because, in general, the Teleport name of the cluster is not the same as the kops cluster name. This leads to an error like

 ⧉  staging (staging:default)+
 √ : (cpco-staging-admin) helmfiles ⨠ kops validate cluster
Validating cluster us-west-2.staging.cpco.io

Cannot load k

Context

What are you trying to do and how would you want to do it differently? Is it something you currently you cannot do? Is this related to an issue/problem?
Would like to clean the README and create a doc website for using this image.
There is too many sections in the README explaining the different usecases...

Perhaps a doc website using VuePress...

This bastion host is bloody useful and will save our team an enormous effort, thanks!

I had a little trouble working out how to run this on ECS so I'm posting my cloudformation template here for anyone that is looking to do the same:

AWSTemplateFormatVersion: 2010-09-09
Description: Bastion

Parameters:

  KeyPairName:
    Description: >-
      Enter a Public/private key pair. If

This is mainly towards the Nextcloud dockerfile:

Instead of assuming nextcloud is always served under foobar.com/, it would be great to let user specify a custom path at run time, e.g.

foobar.com/nextcloud/ OR foobar.com/custom-path/nextcloud/

These are the kernel options required that are missing from the latest vagrant box kernel:

• CONFIG_BRIDGE_NETFILTER
• CONFIG_NETFILTER_XT_MATCH_IPVS
• CONFIG_IP_NF_TARGET_REDIRECT
• CONFIG_EXT3_FS_XATTR
• CONFIG_VXLAN
• CONFIG_NF_NAT_TFTP
• CONFIG_NF_CONNTRACK_TFTP
• CONFIG_AUFS_FS
• `

When checking this site for the EOL information for a given tool, it's unclear when the page was last modified and thus if the information is current or out of date which seems somewhat antithetical to the purpose of this project.

Ideally the Last Modified date would be generated programmatically, but at the very least could be hard coded on each page and made a requirement for merging any pu

https://github.com/jkarlosb/git-server-docker/blob/72f69a5d6b8e719d0c8120f076097a27100ed366/Dockerfile#L14

Are you sure you don't want to do this conditionally in start.sh? With this, every container created with this image will have the same ssh host key which is bad.

I'm trying to use this to do local development since our org locks down our AWS account (even our dev). If it isn't deployed through our ops terraform and scripts it can't interact with AWS. This means that the AWS CLI is impractical. Hence, this image is a godsend for individuals like me who are forced to mock AWS services.

The problem I'm running into is that all of my .NET Core usage of the