rejetto forum

Help setting up Home serve weblog

Guest · 13 · 14592

0 Members and 1 Guest are viewing this topic.

Nick

  • Guest
Hi,

Thanks for a great product. Works like a dream.

Not sure if this is the right forum for this inquiry, nothing else seemed to fit?

Now, I am trying to setup a software driven weblog which I have been using for many years (but never on a home server).

I am having  problems setting up the output so that external users can see what I see when I serve on HFS.

I managed to get it working using the configuartion below so that I can see the output on HFS. But others can't see it.

The critical configuration is the following:

Base Path: C:\Data\HomeServer/
(Base path is the location where the html pages are deposited)

Base URL: http://localhost/HomeServer/
(Is the location from which it reads html)

I can't use the server URL because it seems to change when I restart windows.

What am I doing wrong, can you help?

Regards, Nick


Offline rejetto

  • Administrator
  • Tireless poster
  • *****
    • Posts: 13523
    • View Profile
So you have 2 problems?
1. people don't see your website
2. URL keeps changing

right?

1. read the manual
2. read the FAQ


Nick

  • Guest
Thank you for the reply:

So you have 2 problems?

No, just one

1. people don't see your website

People do see my website both the "index" page generated by the blog software and every other folder I have setup within HFS.

It is this setting that I need help with that the blog software requires to generate pages that link to each other:

Base URL: http://localhost/HomeServer/

Clearly http://localhost/HomeServer/ is not right.

My question is: Where should Base URL point to for links to pages in the same folder as the index page?

When I set the Base URL to http://localhost/HomeServer/ I can see links opening pages and others get nothing. However, they too can see the index page.

2. URL keeps changing right?

I'm not concerned about this, I tried to make the URL static, but then things stopped working properly.

1. read the manual 2. read the FAQ

I find this last comment a bit offensive, especially since I read the manual, FAQ and just about every other page on the Forum. I can read. The fact is, I couldn't find this documented anywhere.

I can understand that you get numerous repeat questions when users could have read the documentation.

But, if such a document exists, and it probably does, otherwise you would not be so arrogant about it, then it is illusive for everyday use.

You can help me or not, that's up to you.

But freeware or not, products have to be serviced. Right?

Regards, Nick


Offline rejetto

  • Administrator
  • Tireless poster
  • *****
    • Posts: 13523
    • View Profile
Offensive? I think you didn't notice my answers were not just generic links, but direct to the specific page talking about the problems. I spent my time searching for the specific URLs.

I think you also didn't pay enough attention to the fact that i misunderstood your problem. It is quite obvious if you read the answer. If i don't understand the question, how can you think i will provide the appropriate answer? Of course it was wrong, and you should not feel hurt by this.

You may use /HomeServer/ as base URL for you software. It may work.


Offline rejetto

  • Administrator
  • Tireless poster
  • *****
    • Posts: 13523
    • View Profile
indeed, i asked "right?"
if the answer to that question was "no", you should just ignore the rest of the message


Offline Fysack

  • Tireless poster
  • ****
    • Posts: 598
  • present picture
    • View Profile
    • Admin
I find this last comment a bit offensive
O please dont Nick, you see, kaptain rejetto is a verry problem oriented man, always cutting to the cheese.
So to be able to answer all question, be everywhere for everybody, i guess its absolut nesseserry to be short and precise.
And the time ive been using this forum, ive never see a person who did not get a answer to his question.
So when you find your answers, maybie you can help me setting up home serve weblog  :D
 
Have a nice day  ;)
GOD CAN READ YOUR MIND


Guest

  • Guest
Your url should be http://127.0.0.1:(your port)/Data/HomeServer/
if the file is located at C:\Data\HomeServer\.

Since I know nothing about blog sofware I'll ask: :)

1.Are the pages generated by the blog software file extension htm or
html ?
 I notice you have a folder called data.
2.Does the blog software use a database of any type to store the info ?

3.When these pages are generated by the sofware do the links show
on the index page?

4.When these pages are generated by the software, does it put them in a
"real" folder in the HFS directory?

If all else fails, is your blog software available to be tested?


Offline rejetto

  • Administrator
  • Tireless poster
  • *****
    • Posts: 13523
    • View Profile
don't miss my actual reply, inside all those comments:

Quote
You may use /HomeServer/ as base URL for you software. It may work.


