Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Additional config for Docker and AWS hosting (#1298)
* aws action * aws action * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * github actions * modified dockerfile * modified requirements to include pytest libs also * modified requirements to include pytest libs also * added deploy script for dev * no cache for compose build * no cache for compose build * updated coaster * nginx path corrected * makefile in assets * coaster * updated requirements * updated requirements * updated requirements * updated requirements * requirements file for tests updated * requirements file for tests updated * requirements file for tests updated * disabled worker container in docker compose * disabled worker container in docker compose * added a new runtests version for docker called docker-tests.sh * added a new runtests version for docker called docker-tests.sh * added a new runtests version for docker called docker-tests.sh * added a new runtests version for docker called docker-tests.sh * added a new runtests version for docker called docker-tests.sh * added a new runtests version for docker called docker-tests.sh * added a container restart flag for postgres * added a container restart flag for postgres * added a container restart flag for postgres * added a container restart flag for postgres * added a container restart flag for postgres * disabling dbconfig in tests * disabling dbconfig in tests * disabled tests * disabled tests * buildx fix * buildx fix * buildx fix * ssh deploy * ssh deploy * ssh deploy * ssh deploy * ssh deploy * ssh deploy * ssh deploy * ssh deploy * ssh deploy * ssh deploy * ssh action added to yml * ssh action added to yml * tests added back * tests added back * Update testanddeploy.yml reinstated tests * hot reloading enabled + tests * added credentials as secrets * disabled tests until credentials are updated * fixed yml error * replaced s3 env with github secrets * pre-commit fixes * uwsgi+streamlining docker compose * added dev docker-compose * fixing staging deployment in github actions * fixing staging deployment via github actions * write permission on mount in staging deployment * working on fixing the settings.py issue * replaced s3 container env with github secrets * fixing path on settings.py * bind instance folder to host directory * updating yml for mounting * replacing docker run with docker-compose for flask db upgrade * Update testanddeploy.yml * enabled the autodeploy flow but disabled the tests * precommit * deploy * staging deployment via fabric * staging deployment via fabric * staging deployment via fabric * pre-commit fixes * pre-commit fixes * Legacy funnel redirects not relevant here; sort files * Generate hashes for requirements * Change Docker base image (untested) * Update pre-commit config * Add .dockerignore. Update Dockerfile for funnel. Add Dockerfile for funnel builder * Build and run test containers * Small changes to make runtests.sh self-sufficient * Replace docker-compose-test.yml with docker-compose-ci.yml * Removes entrypoint for CI tests, which was being used earlier to bypass failure in directly running pytest. docker-tests.sh is no longer required. Turns off TTY for CI tests, as CI output do not support it * Switches image base to nikolaik/python-node * Separate repo modules from local folder in isort (#1709) * Change cookie serializer (#1710) Funnel's cookie serializer used JWT, which was removed from itsdangerous, forcing us to pin the old version. We could not switch to another JWT implementation because our key rotation wrapper only works with itsdangerous. Rather than extend key rotation to another library, with fragile tests, we've opted to switch to a supported serializer in itsdangerous. This switch will invalidate all existing cookies, forcing a re-login for all users. A corresponding change in hasgeek/flask-lastuser#66 is required for all apps hosted in subdomains of Funnel. In addition, RQ Dashboard now requires config on register and so has a new init function. Flask 2.3 no longer supports the `before_first_request` callback, so the blueprint must expect config from the app when first registered on it. * Basic working dev setup on docker * Remove watchdog * Consolidated all docker operations in a single set of Dockerfile and docker-compose.yml files * Backup to disable github workflow testanddeploy.yml * Add PYTHONOPTIMIZE=2 for docker production and test; PYTHONDONTWRITEBYTECODE=1 PYTHONDEVMODE=1 for docker dev * First attempt to run tests on GHA using docker * Backup pytest.yml GHA, so as to not run it * Attempt to run tests on docker * Remove --link from all COPY commands in Dockerfile * Enable usage of gha cache for docker builds on GHA * Remove unnecessary docker compose up options and docker compose down action from docker-ci-test make target * Do not restart funnel-test service on completion of run * Try out local caching - one of the options in docker's gha caching documentation * Replicate steps from the pytest github action, including publishing of coverage; try using gha cache for pip_ cache * Set permissions for coverage folder * Empty commit to re-run docker tests * Basic setup to run funnel from production container using uwsgi; Remove PYTHONDONTWRITEBYTECODE=1 from dev container * Remove obsolete files * Remove PYTHONDEVMODE=1 and PYTHONOPTIMIZE=2 from Dockerfile * Remove FLASK_REDIS_URL from sample.env * Try new docker CI test setup on GHA * Build image before using compose in Docker pytest GHA workflow * Correction in ci.Dockerfile * Added entrypoint for test container and made pulls quite in make target docker-ci-test * Corrections in docker compose file * Corrections in CI docker tests setup * Undo version downgrades; restore pytest and drop testanddeploy in Github Actions * Add Dockerfile linter to pre-commit checks * Reformat Dockerfiles to pass linter check * Add Hadolint for Dockerfile linting * Update pre-commit hadolint hook * Blanket changes for new docker CI setup * Changes made to Dockerfile for bases * Attempt to use resolve cache bind mounts' ownership issues for docker CI setup * Remove obsolete files * Remove OBJC_DISABLE_INITIALIZE_FORK_SAFETY from docker setup; do not run db migration in dev entrypoint --------- Co-authored-by: vivekdurai <vivek@lexaude.com> Co-authored-by: Mitesh Ashar <email@miteshashar.com>
- Loading branch information