Граф коммитов

8 Коммитов

Автор SHA1 Сообщение Дата
Armen Zambrano deaf8c850c Bug 1169263 - Switch from Vagrant to docker-compose (#4901)
* Change permissions for docker/entrypoint.sh
* Allow using Django in localhost
* Documentation changes
Allow running shellcheck tests
Use docker-compose for the Selenium tests
Install docs updates
Switch to yarn cache instead of npm
Install UI dependencies
* Add ability to override DATABASE_URL and use a .env file
2019-05-16 14:56:02 -07:00
Ed Morley 6945c4c471
Bug 1165259 - Add infrastructure documentation (#4766)
- Adds a new "infrastructure" section to the docs, which describes
  architecture, administration and troubleshooting (fixes bug 1165259).
- Adds code comments to any deployment-related files in the repository.
- Adds documentation for the various ways in which users can access
  Treeherder data (fixes bug 1335172).
- Reorganises the structure of some of the existing non-infrastructure
  docs, to make the documentation easier to navigate.
2019-03-11 21:39:34 +00:00
Ed Morley a9e294704d Bug 1318295 - Vagrant: Remove the puppet provisioner
Since it's now a no-op.
2017-03-21 22:48:51 +00:00
Ed Morley d403b08b59 Bug 1318295 - Vagrant: Move APT setup steps to shell provisioner
Add the setup script to a new `vagrant` directory in the root of the
repo, which will replace the `puppet` one.
2017-03-21 22:48:51 +00:00
Ed Morley 8375a4aa02 Bug 1225154 - Remove out of date fig/docker configs
We will likely switch to a Docker based solution in the future, however
for now the configs are unused and out of date (fig has been replaced
with docker-compose, we no longer generate per-repo credentials etc).
In addition, there are tools that can convert the Heroku Procfile into
Docker configs, so we may end up using a solution based on that instead.

As such, let's remove the configs (they'll always be available in
version control history) to reduce the maintenance burden and clutter in
the repo.
2015-11-16 16:13:12 +00:00
Ed Morley a31174407a Bug 1207613 - Remove the dist/ directory from master
Heroku now generates it on deploy, and for stage/prod we generate it
fresh on the stage/prod branch and force push each time. As such, we
have no need for the directory on master, and by removing it we avoid
confusion when new contributors grep the repo.

As an added bonus, the stage/prod deploy script should fail if the dist
directory is missing, so the grunt build cannot be forgotten prior to
deploying. (Currently if it's forgotten, we end up deploying the ancient
dist directory from master that was last updated prior to us switching
to the new deployment strategy.)
2015-10-02 11:55:54 +01:00
Ed Morley 0c79292d68 Bug 1201523 - Run grunt build during the Heroku deploy
This commit relies on the nodejs buildpack being added to the list of
buildpacks for the app, and prior to the Python buildpack. See:
https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app

The nodejs buildpack will automatically install the packages listed in
`dependencies` in package.json, so that we have the requirements for
the grunt build. We don't actually need node or all of the files in
node_modules after we've run the grunt build, so in the future could try
and remove them to reduce the resultant slug size (though it only
increased from 55MB to 70MB, so it's not urgent).

The dist directory has been added to `.slugignore` to prevent the
in-repo directory from being uploaded, since we'll be generating a new
one as part of the deploy. Once `dist/` is deleted from master, that
entry can be removed.
2015-09-30 18:34:56 +01:00
Ed Morley eb8826d704 Bug 1198053 - Add a .slugignore file to reduce Heroku slug size
https://devcenter.heroku.com/articles/slug-compiler#ignoring-files-with-slugignore

This reduces slug size from 68.5MB to 52.6MB.
2015-08-25 01:28:48 +01:00