Using: Dreamweaver CS6, ColdFusion 10, CFBuilder 3 (soon)
I'm currently developing three seperate web projects but am using the same set of resources for each project:
Same CSS reset and initialisation styles e.g grid layouts
Same JQuery initialisation files
At the moment each web project has a copy of the same files in its web root. I'd like to have a place that all the sites link to get these common shared resources. I can only think of two ways to do this, both similar:
Decide on a 'master' site and place all the CSS and JS files in that site only.
Make a new site called 'shared or common' and put all the common stuff in there. but this new site still has to reside on some domain. So I still need to choose a 'master' project.
Both the above points are somewhat difficult to do because there is no 'master' site. None of the sites are linked in any way to each other.
Say I've decided on a master site then I could then link to those files using a fully qualified URL. But this means that when I am in my development environment I won't be able to see these files and use any kind of IDE introspection to see whats in the files when I make changes (e.g. like intellisense detects whats in the files and gives you hints).
Overall whats the best way to share these resources for both development and production environments?
Update: After the answers I realised I need a virtual directory in IIS and also a virtual folder in my Windows 7 local folders where my web project files are kept.
You need to use web server virtual directories (for IIS) or alias (for Apache).
Simply create an alias/virtual directory called 'scripts' (or whatever you want) in the web root of each site (you can do this in your development environment too, if you are using IIS or Apache) and then simply use
<script src="/scripts/my.js" ></script>
I'll venture an answer.
We have shared assets across HTTP to sister sites and some unrelated sites. But the primary site collapsed and it created a single point of failure that cascaded in insane ways across our other sites (support calls were also insane until we got the primary site fixed).
Nightmare. Never again...
What I suggest is to create an Amazon AWS S3 bucket and host your assets there.
Provided you don't exceed 20,000 requests or 15GB of data per month it is free.
There are lots of setup examples on the internet.
AND if I can set this up and get it working like a charm, then you should have no problem either.
Just a consideration...Good luck.
We do this without sites. Instead we use server mappings. In the CFAdmin tool, we have mapped logical path "/" to a directory path. That directory path has folders for js, images, css, and templates. Then if we want to use a javascript file, it's simply:
<script src = "/js/theFileIWant.js">
Related
So as the title says, I have completed my site for my first client in Dreamweaver ( still studying in college ), Do i just upload it to their hosting site of choice and will all the links work? I know how to upload just curious about how the links like images and my root folder will stay in tact.
Yes, Generally, they will. You can try it for yourself and see. As long as your refering to the images relative to your file.
Upload all your files to your live server's 'htdocs' or 'public-html' folder. All your links should work fine, if done properly. As far as you move all your folders (images, css, etc) to the live server everything will work.
Dreamweaver doesn't require any special thing or configuration before deploying, you can even deploy directly from Dreamweaver to be super sure nothing breaks while deploying to the production server.
A friend has asked me to do some work on his existing site which was built in Rapidweaver. I'm on Windows, so is there another way I can access and edit his site?
The Rapidweaver project file is meant to be edited only in Rapidweaver, really. As far as I know, the only way around would be to use an HTML editor to modify the pages that are already in the server. However, I would not reccomend you to do it unless you are not going back to Rapidweaver anymore. Because changing the files in the server does not update your local Rapidweaver files. So, you could end up editing something in the server, then getting back to Rapidweaver and upload a "new" version that would not be completely up to date (the previous changes in the server version would be overriden by the older rapidweaver project).
For that kind of work, a CMS (Content Management System) is a more flexible way to work. Nowadays, one of the most common is Wordpress. It will require an inicial setup but after it is working it can be updated from anywhere via web browser, or even from an app in your iPhone. But it is not a Rapidweaver based sollution.
There are a couple CMS related plugins or stacks (Dropkick CMS, Armadillo, Easy CMS, Total CMS...) for Rapidweaver that could also be useful in this context. Once again, first you would need to buy a licence and to setup the website using one of those plugins or stacks. Only then you would be able to edit on the go.
I'm new to MVC3 and have the feeling this may be an obvious problem but nevertheless I can't find a related question on the issue.
I'm developing a web site in MVC3. My production environment has several web sites positioned as follows, eg:
www.companywebsite.com/app1/
www.companywebsite.com/app2/
...to
www.companywebsite.com/mynewapp/
I'm using IIS on Windows server2008 and have created the "mynewapp" folder. But when I deploy my application into this folder all my relative links and files break.
I've converted my scripts and images to T4-MVC references which seems to handle the relative paths but any bog-standard hyperlinks that I have as relative links will not work (and I don't want to convert them to Razor links due to use of images).
All my mapped routes are working fine without change.
Is there a global setting I can use for deployment to the production environment which will tell my project that the base folder is /mynewapp ??
Thanks in advance.
Every time I want to add new code to my site I have to modify the file outside of users view to debug it before updating the real file users see.
I usually create a copy of the file I want to change and test all changes on it but sometimes this files only appear included on another and I have to create two copies and sometimes it becomes even more complicated.
How is this normally done? Are there any tools to simplify the process, for example and enviroment to test my site on my PC so I don't have to upload files to the server each time I update something. Any info about beta testing new features will be thanked.
Most people have a 2nd server (potentially a virtual machine) configured exactly the same as their live (production) website. Where this 2nd server is located is completely up to you, but it should match your live site by using the same versions of software and same file structure.
I also like the idea of a staging server suggested by Sean. Again, your post doesn't say too much about your production web server and all of the features that you're using (are you running scripts on the server? PHP? some version of SQL?). But for a simple setup, you can run a copy of the Apache web server on your own PC, or something a little more lightweight like the XAMPP server.
I'm setting up our company's first Mercurial web interface, and I've hit a bit of a roadblock. We will have multiple teams using this server, and I don't want team A to have to deal with team B's repositories, and vice-versa.
If hgweb served the repositories as they were held in the folder tree, that would be perfect. Unfortunately, all of the templates I've seen "flatten the tree" into a simple repository list. So I've been trying to set up multiple sites, so that https://hg.server/teamA lists only team A's repos, and https://hg.server/teamB shows only team B's repos. Sounds simple enough!
I'm using ISAPI rather than CGI. Unfortunately, the ISAPI handler seems incapable of pointing to more than one hgweb.config file.
I'm impressed with RhodeCode's look, but I have been unable to get it installed properly. I'm extremely new to Python; so some of the installation instructions are, to say the least, confusing.
So... any suggestions on how to successfully install RhodeCode, or otherwise do what I need to do??
You're correct that hgweb will descend into subdirectories by default and show everything in a big flat list. But try setting
[web]
descend = False
to prevent this. You can still browse the subdirectories directly, as shown in this example on my server:
http://hg.lazybytes.net/team-a/
http://hg.lazybytes.net/team-b/
The top-level directory will then look pretty empty, though. Leaving web.descend at its default values might then be better — you'll then see a big flat list at the top-level, but can still browse subdirectories to only see the repos specific to each team. Seems like the best of both worlds.