-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
POP - fundamental docs #28
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## handle_urls_mvp #28 +/- ##
=================================================
Coverage 100.00% 100.00%
=================================================
Files 6 5 -1
Lines 206 132 -74
=================================================
- Hits 206 132 -74
|
docs/intro/pop.rst
Outdated
|
||
.. code-block:: python | ||
|
||
from ecommerce_page_objects import RULES |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When deploying a POP behind an API, the separate deployment CLI-tool can have a configuration file that points to this entry point variable.
For example, such config file could be named pop.cfg
which is basically:
[deploy]
rules = ecommerce_page_objects.RULES
[projects]
dev = 123
prod = 7890
5eed2dc
to
8e805a7
Compare
Built on top of the branch from #27 which aims to define the minimum specifications/requirements to be a POP.