Django-simple-deploy

Latest version: v0.6.1

Safety actively analyzes 623465 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 9

0.6.1

External changes

- Fixes some issues managing Fly and Platform.sh CLI usage on Ubuntu and macOS.

0.6

---

0.6.0

Deployments should work on all three platforms, for all major OSes. Any fixes from this point should be much more minor bugfixes, rather than rethinking the overall approach. This should be a transition to 1.0.

External changes

- Detects missing Heroku CLI on Ubuntu.
- Creates a Postgres databse on Heroku as needed.
- Updates roadmap.

Internal changes

- Starts to use `--json` on some Heroku CLI calls.

0.5.18

Stabilize deployments to Fly.io. Previously, deployment to Fly.io would fail if you already had an app deployed on Fly. This release addresses that issue, and significantly improves the process for deploying to Fly.

External changes

- Shows all the user's undeployed apps on Fly.io, and gets confirmation that the correct app to deploy to has been chosen.
- If a database is found with a name matching the selected app, gets confirmation that it's okay to use that database.
- Updates all messages related to Fly.io deployments.

Internal changes

- Updated readthedocs config file.
- Fly `deploy.py` file is longer, and needs some refactoring.

0.5.17

Improve logging to include all project inspection steps. This should help with development and troubleshooting.

External changes

- Logs all system and project inspection steps.

Internal changes

- Creates log file immediately, unless `--skip-logging` is used. Previously, a log file wasn't written until we were writing other changes to the project.
- Implements `SimpleDeployCommandError`, which logs the error before raising `CommandError`. `CommandError` should not be used, unless the error output contains sensitive information.
- Implements `log_info()` method, which only logs information without writing it to the console.

0.5.16

Deployment to Platform.sh should be stable. Resumes preliminary support for Fly.io. Heroku deployment is probably broken for new users.

External changes

- Updates to documentation:
- Updated information in Choosing a Platform.
- Many smaller documentation improvements from multiple people looking closely at docs.
- Started official documenation for integration tests.
- Fly.io:
- Assumes you have no existing Fly apps.
- Identifies lowest-latency region to deploy to; defaults to 'sea' if that information is unattainable.
- Deprecate use of `flyctl`; use `fly` consistently throughout.
- Heroku:
- Uses `'*'` for `ALLOWED_HOSTS` on Heroku, as a temp fix.

Internal changes

- Added `.venv` to `.gitignore`, so developers don't have to use `dsd_env`.
- Unit tests:
- No longer use shell scripts;
- Check for Poetry and Pipenv before running;
- No longer require any platform's CLI to be installed;
- Fixed `rum` mispelling of `rm` in unit tests using Poetry, which should improve accuracy of unit testing when using Poetry.
- Pass on Windows as well as macOS and Linux.
- Add `simple_deploy` to Poetry and Pipenv requirements for fly configurations.
- Integration tests
- Converts most existing functionality in integration tests from shell scripts that only work on macOS/ Linux, to cross-platform functionality.
- Prints summary of functionality tests.
- Other changes
- Validates pytest call, to run either unit tests or integration tests, not both. Also require `-s` for integration tests.
- New tool for standing up a dev environment: `build_dev_env.py`
- Started less formal notes about each platform, in *developer_resources/*.
- On Fly deployments, updates `fly open` calls to `fly apps open -a <app-name>`. Also updates deprecated `fly regions list -a` to get region with lowest latency.

Page 1 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.