The key file must be created from an “Activation Code”, which can be retrieved from the JetBrains website by logging into the account and downloading the “Activation code for offline usage”. The portable setup also allows you to easily copy that folder between servers.Ĥ) Edit bin/phpstorm64.vmoptions to increase XmS and Xmx memory (optional).ĥ) Run bin/inspect.sh once, this initializes the profile folder and will fail because of a missing license.Ħ) Copy phpstorm.key into profiles/config folder. Otherwise the profile is located in the current users home directory, which is a bit problematic if you want to run PHPStorm with different users. It hard-links profile relative to the PHPStorm folder, effectively making it a “portable” installation. Setting Up PHPStorm on a Serverġ) Download the Linux package of PHPStorm from the offical website.Ģ) Unpack it to some folder on your server.ģ) Edit bin/idea.properties as follows: =$/profile/log Then, commit it to your repository, doesn’t matter where you locate it, you can also keep it under it’s original path if you want to share it with all other developers – which is not a bad idea at all. When you’re happy with it, save the inspection profile to the project and get the inspections configuration file from. I recommend creating one in your IDE clicking together the inspections and error levels as you like, so you can see the results instantly annotated in the code editor. So let’s do this! Inspection Profileįirst thing you need is an inspection profile. Did you know that PHPStorm (or any other Jetbrains IDE) can run inspections from command line and generate XML files for the results? This is a great “hidden” feature of those IDEs and machine-readable output means it can be somehow integrated with a continuous integration (CI) process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |