Your hosting provider must be able to run an ASP.NET MVC3 application in medium trust (Framework .NET 4.0).
Write-permissions are needed:
There are NO database settings to be worried about :).
If you hosting provider runs II6, you may need to do some tweaking (read about this here)
In order to make any ASP.NET MVC application work, you need to deploy it in a virtual application folder. That ensures that IIS is going to be able to find the assemblies located on the bin folder, web.config files, etc
If you just create a folder inside your wwwroot space and drop the files there, it won't work.
If you manage your own IIS server, there is a helpful link here that shows how to create virtual application folders
If you are using a shared hosting, you may need to enter into the control panel provided by your company. In case you are using HELM< in your hosting provider/strong>, these are the steps to do it yourself:
You will need to set which folder of your root application will act as virtual folder
Just unzip the package and copy all the files into the virtual folder you just created. You normal will do that using a FTP client.
This is how my /demomvc virtual application looks then I access it using a FTP client:
At this point, if you did correctly the above steps (creating the virtual folder and placing the files) you should be able to hit the application. If you get a 404 error (page not found), that's probably because you server runs an old version of IIS. Please check the troubleshooting area to know how to fix it.
If you get a yellow screen instead, saying something like there has been an error in the application finding the images, you are in the right path! let's configure the application!
Open ajaxphotogallery.config and specify the pyshical path where your images are located (RepositoryPhysicalPath configuration entry)
Just with that you are almost ready to go.
Open ajaxphotogallery.config and define who is admin (you can have more than one)
You just need to edit the config file associated to that folder like and set the PrivateFolder=true and then the list of users that are going to be able to access the folder like this:
Permissions are inherit so if you set a folder as private, the subfolders will be private too
top
The default email notification service is Postmark (leave sending email for the people that actually know how to do it)
Postmark is a reliable service (hassle free) to send your email.
In order to make email notifications work with Postmark you will need to:
Configuration is stored in memory and read just once, so if you change the configuration file, make sure the application restarts (for example, by updating the web.config file you will force application to restart and configuration file to be read from disk again)
The application runs on ASP.NET MVC, so there is not default file to call (like default.aspx). Instead, IIS transfer the control of the web request to the ASP.NET MVC, that lookup the right route (for example /pictures) and translate into a controller action and code execution.
If nothing is executed, please check that: