WebStorm Deployment menu options greyed out? - webstorm

I have decided to use WebStorm it seems good however most of the time if I go to Tools - Deployment the upper menu options are greyed out? I can configure and I can go to Options but I cannot download from the server? I can open the remote host just fine and scroll through documents that way but from what I understand WebStorm loses a lot of functionality if you develop this way.
I have no Git and am just working by myself so this workflow is fine for me right now.....if I can download from the server!
In my Deployment Menu from Tools all of the tests work and I can autofind my folder and all that. Whats going on?
Here is the Mappings section:

Your Local path has to be part of your current project (root or a subfolder).
The deployment path a folder of your server where it should be stored - if it should be stored on the root it is just a slash: '/'.
If your connection is successful you should be able to select a folder with the dialog (on the right).
Make also sure your server is marked as 'default' which is your default connection for this project - based on that link.
The projects has been indexed by WebStorm so you can easily refactor and other fancy stuff.
Every project has a root folder with a config folder .idea.

For those that are convinced their mappings are set up the right way, here's one key thing to check. It seems like their SFTP usage does not follow symbolic links (on the remote) correctly. And you can see that if you go to the Mappings tab and click on the "..." for the Deployment path - when it shows the list, symlinked dirs do not show up. By avoiding symlinks in the path, I was able to get the upper part of the Tools/Deployment menu to be active again (non-grey)
I was using PyCharm Pro 2017.3

Related

VuePress build deletes CNAME file in ./docs needed for Github Pages custom domain

I'm trying to get VuePress to work well with GitHub Pages and a custom domain. I have the site working -- https://www.southertonrr.com (repo) -- as long as I manually add a CNAME file to my output folder ('./dest', or in my case, './docs', because that's where GitHub Pages looks for the site) every time after I issue a build command. Otherwise, I assume the build command deletes everything in my output folder and rebuilds the entire site.
Is there a way to get vuepress build to either leave that file alone, or copy a CNAME file from my ./src to my ./docs? Should I be looking at the configureWebpack config to use webpack to do it? (I'm new to webpack.)
Different product completely, but I noticed that Docusaurus for React has a CNAME config setting that does this for you, so I thought I'd check to see if the VuePress community had something similar.
See relative document
Sometimes you may need to provide static assets that are not directly referenced in any of your Markdown or theme components - for example, favicons and PWA icons. In such cases, you can put them inside .vuepress/public and they will be copied to the root of the generated directory.

CF11 LocalHost 404 Issue

I've just recently installed CF11 on a new machine but I'm encountering the below issue when trying to navigate to the localhost directory in a browser.
On my previous machine which was using CF10 I was able to get the directory listings and navigate through folders to specific pages so is it some setting that I am missing?
I can navigate to CFAdmin okay and have added a whole range of aliases in my server.xml file which I can navigate to, as well as adding the CFIDE and WEB-INF ones.
As an aside, I also seem to get that silly 404 badge in front of CFs debug output when I try and navigate to a page that doesn't yet exist. Is there a way to switch it off?
If you need more details let me know.
Thanks in advance

How to link to an .ipa file (over the air ios app installation) using django and STATIC_URL?

I have a django server set up in development. It is basically the simplest "app store" you can imagine. I can now finally serve up static images using STATIC_URL as the prefix.
I however have failed to be able to enable over the air installation of my .ipa file.
When I click on my link on my iPhone or iPad, I get a 404 error, which leads me to think that the path to my .ipa is incorrect. Except that I think that my path is correct :>
Can anyone please point me to what the magic path needs to be?
Thank you!
Inside my django template, all I do is provide a link to the app like so:
Neither of the following work:
Cool Runner
Cool Runner
Cool Runner
So the third try, links to my plist and it IS found, but when I click on it in mobile Safari on my iPHone it just displays the contents of the pList. I am supposed to link to the pList and not the .ipa, right?
Cool Runner
The fourth try (directly above where I link to the ipa) prompts me to download the ipa, and then mobile Safari offers to let me open the link in Evernote, or a few other apps. Not exactly what I want.
In the exact same template, for sanity checks, I provide a link to an mp3 and an iphone configuration profile, which both DO work (clicking on the iphone configuration profile link does launch the iPhone's settings app and asks me to install the config profile correctly)
cool song
<a href="{{STATIC_URL}}binaries/coolRunner.mobileconfig>Cool Runner Configuration Profile</a>
Could there be a problem with my actual ipa file, as in, maybe it is not provisioned right? I used XCode 4.5 and archived it, and followed the dead simple wizard, distributed it for enterprise/ad-hoc deployment, code-signed it with my identity (I have all the privileges except that I am not the Team Agent, but I am an admin), and filled out the form that requires an App URL (which I said to be http://192.168.1.109:8000/appstore/static/binaries/coolRunner.plist)
Well the one thing I neglected, is the way to do it:
Cool Runner
That works. For others who may come after me, let me explain that when you have STATIC_URL defined at the default /static/ in django's development server, you locate your static files right off the domain name and port number: (e.g., http://192.168.1.109:8000/static/captain_obvious.png)
Please also note that I did NOT have to add a type="application/octet-stream" nor a type="text/xml" either on the development server nor in my tag. I'd seen some posts that said that you need it, although those posts may have been referring to production.

Coldfusion 10 on Windows 2k8 - .com/ loads OK but .com/index.cfm gives a 404

I'm setting up a new server (CF10 W2K8) going by Pete Freitag's new CF10 lockdown guide. I have a test site installed and if I bring up www.mydomain.com it loads the default document (index.cfm) just fine. However, if I try www.mydomain.com/index.cfm (or any other specific .cfm page), I get a 404 not found.
IIS logs do record a 404 error. If I create a .htm/.html page it comes up fine.
I had this problem as well. Running on Windows Server 2008 R2.
I found some threads that suggested that I re-run the "Web Server Configuration Tool" that is installed with CF 10 ({cfroot}\cfusion\runtime\bin\wsconfig.exe).
I tried several things including "Add..." using the name of the server (instead of localhost). Then when I removed it (connections using the name of the server), I could see the IIS commands getting executed to remove all of the connection settings. I also removed the localhost connection. However, using "Add..." to attempt to add localhost back never worked.
So, for me, this tool only worked for removing the cfm/IIS settings that allowed CF to work. My next step was going to be a reinstall of CF 10. However, I found a link to this page:
http://helpx.adobe.com/coldfusion/kb/coldfusion10-iis-manual-connector-configuration.html
I followed the instructions on that page with a few exceptions. I didn't need to follow steps #1 & #2. The file (isapi_redirect.dll) was still there. Steps #3 - #5 were verified (the files existed and had the correct information in them). Everything worked after I finished the steps, except document root documents (http://website.com/). All I had to do was add index.cfm as a server-wide "Default Document". Adobe forgot that step in their instructions.
I don't know why the "Web Server Configuration Tool" failed to install on my server. I even tried running it "Run as administrator" with no success.
I did have to add the virtual directories (CFIDE & jakarta) to all the sites on the server as well.
You can use these handy command-line snippets to speed up that process if you have multiple sites to manage:
rem add cfide virtual directory (CF 10):
%systemroot%\System32\inetsrv\appcmd add vdir /app.name:"site.com/" /path:/CFIDE /physicalPath:"{cfroot}\cfusion\wwwroot\CFIDE"
rem add jakarta virtual directory (CF 10):
%systemroot%\System32\inetsrv\appcmd add vdir /app.name:"site.com/" /path:/jakarta /physicalPath:"{cfroot}\config\wsconfig\1"
Just replace the "site.com" and {cfroot} values to work with your server.
When setting up additional sites you must create a virtual directory called jakarta that is mapped to the /config/wsconfig/1 folder
Sorry - forgot to mark this closed. I reformatted and reinstalled everything per the CF10 lockdown guide and it worked that time.
I know one problem I had was mapping a virtual 'jakarta' directory in IIS, but I never came up with a specific solution for the domain.com/index.cfm issue.

I could not launch Php files using Aptana Studio 3

I recently downloaded the Aptana Studio 3 and installed it on my computer..I also configure the webserver in aptana by navigating in window > preferences > webservers, and then i click new button i choose "external web server". then filled all fields ,
Name:WampSerever
Base URL://localhost
C:\wamp\www
Start Command: NET START wampapache
stop Command: NET STOP wampapache
After that, when i am going to test my php by clicking the green button above in the Aptana Studio select "Run firefox-Internal Server"...the firefox open but it displays blank page...
This is what is displayed in the URL
http://127.0.0.1:8020/TestAptana/Hello.php
If your code is correct then try this. I use XAMMP as my server so I'm not sure if this will work with WAMMP.
Go to run configurations select Web Browser then choose which browser you want to use. Then in the main tab under Server find "Use base URL" and click on it. Enter http://localhost/ and make sure that you check the "Append project name".
Make sure that your index page's name is index.html or index.php if you are using php and try running it.
I have this problem too, but one additional thing you need to is to set the path for PHP.exe.
Do this by going to Preferences/Aptana Studio/Editors/PHP/PHP Interpreter. Add and fill in blanks (browse) to php.exe.