Nick

  • Guest
Hi all,

Thank you for the prompt replies and wanting to help me out. I appreciate that.

Now, the blog is called Thingamablog and it generates static html pages that link to each other using the Base URL: http://...... (whatever)

I have never had a problem with this software. You can generate pages locally or FTP to the net.

On the net it is easy because you can set the default path to the root of the HTM directory eg. http://....../

Now the problem I have with HFS is that my base URL changes everytime I restart windows. It's not a big change but it breaks my links.

For example: let's say my IP address is 58.9.225.170, the next time I restart XP the last combination is always different eg. 58.9.225.55 or 205 or whatever.

I've tried setting a static ip address within HFS, but then nothing works on restart. It makes it impossible to serve without having to provide a new IP address after every start to users. Kind-of defeats the purpose in my case of serving.

Anyway, I have noted the advice from rejetto, but clearly it is not a solution in this case.

Perhaps a more detailed help file for this situation is appropriate. I cannot believe that I am the only one with this dilemma.

Antother product "Home Web Server" and I am not pluging the oposition, just mentioning it, solves this problem by mimicking the web based setup on the local computer. eg.

http:/
           /cgi
           /php
           /images

etc.

Yes, I know I can use their solution. But I am happy with HFS. Everything works and is simple except making pages link to each other and work accross login sessions.

There obviosly is a solution to this problem. I am not that web savy to work it out.

Sorry for the long reply, I am aware you guys have better things to do than reading my long posts.

Regards, Nick         


Offline ~GeeS~

  • Tireless poster
  • ****
    • Posts: 269
  • "The web was made for sharing..."
    • View Profile
OMG  :o

It seems to me, that you've a dynamic IP-address:
"...my IP address is 58.9.225.170, the next time I restart XP the last combination is always different eg. 58.9.225.55 or 205 or whatever ..."

Try to get a static one from your ISP or make use of a (free) DNS webservice (e.g. dyndns, no-ip ... )

"... Now the problem I have with HFS is that my base URL changes everytime I restart windows. It's not a big change but it breaks my links. ..."

Do not use absolute paths in your pages to avoid broken links.  ::)
If you really have to use them, you could get a "static" domainname ( e.g. from dyndns, no-ip etc.)


« Last Edit: December 08, 2006, 08:12:08 PM by ~GeeS~ »
~GeeS~


Offline rejetto

  • Administrator
  • Tireless poster
  • *****
    • Posts: 13523
    • View Profile
Anyway, I have noted the advice from rejetto, but clearly it is not a solution in this case.

1. it is not so clear to me. can you explain in detail?

2. When i told you to read the FAQ, i pointed you to a specific point, you can see the link. To that point, you get a static base address. I think that solve your problem. If not, please tell us why, so it's easier to furnish a better advice.


Nick

  • Guest
Hi all,

Thank you rejetto and others for your help, I worked it out.

However, it is not as easy as you think it should be for the average user to do this.

And, when the advice:

"When i told you to read the FAQ, i pointed you to a specific point, you can see the link. To that point, you get a static base address"

.... finally arrived and was elaborated, was of assistance. But, it wasn't necessary to have had to force it out of you through numerouse posts, when it could have been provided earlier. It certainly would have made the process and service less painful.

Now, I am not looking for an argument here, nor am I trying to apportion balme, the issue is that in an expert mode, we sometimes start to think others know what we know - which they don't.

Anyway, the point is that in your FAQ and in your help files you should use some simple English to tell users how to do this and not explain in Computer "expert" terminology.

Something like this might help (suggested language":

For users who have a dial up connection, or for those whose IP address changes when they restart windows, it is recomended you take the following steps in order to get the best out of your HFS experience:

1. Register a "Static DNS" with one of the recommended service providers.

A static address is like a mask which sits over you IP address and users can login using a more convential mode than using digits such as http://55.334.23 etc. The service provider will provide you with various choices whereby you IP address that was originally something like http://55.334.23 can instead be something like http://HFSuser.weblog.org


2. You might in addition, using the same service provider, setup  a "WebHop" service.

This will help you in making your IP address more portable

Both of these services are free at the time of writing.

Regards, Nick


Guest

  • Guest
 It also might have helped, if you had answered questions about specifics, when asked.
There are reasons they were asked. The answers often point
to a solution to specific problems, that some of us may have already
resolved.