mirror of
https://github.com/evennia/evennia.git
synced 2026-03-16 21:06:30 +01:00
Merge pull request #3576 from ChrisLR/docs/pycharm-linux
Rewrite doc for pycharm
This commit is contained in:
commit
bde8c0def7
1 changed files with 100 additions and 59 deletions
|
|
@ -1,84 +1,125 @@
|
|||
# Setting up PyCharm with Evennia
|
||||
|
||||
[PyCharm](https://www.jetbrains.com/pycharm/) is a Python developer's IDE from Jetbrains available for Windows, Mac and Linux. It is a commercial product but offer free trials, a scaled-down community edition and also generous licenses for OSS projects like Evennia.
|
||||
[PyCharm](https://www.jetbrains.com/pycharm/) is a Python developer's IDE from Jetbrains available for Windows, Mac and Linux.
|
||||
It is a commercial product but offer free trials, a scaled-down community edition and also generous licenses for OSS projects like Evennia.
|
||||
|
||||
> This page was originally tested on Windows (so use Windows-style path examples), but should work the same for all platforms.
|
||||
First, download and install the IDE edition of your choosing.
|
||||
The community edition should have everything you need,
|
||||
but the professional edition has integrated support for Django which can help.
|
||||
|
||||
First, install Evennia on your local machine with [[Getting Started]]. If you're new to PyCharm, loading your project is as easy as selecting the `Open` option when PyCharm starts, and browsing to your game folder (the one created with `evennia --init`). We refer to it as `mygame` here.
|
||||
## From an existing project
|
||||
|
||||
If you want to be able to examine evennia's core code or the scripts inside your virtualenv, you'll
|
||||
need to add them to your project too:
|
||||
Use this if you want to use PyCharm with an already existing Evennia game.
|
||||
First, ensure you have completed the steps outlined [here](https://www.evennia.com/docs/latest/Setup/Installation.html#requirements).
|
||||
Especially the virtualenv part, this will make setting the IDE up much easier.
|
||||
|
||||
1. Go to `File > Open...`
|
||||
1. Select the folder (i.e. the `evennia` root)
|
||||
1. Select "Open in current window" and "Add to currently opened projects"
|
||||
1. Open Pycharm and click on the open button, open your root folder corresponding to `mygame/`.
|
||||
2. Click on File -> Settings -> Project -> Python Interpreter -> Add Interpreter -> Add Local Interpreter
|
||||

|
||||
3. Click on VirtualEnv -> Existing Interpreter -> Select your existing virtualenv folder,
|
||||
should be `evenv` if you followed the default installation.
|
||||
|
||||
It's a good idea to set up the interpreter this before attempting anything further. The rest of this page assumes your project is already configured in PyCharm.
|
||||

|
||||
|
||||
1. Go to `File > Settings... > Project: \<mygame\> > Project Interpreter`
|
||||
1. Click the Gear symbol `> Add local`
|
||||
1. Navigate to your `evenv/scripts directory`, and select Python.exe
|
||||
## From a new project
|
||||
|
||||
Use this if you are starting from scratch or want to make a new Evennia game.
|
||||
1. Click on the new project button.
|
||||
2. Select the location for your project.
|
||||
You should create two new folders, one for the root of your project and one
|
||||
for the evennia game directly. It should look like `/location/projectfolder/gamefolder`
|
||||
3. Select the `Custom environment` interpreter type, using `Generate New` of type `Virtual env` using a
|
||||
compatible base python version as recommended in https://www.evennia.com/docs/latest/Setup/Installation.html#requirements
|
||||
Then choose a folder for your virtual environment as a sub folder of your project folder.
|
||||
|
||||

|
||||
|
||||
Click on the create button and it will take you inside your new project with a bare bones virtual environment.
|
||||
To install Evennia, you can then either clone evennia in your project folder or install it via pip.
|
||||
The simplest way is to use pip.
|
||||
|
||||
Click on the `terminal` button
|
||||
|
||||

|
||||
|
||||
1. Type in `pip install evennia`
|
||||
2. Close the IDE and navigate to the project folder
|
||||
3. Rename the game folder to a temporary name and create a new empty folder with the previous name
|
||||
4. Open your OS terminal, navigate to your project folder and activate your virtualenv.
|
||||
On linux, `source .evenv/bin/activate`
|
||||
On windows, `evenv\Scripts\activate`
|
||||
5. Type in `evennia --init mygame`
|
||||
6. Move the files from your temporary folder, which should contain the `.idea/` folder into
|
||||
the folder you have created at step 3 and delete the now empty temporary folder.
|
||||
7. In the terminal, Move into the folder and type in `evennia migrate`
|
||||
8. Start evennia to ensure that it works with `evennia start` and stop it with `evennia stop`
|
||||
|
||||
At this point, you can reopen your IDE and it should be functional.
|
||||
[Look here for additional information](https://www.evennia.com/docs/latest/Setup/Installation.html)
|
||||
|
||||
Enjoy seeing all your imports checked properly, setting breakpoints, and live variable watching!
|
||||
|
||||
## Debug Evennia from inside PyCharm
|
||||
|
||||
1. Launch Evennia in your preferred way (usually from a console/terminal)
|
||||
1. Open your project in PyCharm
|
||||
1. In the PyCharm menu, select `Run > Attach to Local Process...`
|
||||
1. From the list, pick the `twistd` process with the `server.py` parameter (Example: `twistd.exe --nodaemon --logfile=\<mygame\>\server\logs\server.log --python=\<evennia repo\>\evennia\server\server.py`)
|
||||
### Attaching to the process
|
||||
1. Launch Evennia in the pycharm terminal
|
||||
2. Attempt to start it twice, this will give you the process ID of the server
|
||||
3. In the PyCharm menu, select `Run > Attach to Process...`
|
||||
4. From the list, pick the corresponding process id, it should be the `twistd` process with the `server.py` parameter (Example: `twistd.exe --nodaemon --logfile=\<mygame\>\server\logs\server.log --python=\<evennia repo\>\evennia\server\server.py`)
|
||||
|
||||
Of course you can attach to the `portal` process as well. If you want to debug the Evennia launcher
|
||||
You can attach to the `portal` process as well, if you want to debug the Evennia launcher
|
||||
or runner for some reason (or just learn how they work!), see Run Configuration below.
|
||||
|
||||
> NOTE: Whenever you reload Evennia, the old Server process will die and a new one start. So when you restart you have to detach from the old and then reattach to the new process that was created.
|
||||
|
||||
> To make the process less tedious you can apply a filter in settings to show only the server.py process in the list. To do that navigate to: `Settings/Preferences | Build, Execution, Deployment | Python Debugger` and then in `Attach to process` field put in: `twistd.exe" --nodaemon`. This is an example for windows, I don't have a working mac/linux box.
|
||||
|
||||

|
||||
### Run Evennia with a Run/Debug Configuration
|
||||
|
||||
## Run Evennia from inside PyCharm
|
||||
This configuration allows you to launch Evennia from inside PyCharm.
|
||||
Besides convenience, it also allows suspending and debugging the evennia_launcher or evennia_runner
|
||||
at points earlier than you could by running them externally and attaching.
|
||||
In fact by the time the server and/or portal are running the launcher will have exited already.
|
||||
|
||||
This configuration allows you to launch Evennia from inside PyCharm. Besides convenience, it also allows suspending and debugging the evennia_launcher or evennia_runner at points earlier than you could by running them externally and attaching. In fact by the time the server and/or portal are running the launcher will have exited already.
|
||||
#### On Windows
|
||||
1. Go to `Run > Edit Configutations...`
|
||||
2. Click the plus-symbol to add a new configuration and choose Python
|
||||
3. Add the script: `\<yourprojectfolder>\.evenv\Scripts\evennia_launcher.py` (substitute your virtualenv if it's not named `evenv`)
|
||||
4. Set script parameters to: `start -l` (-l enables console logging)
|
||||
5. Ensure the chosen interpreter is your virtualenv
|
||||
6. Set Working directory to your `mygame` folder (not your project folder nor evennia)
|
||||
7. You can refer to the PyCharm documentation for general info, but you'll want to set at least a config name (like "MyMUD start" or similar).
|
||||
|
||||
A dropdown box holding your new configurations should appear next to your PyCharm run button.
|
||||
Select it start and press the debug icon to begin debugging.
|
||||
|
||||
#### On Linux
|
||||
1. Go to `Run > Edit Configutations...`
|
||||
2. Click the plus-symbol to add a new configuration and choose Python
|
||||
3. Add the script: `/<yourprojectfolder>/.evenv/bin/twistd` (substitute your virtualenv if it's not named `evenv`)
|
||||
4. Set script parameters to: `--python=/<yourprojectfolder>/.evenv/lib/python3.11/site-packages/evennia/server/server.py --logger=evennia.utils.logger.GetServerLogObserver --pidfile=/<yourprojectfolder>/<yourgamefolder>/server/server.pid --nodaemon`
|
||||
5. Add an environment variable `DJANGO_SETTINGS_MODULE=server.conf.settings`
|
||||
6. Ensure the chosen interpreter is your virtualenv
|
||||
7. Set Working directory to your game folder (not your project folder nor evennia)
|
||||
8. You can refer to the PyCharm documentation for general info, but you'll want to set at least a config name (like "MyMUD Server" or similar).
|
||||
|
||||
A dropdown box holding your new configurations should appear next to your PyCharm run button.
|
||||
Select it start and press the debug icon to begin debugging.
|
||||
Note that this only starts the server process, you can either start the portal manually or set up
|
||||
the configuration for the portal. The steps are very similar to the ones above.
|
||||
|
||||
1. Go to `Run > Edit Configutations...`
|
||||
1. Click the plus-symbol to add a new configuration and choose Python
|
||||
1. Add the script: `\<yourrepo\>\evenv\Scripts\evennia_launcher.py` (substitute your virtualenv if it's not named `evenv`)
|
||||
1. Set script parameters to: `start -l` (-l enables console logging)
|
||||
1. Ensure the chosen interpreter is from your virtualenv
|
||||
1. Set Working directory to your `mygame` folder (not evenv nor evennia)
|
||||
1. You can refer to the PyCharm documentation for general info, but you'll want to set at least a config name (like "MyMUD start" or similar).
|
||||
2. Click the plus-symbol to add a new configuration and choose Python
|
||||
3. Add the script: `/<yourprojectfolder>/.evenv/bin/twistd` (substitute your virtualenv if it's not named `evenv`)
|
||||
4. Set script parameters to: `--python=/<yourprojectfolder>/.evenv/lib/python3.11/site-packages/evennia/server/portal/portal.py --logger=evennia.utils.logger.GetServerLogObserver --pidfile=/<yourprojectfolder>/<yourgamefolder>/server/portal.pid --nodaemon`
|
||||
5. Add an environment variable `DJANGO_SETTINGS_MODULE=server.conf.settings`
|
||||
6. Ensure the chosen interpreter is your virtualenv
|
||||
7. Set Working directory to your game folder (not your project folder nor evennia)
|
||||
8. You can refer to the PyCharm documentation for general info, but you'll want to set at least a config name (like "MyMUD Portal" or similar).
|
||||
|
||||
Now set up a "stop" configuration by following the same steps as above, but set your Script parameters to: stop (and name the configuration appropriately).
|
||||
You should now be able to start both modes and get full debugging.
|
||||
If you want to go one step further, you can add another config to automatically start both.
|
||||
|
||||
A dropdown box holding your new configurations should appear next to your PyCharm run button. Select MyMUD start and press the debug icon to begin debugging. Depending on how far you let the program run, you may need to run your "MyMUD stop" config to actually stop the server, before you'll be able start it again.
|
||||
1. Go to `Run > Edit Configutations...`
|
||||
2. Click the plus-symbol to add a new configuration and choose Compound
|
||||
3. Add your two previous configurations, name it appropriately and press Ok.
|
||||
|
||||
### Alternative config - utilizing logfiles as source of data
|
||||
|
||||
This configuration takes a bit different approach as instead of focusing on getting the data back through logfiles. Reason for that is this way you can easily separate data streams, for example you rarely want to follow both server and portal at the same time, and this will allow it. This will also make sure to stop the evennia before starting it, essentially working as reload command (it will also include instructions how to disable that part of functionality). We will start by defining a configuration that will stop evennia. This assumes that `upfire` is your pycharm project name, and also the game name, hence the `upfire/upfire` path.
|
||||
|
||||
1. Go to `Run > Edit Configutations...`\
|
||||
1. Click the plus-symbol to add a new configuration and choose the python interpreter to use (should be project default)
|
||||
1. Name the configuration as "stop evennia" and fill rest of the fields accordingly to the image:
|
||||

|
||||
1. Press `Apply`
|
||||
|
||||
Now we will define the start/reload command that will make sure that evennia is not running already, and then start the server in one go.
|
||||
1. Go to `Run > Edit Configutations...`\
|
||||
1. Click the plus-symbol to add a new configuration and choose the python interpreter to use (should be project default)
|
||||
1. Name the configuration as "start evennia" and fill rest of the fields accordingly to the image:
|
||||

|
||||
1. Navigate to the `Logs` tab and add the log files you would like to follow. The picture shows
|
||||
adding `portal.log` which will show itself in `portal` tab when running:
|
||||

|
||||
1. Skip the following steps if you don't want the launcher to stop evennia before starting.
|
||||
1. Head back to `Configuration` tab and press the `+` sign at the bottom, under `Before launch....`
|
||||
and select `Run another configuration` from the submenu that will pop up.
|
||||
1. Click `stop evennia` and make sure that it's added to the list like on the image above.
|
||||
1. Click `Apply` and close the run configuration window.
|
||||
|
||||
You are now ready to go, and if you will fire up `start evennia` configuration you should see
|
||||
following in the bottom panel:
|
||||

|
||||
and you can click through the tabs to check appropriate logs, or even the console output as it is
|
||||
still running in interactive mode.
|
||||
You can now start your game with one click with full debugging active.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue