I primarily use WinSCP to connect to a particular site every time I launch the program. I've read about configurations that will launch the app and connect to a site each time the computer starts (such as this), but how can I set WinSCP to connect to a site automatically when launching the app itself?
See WinSCP Command-line Options:
The first syntax opens the site. To open site, stored in folder, use path syntax “folder/site”. You can also open workspace or all sites in site folder.
Select your store site on WinSCP login dialog and go to Manage > Desktop Icon.
It will create a desktop icon that opens WinSCP and automatically logins to the site.
See https://winscp.net/eng/docs/integration#icons
Related
I have a large amount of sites running on IIS 7.5 on Windows Server 2008 R2 Standard, each with many bindings configured. I need to extract the bindings into a text file.
One method is to manually go through each binding for each site within IIS, but it is a painstaking task. It would be easier to access them via a text file. I was lead to believe that site and binding combinations were stored in this file: C:\Windows\System32\inetsrv\Config\applicationHost.config, but I only see a subset of the sites that are configured on the server, and not all of those have all the bindings. So my question is, where does IIS store all of the site bindings?
I'm hoping it's in the form of an accessible text file (e.g. a .config file). If it is in the form of an accessible text file, I only need read access for now, but it would be good to know if this file can be written to rather than needing to edit bindings via IIS, and if so, does the file require administrator level access.
It is possible that you have opened applicationHost.conf with a 32-bit editor (like notepad++).
If you do that it will open C:\Windows\SysWOW64\inetsrv\Config\applicationHost.conf and not C:\Windows\System32\inetsrv\Config\applicationHost.config.
Check this answer for more information.
If you open the file with a 64-bit editor (like Windows notepad), you will see all your websites.
I have a WordPress installation on an Azure Website (not a WebRole). I have FTP access to the site but it literally can take like an hour, which is insane because if I could just ZIP the thousands of files on the site (due to all the plugins, etc) it might take 5 seconds to run the zip. Downloading that then would be far more reliable, as its just 1 file, not 10,000 that could get messed in transfer. Traditional hosters allow you to get on their control panel and zip folders, for instance, but FTP doesn't allow this.
So can I do this on an Azure website, any way, shape or how??? I've looked a bit into SFTP which seems to have some such capabilities but it doesn't seem to be implemented in Azure websites. What can I do, this whole work flow is despisable, I can't live with it, it discourages backups. This encourages one to go to a traditional shared host but I would rather not if possible.
Use the Kudu Console. To access it, simply go to {yoursite}.scm.azurewebsites.net.
You will then be prompted for your login credentials for your Microsoft Azure Account. Once logged in, click on 'Debug Console' at the top of the web page.
Within the UI, Next to each file and folder, there is a Down Arrow icon that lets you download the item.
For files, it directly downloads the file by navigating to it.
For directories, it downloads a zip file containing the full content of the folder.
Detailed instructions can be found here: https://github.com/projectkudu/kudu/wiki/Kudu-console
Adding a screeshot of kudu-console.
Another solution would be the Kudu API, you can accomplish a lot of stuff with it such as downloading a folder from the app service as ZIP as well as automating this using a script. Use the following link within a web browser for example:
If logged in to kudu from the browser just use:
https://{{your-site}}.scm.azurewebsites.net/api/zip/{{folder-path}}
If using a script or command line pass your credentials as follows:
https://user:pass#{{your-site}}.scm.azurewebsites.net/api/zip/{{folder-path}}
Where user and pass can be obtained by going to your app service in the Azure Portal and clicking Get Publish Profile in the Overview tab. See the Deployment Credetials documentation for more details.
Note: The folder path starts from D:\home.
For more information consult the kudu Rest API documentation.
I have recently switched to Coda 2 on Mac (OSX 10.8.2) and under site definitions the host, username and all other information save fine. It will not, however save my passwords. I DO NOT have "ask each time" checked (preemptive answer). Any help would be greatly appreciated.
Found a solution for this. If you open up Keychain Access, find the key that is named after your site so for example ftp.sitename.com. Double click it and go to access. Make it so that any program can use it. Then if you go back to Coda, enter the password once and d/c. It should be saved when you re-open the program :)
Great! But the only thing is missing, that you didn't mention how or from where to open KeyChain access. I used mac spotlight to find it.
Actual location to open Keychain access: under Applications > Utility > KeychainAccess
Just select the ftp.yourwebsiteurl.com
Doubleclick on it
There will be two tabs. Click on AccessControl tab
Select the radio button option : Allow all applications to access this item.
It will ask your system admin password to allow.
Go back to Coda > right click on your website > click Disconnect
Now reenter your password > Connect.
That's it. Your password will be remembered for further connections.
Coda 2.x has built in FTP, git, SSH, and more.
Coda's way of dealing with FTP is to have you set up your files as a "Site"
Once you set it up this way, it saves FTP logins, git logins, ssh logins, etc for all aspects of that site.
Do this:
Open Coda - Coda should automatically open at the 'sites' page. If not, press Command-1 to go to sites.
Right-click, and select 'add site'.
Fill out the details for the site, and save.
Whenever you open that site, Coda will automatically connect to the server.
It's pretty easy to walk thru the dialog options.
A developer just send me a running website files from IIS directory. I want to know if I can run the website on my PC. The file contain "Default.aspx" file, which I assume is of some importance.
I want to know if it is possible to run the website on my PC, I have installed IIS and I placed the file in the wwwroot folder, but unfortunately I dont know how to proceed from here.
Can someone please point me to the right way to continue with this task.
Thanks in advance
First time use of IIS
Now that IIS is running on your system, it should have defaulted to running on port 80. You can test this out by going to http://localhost/
The file you have placed in the wwwroot directory Default.aspx is an ASP.NET application. You need to go to IIS and convert the directory it is stored into a web application.
Now when creating web applications, it is better to create them in another folder other than your wwwroot folder, and in the case of this tutorial it is easier. Move your Default.aspx into a folder named 'webapp', or something of the like.
To convert it into an application, do the following:
In the Server Manager, expand the
'Roles' item in the tree
Expand the 'Web Server (IIS)' item
Click on 'Internet Information Services (IIS) Manager
In the window on the right hand side, you will need to open up your server. In my case, my server is called WIN2008R2. Your server name will be located inside the 'Connections' pane. Expand your server in the tree
Expand the 'Sites' item
Expand your newly created site. There should only be one there, and the item will have a globe next to it
Now right click on your 'webapp' item which will have a folder next to it, and click 'Convert to Application'. Then leave all the properties the same in the window that comes up and click OK.
You have now created a new web application. By going to http://localhost/webapp you should see it working.
You need to configure IIS to host an ASP.NET website.
You can find information about configuring IIS here: http://msdn.microsoft.com/en-us/library/ms178477.aspx
Another option is using the Cassini web server (instead of IIS). You may find it easier to configure: http://ultidev.com/products/cassini/
We've installed Windows Search Server Express on one of our servers, which apparently runs on top of sharepoint.
Sharepoint was installed on port 80, where our "normal" intranet runs. When I disable the intranet and run the sharepoint site, everything works as intended. The intranet is linked in many places it would be a pain to move it, so I'm trying to move sharepoint to another "place" (hoping this is less of a pain), either a different port or as a virtual directory under the main site.
First, when I make any of these changes, it fails to get access to the intranet root. Not sure what it is looking for there, but ok, I give "Network service" (the acocunt the "Sharepoint 80" application pool is running under) access to the intranet root. This gets me one step further, I am stumped:
When I move the Sharepoint website to another port, it complains that it can't find default.aspx (there is none, but also it doesn't need it when running on port 80)
When I move it to a sub folder of the existing site, and try to open the global.asax in the browser, ti tells me that this extension is prohibited, even though the "Application configuration" is - as far as I understand - identical to that of the Sharepoint site, and allows GET, HEAD, POST, DEBUG for .asax.
Any suggestions?
Sharepoint sites should be able to run on any port- if you go into Sharepoint Central Admin and create or delete web applications without a problem.
Is it your intention to run heterogenously with Sharepoint and your regular site both on Port 80? I know that you can create a web application on 80 and then not have a root site collection ( Sharepoint applications consist of a Web Application that runs on a certain port and any number of Site Collections within that, each of which has it's own directory path and can contain lists, libraries, other Site Collections and so on ) just creating one on a different path, but I don't know for sure how that would work alongside an existing web site on the same port- it may not play nice. Again, you can create and delete site collections from the Sharepoint Central Admin page, which is linked from your Administrative Tools list on your server.I would try this first, as if it works it's an easy solution.
Is Windows Search Server Express related to Sharepoint's own search facilities? If it is you may find that it expects to run using some of the Shared Service Provider facilities, which even Sharepoint doesn't expect to be running on the same port as the sites it's providing services for.
An even better way would be to create another alias (cname) in your DNS for your server, just set a different host header for each web site.
for example, in DNS your machine might be named 'intranet'. Create an alias for that machine named 'sharepoint'
In IIS, create a new website for sharepoint, and set the host header for that site to 'sharepoint.domain.com', where domain.com is your domain.
Do the same for the intranet website, but set the host header to 'intranet.domain.com'
That way, your users don't have to use another port in the URL.
Thank you! I found the option in the sharepoint administration website.
I add this response to detail the steps I have taken - maybe they are useful for someone else.
In the sharepoint administration website (running flawlessly on another port), I chose "create or extend web applications", then "extend existing web application".
There, from the the drop down "Web application", "change web application" opens a popup with the web applications available. Search server was installed as "Sharepoint 80", so I selected that.
Then I selected "Create new IIS website", with a new name and a new port. All the other options looked fine to me as default.
Clicking OK, this creates a new web site in IIS, which was configured correctly. it doesn't work via the IP address of the server (http://192.x.x.x:8080), only using the server name - but that's ok with me :)
I still had to make some adjustments with the access rights, but the full crawl is running and I can find a few documents already. Yay!
This is much easier when you first backup your site and then create a new site from the central admin with a new port number and then restore the backup to it(overwrite)