I have setup some file watchers (like: jshint, uglifyjs, sass, ...) in PhpStorm.
Already I've exported them into a xml file extension for later use in my upcoming projects.
I could manually import this file at the beginning of every project that I will start; but is there any option to configure PhpStorm to automatically import watchers at every project creation?
Unfortunately there are no options for this a.t.m. Please follow corresponding feature request: https://youtrack.jetbrains.com/issue/WEB-8414
Related
I created one package using NSIS but to install this package on any machine,it's asking for admin credentials. I tried to find out .nsi file for this created package to change RequestExecutionLevel but could not find that. Can anybody suggest where should I check for .nsi file that has been created for new package?
As far as I know NSIS should generate .nsi file for package created. Correct me if I'm wrong here.
NSIS itself does not create .nsi files, it expects you to write them yourself in your favorite editor. The only .nsi files provided by NSIS are in \NSIS\Examples.
A 3rd-party NSIS editor with a wizard feature might create a .nsi for you...
I'm quite confused as to how to create a deployment in SSIS 2008 that I can use throughout the various sites we are going to deploy to. I'm using the deployment utility to deploy my ETL packages which are file based and executed using a SQL job.
When I rebuild my solution, the deployment files are created along with their configuration files which I bind my connection strings to. I've discovered that each of the packages are still referencing the configuration files in my project folder, rather than the configuration files in the deployment folder. I thought that when I created a deployment, the paths referencing the configuration files would be relative paths.
Ideally, what I would have liked to have been able to do would be to copy the contents of the deployment folder to a flash drive, plug it in at the site I'm deploying to and edit the configuration file per the customer site, execute the deployment manifest file in the folder and expect everything to work. But this doesn't seem to be the case.
I also notice that the SQL job has an option to specify the configuration files for the packages, but this doesn't seem to have an effect either. I must clearly be doing something wrong here, please could someone assist.
Seems like you are encountering these two issues with SSIS deployment and execution:
Configuration file references are stored with absolute paths (meaning the concrete path used in the development environment when the configuration file reference was created, and in production this is the same path that will be used).
Specifying a different configuration file at runtime in SSIS 2008 cannot override values specified at design time (see Understanding How SSIS Package Configurations Are Applied at Run Time).
To deploy your packages with a simple file copy the way you describe, you must change your packages to use a relative reference to your configuration files:
Right click the package file and select View Source to open the XML view of the package source. Search for your configuration file, which will include the path, and remove the path; keeping only the filename portion. Alternatively, change the absolute path to a relative path to the configuration file. Save and close the XML view of the package.
Now when you deploy the package and the configuration file together, ensuring they have the same relative location to each other, the package will find the config file by the relative path, and work the way you expect.
Note: from this point forward you will need to open the BIDS IDE by double-clicking on the project or solution file. If you launch Visual Studio, and then open the project or solution from within the IDE, the IDE will not be able to find the configuration file when you execute the package (the current directory will be Windows\System32, not your package folder).
I have a lot of similar projects created in PHPStorm and I need the same Run/Debug configuration in all my projects. Right now the Run/Debug configuration is empty when I create a new project.
I have tried exporting and importing settings from the file menu but that does not copy the Run/Debug configuration of project A into project B.
Can someone please tell me how to copy the Run/Debug configuration of one project into another?
Run/Debug Configurations are project-specific and therefore cannot be exported/imported via File | Export/Import Settings... which is for IDE-wide settings only.
By default, all Run/Debug configurations are stored in YourProject/.idea/workspace.xml file together with other developer-specific settings.
In order to be able to share (better say -- copy) between the projects:
Make sure that each of such Run/Debug configurations has "Shared" box ticked.
Such shared run configurations will be stored in separate *.xml files in YourProject/.idea/runConfigurations/ folder which you can include in VCS if necessary.
You can copy these files from one project to another (while project is closed in IDE, of course).
Cython's *.pyx files need to be compiled for it to function with other py files. Because of this, I would like a file watcher for PyCharm just like for *.coffee files and for *.ts files.
How would one create a file watcher for Cython in Pycharm. A step by step tutorial would be greatly appreciated.
The easiest way would be "Compile on Save".
As an example, in Netbeans the "Compile on Save" feature can be enabled via "Build -> Compiling"
As for the python-demon itself, you could start it by using gunicorn, store md5 hash for each file, revalidate them all the time, and rebuild as soon as hash key was changed for the file.
I've just installed Kohana 3.0.4.2 and I have run the index.php file successfully. According to the documentation, the next step is to edit the config files in the application/config folder. I have that folder but there are no files in it! I downloaded the package again to make sure it wasn't corrupted, but the same problem exists. Why is the application/config folder empty?
You're probably looking at outdated (2.*) documentation. The only config file to edit after an install is application/bootstrap.php. There is some configuration in index.php, but you really shouldn't be touching that unless you want to change the directories things are stored in.
The config folder is used for config files of your custom classes. Since you obviously don't have any in an empty project, the folder is empty. You can see an example of them in use by looking at system/config, where the config files for some of the system classes lie.
As of now, the best docs are the unofficial Kohana wiki. There's also the official docs, but they're a work in progress.
One of the best things about Kohana 3 is that it's extensible and really modular.
In you case, there are no config files by default, you only have the clean framework with couple of modules ( you'll find them in the /modules folder ). Every modul has pretty much the same hierarchy as application folder, so you'll probably find the default config files there.
If you need database config, go to /modules/database/config/ and you'll find the default one, copy it to application/config and you've overwriten the default one from being used ( Kohana autoload just works this way; first looks for files in application folder, then the loaded modules folder(s), and the system (framework) folder is the last.