|
|
|
@ -343,41 +343,51 @@ script is available. Note that you don't need to set ``FLASK_APP``. ::
|
|
|
|
|
PyCharm Integration |
|
|
|
|
------------------- |
|
|
|
|
|
|
|
|
|
The new Flask CLI features aren't yet fully integrated into the PyCharm IDE, |
|
|
|
|
so we have to do a few tweaks to get them working smoothly. These instructions |
|
|
|
|
should be similar for any other IDE you might want to use. |
|
|
|
|
The Flask CLI features aren't yet fully integrated into the PyCharm IDE, |
|
|
|
|
so we have to do a few tweaks to get them working smoothly. These |
|
|
|
|
instructions should be similar for any other IDE you might want to use. |
|
|
|
|
|
|
|
|
|
In PyCharm, with your project open, click on *Run* from the menu bar and go to |
|
|
|
|
*Edit Configurations*. You'll be greeted by a screen similar to this: |
|
|
|
|
In PyCharm, with your project open, click on *Run* from the menu bar and |
|
|
|
|
go to *Edit Configurations*. You'll be greeted by a screen similar to |
|
|
|
|
this: |
|
|
|
|
|
|
|
|
|
.. image:: _static/pycharm-runconfig.png |
|
|
|
|
:align: center |
|
|
|
|
:class: screenshot |
|
|
|
|
:alt: screenshot of pycharm's run configuration settings |
|
|
|
|
:align: center |
|
|
|
|
:class: screenshot |
|
|
|
|
:alt: screenshot of pycharm's run configuration settings |
|
|
|
|
|
|
|
|
|
There's quite a few options to change, but once we've done it for one command, |
|
|
|
|
we can easily copy the entire configuration and make a single tweak to give us |
|
|
|
|
access to other commands, including any custom ones you may implement yourself. |
|
|
|
|
There's quite a few options to change, but once we've done it for one |
|
|
|
|
command, we can easily copy the entire configuration and make a single |
|
|
|
|
tweak to give us access to other commands, including any custom ones you |
|
|
|
|
may implement yourself. |
|
|
|
|
|
|
|
|
|
For the *Script* input (**A**), navigate to your project's virtual environment. |
|
|
|
|
Within that folder, pick the ``flask`` executable which will reside in the |
|
|
|
|
``bin`` folder, or in the ``Scripts`` on Windows. |
|
|
|
|
Click the + (*Add New Configuration*) button and select *Python*. Give |
|
|
|
|
the configuration a good descriptive name such as "Run Flask Server". |
|
|
|
|
For the ``flask run`` command, check "Single instance only" since you |
|
|
|
|
can't run the server more than once at the same time. |
|
|
|
|
|
|
|
|
|
The *Script Parameter* field (**B**) is set to the CLI command you to execute. |
|
|
|
|
In this example we use ``run``, which will run the development server. |
|
|
|
|
Select *Module name* from the dropdown (**A**) then input ``flask``. |
|
|
|
|
|
|
|
|
|
You can skip this next step if you're using :ref:`dotenv`. We need to add an |
|
|
|
|
environment variable (**C**) to identify our application. Click on the browse |
|
|
|
|
button and add an entry with ``FLASK_APP`` on the left and the name of the |
|
|
|
|
Python file or package on the right (``app.py`` for example). |
|
|
|
|
The *Parameters* field (**B**) is set to the CLI command to execute |
|
|
|
|
(with any arguments). In this example we use ``run``, which will run |
|
|
|
|
the development server. |
|
|
|
|
|
|
|
|
|
Next we need to set the working directory (**D**) to be the same folder where |
|
|
|
|
our application file or package resides. PyCharm changed it to the directory |
|
|
|
|
with the ``flask`` executable when we selected it earlier, which is incorrect. |
|
|
|
|
You can skip this next step if you're using :ref:`dotenv`. We need to |
|
|
|
|
add an environment variable (**C**) to identify our application. Click |
|
|
|
|
on the browse button and add an entry with ``FLASK_APP`` on the left and |
|
|
|
|
the Python import or file on the right (``hello`` for example). |
|
|
|
|
|
|
|
|
|
Finally, untick the *PYTHONPATH* options (**E**) and give the configuration a |
|
|
|
|
good descriptive name, such as "Run Flask Server", and click *Apply*. |
|
|
|
|
Next we need to set the working directory (**D**) to be the folder where |
|
|
|
|
our application resides. |
|
|
|
|
|
|
|
|
|
Now that we have a configuration which runs ``flask run`` from within PyCharm, |
|
|
|
|
we can simply copy that configuration and alter the *Script* argument |
|
|
|
|
If you have installed your project as a package in your virtualenv, you |
|
|
|
|
may untick the *PYTHONPATH* options (**E**). This will more accurately |
|
|
|
|
match how you deploy the app later. |
|
|
|
|
|
|
|
|
|
Click *Apply* to save the configuration, or *OK* to save and close the |
|
|
|
|
window. Select the configuration in the main PyCharm window and click |
|
|
|
|
the play button next to it to run the server. |
|
|
|
|
|
|
|
|
|
Now that we have a configuration which runs ``flask run`` from within |
|
|
|
|
PyCharm, we can copy that configuration and alter the *Script* argument |
|
|
|
|
to run a different CLI command, e.g. ``flask shell``. |
|
|
|
|