plain.dev 0.26.0__tar.gz → 0.26.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (32) hide show
  1. {plain_dev-0.26.0 → plain_dev-0.26.1}/PKG-INFO +4 -4
  2. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/README.md +3 -3
  3. {plain_dev-0.26.0 → plain_dev-0.26.1}/pyproject.toml +1 -1
  4. {plain_dev-0.26.0 → plain_dev-0.26.1}/.gitignore +0 -0
  5. {plain_dev-0.26.0 → plain_dev-0.26.1}/LICENSE +0 -0
  6. {plain_dev-0.26.0 → plain_dev-0.26.1}/README.md +0 -0
  7. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/__init__.py +0 -0
  8. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/cli.py +0 -0
  9. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/contribute/README.md +0 -0
  10. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/contribute/__init__.py +0 -0
  11. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/contribute/cli.py +0 -0
  12. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/debug.py +0 -0
  13. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/default_settings.py +0 -0
  14. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/entrypoints.py +0 -0
  15. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/gunicorn_logging.json +0 -0
  16. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/mkcert.py +0 -0
  17. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/pdb.py +0 -0
  18. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/poncho/__init__.py +0 -0
  19. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/poncho/color.py +0 -0
  20. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/poncho/compat.py +0 -0
  21. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/poncho/manager.py +0 -0
  22. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/poncho/printer.py +0 -0
  23. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/poncho/process.py +0 -0
  24. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/precommit/__init__.py +0 -0
  25. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/precommit/cli.py +0 -0
  26. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/requests.py +0 -0
  27. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/services.py +0 -0
  28. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/templates/dev/requests.html +0 -0
  29. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/urls.py +0 -0
  30. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/utils.py +0 -0
  31. {plain_dev-0.26.0 → plain_dev-0.26.1}/plain/dev/views.py +0 -0
  32. {plain_dev-0.26.0 → plain_dev-0.26.1}/tests/settings.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: plain.dev
3
- Version: 0.26.0
3
+ Version: 0.26.1
4
4
  Summary: Local development tools for Plain.
5
5
  Author-email: Dave Gaeddert <dave.gaeddert@dropseed.dev>
6
6
  License-Expression: BSD-3-Clause
@@ -22,7 +22,7 @@ A single command that runs everything you need for local development.
22
22
 
23
23
  ![Plain dev command example](https://github.com/dropseed/plain/assets/649496/3643bb64-a99b-4a8e-adab-8c6b81791ea9)
24
24
 
25
- The `plain.dev` package can be [installed from PyPI](https://pypi.org/project/plain.dev/), and does *not* need to be added to `INSTALLED_PACKAGES`.
25
+ The `plain.dev` package can be [installed from PyPI](https://pypi.org/project/plain.dev/), and does _not_ need to be added to `INSTALLED_PACKAGES`.
26
26
 
27
27
  - [`plain dev`](#plain-dev)
28
28
  - [`plain dev services`](#plain-dev-services)
@@ -44,7 +44,7 @@ The `plain dev` command does several things:
44
44
 
45
45
  ### Services
46
46
 
47
- Use services to define databases or other processes that your app *needs* to be functional. The services will be started automatically in `plain dev`, but also in `plain pre-commit` (so preflight and tests have a database).
47
+ Use services to define databases or other processes that your app _needs_ to be functional. The services will be started automatically in `plain dev`, but also in `plain pre-commit` (so preflight and tests have a database).
48
48
 
49
49
  Ultimately, how you run your development database is up to you. But a recommended starting point is to use Docker:
50
50
 
@@ -56,7 +56,7 @@ postgres = {cmd = "docker run --name app-postgres --rm -p 54321:5432 -v $(pwd)/.
56
56
 
57
57
  ### Custom processes
58
58
 
59
- Unlike [services](#services), custom processes are *only* run during `plain dev`. This is a good place to run something like [ngrok](https://ngrok.com/) or a [Plain worker](../../../plain-worker), which you might need to use your local site, but don't need running for executing tests, for example.
59
+ Unlike [services](#services), custom processes are _only_ run during `plain dev`. This is a good place to run something like [ngrok](https://ngrok.com/) or a [Plain worker](../../../plain-worker), which you might need to use your local site, but don't need running for executing tests, for example.
60
60
 
61
61
  ```toml
62
62
  # pyproject.toml
@@ -4,7 +4,7 @@ A single command that runs everything you need for local development.
4
4
 
5
5
  ![Plain dev command example](https://github.com/dropseed/plain/assets/649496/3643bb64-a99b-4a8e-adab-8c6b81791ea9)
6
6
 
7
- The `plain.dev` package can be [installed from PyPI](https://pypi.org/project/plain.dev/), and does *not* need to be added to `INSTALLED_PACKAGES`.
7
+ The `plain.dev` package can be [installed from PyPI](https://pypi.org/project/plain.dev/), and does _not_ need to be added to `INSTALLED_PACKAGES`.
8
8
 
9
9
  - [`plain dev`](#plain-dev)
10
10
  - [`plain dev services`](#plain-dev-services)
@@ -26,7 +26,7 @@ The `plain dev` command does several things:
26
26
 
27
27
  ### Services
28
28
 
29
- Use services to define databases or other processes that your app *needs* to be functional. The services will be started automatically in `plain dev`, but also in `plain pre-commit` (so preflight and tests have a database).
29
+ Use services to define databases or other processes that your app _needs_ to be functional. The services will be started automatically in `plain dev`, but also in `plain pre-commit` (so preflight and tests have a database).
30
30
 
31
31
  Ultimately, how you run your development database is up to you. But a recommended starting point is to use Docker:
32
32
 
@@ -38,7 +38,7 @@ postgres = {cmd = "docker run --name app-postgres --rm -p 54321:5432 -v $(pwd)/.
38
38
 
39
39
  ### Custom processes
40
40
 
41
- Unlike [services](#services), custom processes are *only* run during `plain dev`. This is a good place to run something like [ngrok](https://ngrok.com/) or a [Plain worker](../../../plain-worker), which you might need to use your local site, but don't need running for executing tests, for example.
41
+ Unlike [services](#services), custom processes are _only_ run during `plain dev`. This is a good place to run something like [ngrok](https://ngrok.com/) or a [Plain worker](../../../plain-worker), which you might need to use your local site, but don't need running for executing tests, for example.
42
42
 
43
43
  ```toml
44
44
  # pyproject.toml
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "plain.dev"
3
- version = "0.26.0"
3
+ version = "0.26.1"
4
4
  description = "Local development tools for Plain."
5
5
  authors = [{name = "Dave Gaeddert", email = "dave.gaeddert@dropseed.dev"}]
6
6
  license = "BSD-3-Clause"
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes