View previous topic :: View next topic |
Author |
Message |
swazi -
Joined: 07 Dec 2005 Posts: 4
|
Posted: Wed Dec 07, 2005 3:04 pm Post subject: public_html |
|
|
G'day folks,
Hope this isn't a frequently asked question.. I use Abyss to keep local copies of websites I maintain on a variety of servers. There's one site, on an apache server presumably on a unix system, which has a "public_html" directory structure I'd like to be able to emulate under windows. Is it possible?
I've recreated the directory structure, but Abyss serves it up differently.. What is remotely /swazi/public_html/images/image.jpg I keep in E:\home\swazi\public_html\images\image.jpg, with my root being E:\home.. It gets served up as http://swazi.domain.com/images/image.jpg, with Abyss it comes out as http://127.0.0.1/swazi/public_html/images/image.jpg.. if i just use a relative link /images/image.jpg it churns out 127.0.0.1/images/image.jpg, neither of which are correct.. (don't bother with the links themselves, they're just examples.. :o)
is there a work-around so that i don't have to edit the code before I upload?
thanks
swazi |
|
Back to top |
|
 |
Anonymoose -
Joined: 09 Sep 2003 Posts: 2192
|
Posted: Wed Dec 07, 2005 3:27 pm Post subject: |
|
|
If I'm reading it right, you just need to change the root of the website in Abyss.
On Linux/Unix/whatever hosting, /swazi/public_html/ is treated as the root folder of your website, so /swazi/public_html/images is just /images in a relative link in your code.
On Abyss it sounds like you have pointed the root to E:\ where you should have pointed it to the public_html directory instead, which would give you the same relative link structure.
Hope this makes sense? _________________
"Invent an idiot proof webserver and they'll invent a better idiot..." |
|
Back to top |
|
 |
swazi -
Joined: 07 Dec 2005 Posts: 4
|
Posted: Wed Dec 07, 2005 9:34 pm Post subject: |
|
|
G'day 'moose..
You are correct, yes, but i think i was unclear. For a start, changing the root would then break the other sites I host on my local server. Also, I don't know if it would break the HTML that refers to /swazi/cgi-bin which resides alongside /swazi/public_html rather than beneath it.
I use abyss primarily to serve my client's website as I design them, at http://127.0.0.1/client. If I need the client to see the site, I can send 'em to http://n.n.n.n/client. When finished, I'll upload it to http://theirISP.com/client or quite frankly, wherever the hell they want it.
I'm just trying to reduce the amount of code I need to change between my local server and wherever the code might go..
Was just thinking, can i do sub-domains with Abyss on localhost?
cheers,
swazi |
|
Back to top |
|
 |
swazi -
Joined: 07 Dec 2005 Posts: 4
|
Posted: Sun Dec 11, 2005 1:45 am Post subject: |
|
|
problem solvered - switched to apache.. :o) |
|
Back to top |
|
 |
MonkeyNation -
Joined: 05 Feb 2005 Posts: 921 Location: Cardiff
|
Posted: Sun Dec 11, 2005 2:08 am Post subject: |
|
|
Saying that here's like walking into an airport with a detinator in your hand.
But I don't think it will solve your problem, really. You just need to make your paths relative, E.G. link to /client/page2.html, or page2.html, instead of http://mydomain.com/page2.html. _________________
 |
|
Back to top |
 |
 |
swazi -
Joined: 07 Dec 2005 Posts: 4
|
Posted: Sun Dec 11, 2005 4:43 am Post subject: |
|
|
MonkeyNation wrote: | Saying that here's like walking into an airport with a detinator in your hand. |
:o) I've never really been fond of .conf files and doing all the setup by hand, so to speak, which i why I always tried to avoid going to apache. But if I want my sites to work locally in the same manner as they do remotely, I guess I need to do as the romans do..
MonkeyNation wrote: | But I don't think it will solve your problem, really. You just need to make your paths relative, E.G. link to /client/page2.html, or page2.html, instead of http://mydomain.com/page2.html. |
I was of course already using relative links. The problem I've found was the way apache redirects folder's on a per-user basis. An hour or so of fiddling with the .conf file sorted my problem out, and I can now access the local version of the website in question at http://swazi.localhost in the exact same manner as I access the remote version. The downside of this is that I can't redirect anyone from outside my machine to that address, but then the whole purpose of this exercise is for my own benefit... or i couldof course get myself a domain name...
swazi.. |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|