In IIS I can convert a folder in a website into an application... but how to do you make the root website an application?
Right now if I have an application (let's call it foo), the only way I know to get it running in IIS is to create a website (we'll call it bar.com) and then add the application under the website so that I have to access it by navigating to http://bar.com/foo. How can I set it up to navigate to the app when simply navigating to bar.com?
but how to do you make the root website an application?
The root website is already an application. So basically when you have a website, this website is mapped to a physical location on the hard disk which is where you should deploy your code. Then if the website has a binding with bar.com:80, your application will be directly accessible on http://bar.com.
Related
I have 2 ASP.NET core projects, first one lets call it Test which contains angular SPA, and the second one Test.API which exposes a RESTfull API to the angular app, now i'm deploying 2 apps to Azure web apps under custom domain.
Test is: www.mydomain.com
Test.API is api.mydomain.com
My problems is that any call from my angular app causing an additional OPTIONS request (delay) that i want to eliminate, by rewriting request (Not redirect) that points to api.mydomain.com/* to www.mydomain.com/api/*.
And also keeping 2 different web apps.
Tried to use asp.net - IIS URL Rewrite module but without any luck, can someone provide me with working example or suggest other way to accomplish this.
Please try to use Azure Web App Virtual Directory. Refer to this article to know how to deploy multiple virtual directories to a single Azure Website. Please try to deploy Test web app to the root project, and deploy Test.API to the virtual directory. After this, we can use www.mydomain.com to access the root web app, use www.mydomain.com/api to access the web app existed in virtual directory.
I have an Umbraco website with an SQl db. I backed up the DB and imported it on the SQL server on the server here. I then copied all the files of my umbraco folder and placed them in a folder on the server here as well.
I then made an 'application' in IIS and gave it an 4.5 application pool (integrated). I linked it to the folder on the server where all of the files are.
When I browse to the site I get to see all the content, also the dynamic content from the DB, but none of the mark up is applied. If I add /umbraco behind it to access the dev dashboard I just get a white page.
I have only been working with it for 5 days and am new to umbraco. IIS on the local server here has no web deploy installed and FTP is also not an option. I developped the website with Webmatrix and web deploy & FTP are the only two publish option it gives me.
Is there something I did wrong or how can I get the website to work properly here?
Umbraco needs to run in Full Trust mode. Make sure that your IIS is configured for Full Trust.
On Features View --> .NET Trust Levels --> Full (internal)
I'm new and I just took over management of a website that runs on the Yii framework.
I have access to the cPanel, FTP and the web server. I can see the /var/www/yii/framework/ folder and everything inside- including the Yiic.php & Yiic.bat files on the FTP & public server via Filezilla.
I was told that the source codes are hosted on a private git server. But I read from the yii documentation that there is a webapp i can access where I can make core changes to the site.
How can I access the Yii Webapp to make changes to the site? (All i see now are .php files on filezilla)
You need to create application outside framework folder, then use framework in that application. Look this article for some overview.
I am looking to migrate an MVC website to Azure web sites. My current set up in IIS is as follows:
Main MVC site -> www.thesite.com (physical path = wwwroot/thesite)
WordPress blog for the site -> www.thesite.com/blog (physical path = wwwroot/thesiteblog)
These are two separate projects on my end. They exist in separate directories within wwwroot. On the Main MVC site, I configured a virtual directory to point www.thesite.com/blog to wwwroot/thesiteblog.
Is it possible to replicate this behavior using Azure web sites? I see there are configuration options for virtual applications and directories, but they only seem to allow pointing to other places withing the same web site. Ideally, Id like to create 2 Azure web sites, and have the /blog subdirectory of web site #1 point to the root of web site #2. I do not wish to incorporate the code from site #2 into site #1, but I would if I find that is my only option.
I cannot be the only one out there who has had this need before, yet I am having a hard time finding any current information about how to go about doing this. Any thoughts out there?
You can keep them in 2 separate projects and use the virtual directories and applications settings in Azure to publish the 2 different projects under the same site. They will run under the same application pool because in Azure currently there is a 1:1 mapping between websites and application pools. For how to, check my answer here
We have a production application (Classic ASP, IIS 7.5) that uses the IIS Default Website and a virtual directory. The application accesses documents from a document share. It works and has worked for many years.
Recently we have added a number of new web applications all under Default Web Site and we are attempting to separate them out into their own IIS Websites. So, we setup a new IIS Website and used a binding to get the application to use the new web site and used the same application pool pointing to the exact same code. (note: our application uses subdomains to point to different databases so we just took one subdomain and binded it to the new site).
For some reason, the documents that are accessible from the Default Web Site are not accessible in the new website. But given that both are using the same application pool and thus share the same application pool identity, how is it possible that one website can access the share, but the other cannot?
More info. we have tried using a domain user as the app pool identity and NETWORKSERVICE both of which work in the Default, neither of which work in the new web site. Also, how are we accessing the documents? We have an ASP file which simply uses the ADO Stream object and we reference the file using "\\docserver\documents..." (which again, is the same in both websites as they are both looking at the same code.