Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing DNN on a server,Installing DNN on a server,
Previous
 
Next
New Post
1/4/2008 2:03 PM
 

Hi.

I'm developing an intranet for my company and i'm having some problems installing DNN.

I've tried following the steps in the DotNetNuke Installation Guide.pdf and i've tried the source/install package and the starter kit package.

After a few setbacks, i manage to get the connection string in the web.config properly configurated and i created a virtual directory using IIS which points to the Website files located in my local drive.

So i have a virtual directory (localhost:/dotnnetnuke_2) which points to c:\dnnintranet

I can install the site and work with it just fine - which leads me to think that the connection string is properly configured because it installed the database and i created a few pages/users added modules/etc tried new skins - all of this without problems.

I don't know if it is relevant but the database is stored on a server (not locally),

Now i need to upload the files to a server (ftp), but when i access the domain, it redirects to (localhost:/dotnnetnuke_2). I already added the URL (tried both without and with the /subfolder) to the HTTP alias and it doesn't fix it.

I did something along these lines:

1. Download DNN Source Package

2. rename release.config to web.config

3. configure the connection string (in both places)

4. Set the folder permissions so i can access the site using a browser

5. Open 'DotNetNuke.sln' in visual studio

6. View site in browser (using Visual Studio) - the site then installs the database scripts/etc.

7. Publish the site in c:\dnnintracom

8.Copy c:\dnnintracom to a remote server (ftp)

I am doing something wrong?

I also have a few questions...

Do i need to upload to the server (ftp)  the dnn website before running the dnn site for the first time (before installing the database scripts, etc.)?

Do i work directly on the site that points to the remote server? or i work with it locally and have to upload it again with each change?

Do i need to publish the web site (using visual studio) directly to the remove server? or locally and then copy the files to the remote server?

If i don't publish, is it safe to copy the dnn site to the remote server/is the data unencrypted?

Feel free to ask me for more information if i didn't provide it and you think its relevant.

Thank you for your time and help.

Tiago Costa

 
New Post
1/4/2008 5:18 PM
 

Tiago,

You raised a number of questions and below I've tried to flush out the exact questions and give you my thoughts on them.

1) your production domain redirects to the URL of the development environment

this should be a relatively painless fix -- you need to add your domain name to the portalalias table in the database (you can do that in your local environment and restore the database or insert a row manually in your production environment) -- remember to restart your site after you do this by "touching" the web.config or restarting the application pool.

2) I'm not sure i understand this one -- "do I need to upload to the server the dnn website before running the dnn site for the first time" but I can answer the question "what do i need to have in my production environment before I access the site (when moving test/development environment to production)"

Here is what you need to set up before you access your production environment through your domain name:

  • your development DNN file system with a web.config that points to the production DNN database
  • Give the appropriate windows user permissions to the file system *
  • a virtual directory set up in IIS that points to that file system
  • a portal alias entry for your domain name (this is so it doesn't redirect to the only other portal alias -- your dev site's URL)

* asp.net or network service account depending on your operating system

3) Do you need to work directly with the production server or test each change and move to production.

This will entirely depend on what kind of change you are making and what kind of use your production site is getting. I would recommend testing all development before you put it in production.

4) Publish directly ot the remote server or locally and copy?

I would build everything locally and then copy those files out to the production server after everything is verified. This is just my preference, you may be able to do it either way.

5) In what manner are you copying the files to the server? The files themselves are not necessarily encrypted, but depending on how you transfer them to the server you may be able to encrypt them.


hope that helps,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
1/7/2008 6:15 AM
 

Just wanted to say that i finally got this to work.

Thanks for your help

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing DNN on a server,Installing DNN on a server,


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out