зеркало из https://github.com/mozilla/fxa.git
c6d3ce8741
Because: - at least one of the build processes creates a 'tmp' directory in the project root directory, which would cause the mono build script to fail - this is not an issue in CI since its starting state is clean but locally if the monorepo's been built before this becomes an issue This commit: - renames the temporary file name slightly |
||
---|---|---|
.. | ||
docker | ||
firebase | ||
goaws | ||
pm2 | ||
.prettierrc | ||
.stylelintrc | ||
README.md |
README.md
_dev
This directory contains files to support local development that aren't needed in production, especially things that would otherwise clutter up the root directory.
docker
There are a couple different docker files for the mono repo:
- **docker/ci** - This controls the creation of a base image used for CI pipelines. The goal of this image is to offer quick install and start up times of the fxa project.
- **docker/ci-lockfile-generator** - This is a developer utility, and acts as mechanism / sanity check against yarn lock file mismatches. Prior to yarn 3.3.0 some systems would encounter bad hashes in yarn lock file. In case this ever resurfaces, we will leave this file here.
- **docker/ci/mono** - This file builds a deployable version of the mono repo. It houses all available services in one image. Services can be targeted as needed.