Henry wrote:
>
> --- In vanilla-pudding@yahoogroups.com
> <mailto:vanilla-pudding%40yahoogroups.com>, Pete Wason <codevark@...>
> wrote:
> >
> > Henry wrote:
> > >
> > > Hi,
> > >
> > > I am fairly new to Vanilla. It took me awhile to install, but it's
> > > currently running locally on my laptop. I have heard that the
> > > difficulty I underwent installing it isn't comparable to what it's
> > > like installing on a network. This is my goal.
> > >
> > > I'm looking into godaddy.com for pricing purposes and, though this
> > > message is Off Topic, I wonder if anybody can explain the difference
> > > of "registering" a domain name and "hosting". Registration for the
> > > domain www.wettowel.com runs approximately $10/year with godaddy.com,
> > > but hosting costs a bit more. To avoid the monthly hosting charges, I
> > > am curious whether assistance in setting up my Vanilla space, so that
> > > my laptop functions as the server with whatever domain name I
> > > eventually end up registering (blanketsin, as wettowel seems to've
> > > already been taken), is supported in this group.
> > >
> > >
> >
> > Hi, Henry -
> >
> > Generally, "hosting" is just paying someone for some space on their
> > server. Often it includes domain registration, which is the process by
> > which your IP address (usually out of your control and dynamic if you
> > get your internet access from an ISP) is associated with a domain name,
> > like "www.whoosit.com".
> >
> > If you have an ISP (like a cable internet provider) they often give you
> > a little bit of hosting space on their servers, like 5MB or something
> > like that. For a small, basic website, that's plenty. But setting up
> > your own web server, even if your IP is dynamic, isn't rocket
> surgery. I
> > have a CentOS linux server running Apache, MySQL, PHP, etc., with a
> > bunch of virtual hosts defined. My domains are registered through
> > GoDaddy.com. I use a free (donations accepted) DNS service called
> > EveryDNS to link these domain names to my external "WAN" IP provided by
> > Charter (my cable provider). A script on my server runs every 3 hours
> > and sends my current external IP (which it reads from my router) to
> > EveryDNS to keep my websites reachable in case Charter decides to
> change
> > my IP (which happens every time I shut everything down durning intense
> > lightning storms, for example).
> >
> > There really should be no difference between setting up vanilla "on a
> > network" and setting it up locally. If you plug your laptop into a
> > network, other machines on that network should be able to reach your
> > vanilla-space by (web) browsing to your machine's IP address
> followed by
> > /cgi-bin/vanilla.cgi.
> > *__________________________________________________________
> > Pete Wason* Hy Noom Publications /codevark@.../ 508.865.5414
> >
>
> At the risk of sounding disagreeable, the concept of plugging into a
> network doesn't always allow access to my vanilla space by other
> machines. Consider using a public network at the local library or a
> nearby café. But maybe I should begin with a description of how I plan
> to on implementing my vanilla space before I request assistance in
> it's public installation.
>
> As you may have heard, yahoo is terminating its briefcase.yahoo.com
> services. Until I find a replacement for uploading my .xls, word
> documents, etc. I would like to utilize the attachment feature which
> Vanillaspace offers so that I can transfer my files over the web using
> a different machine at work (like a PC). I own a mac, BTW.
>
> Around the time I started this thread, I went ahead and registered my
> domain name as www.blanketsin.com but I don't know how to implement
> the IP address into vanilla so that other machines can publicly access
> my vanilla space. Since you mention that you have your domains
> registered with godaddy too, would I be completely out of place if I
> asked you, or anybody reading this, how I can achieve the task of
> installing Vanilla using my domain name?
>
> -Henry
>
>

I register with GoDaddy, but host my own sites. I use EveryDNS to point
outside requests for my domain name to my dynamic IP assigned to my
router by my ISP, Charter - I have a script on my server that keeps this
link updated in the case where my IP changes. My router forwards port 80
traffic (HTTP) to the internal IP address of my webserver.

As far as the cafe scenario, once you are connected to the wireless
network, you will be assigned an IP address. Other people on that same
wireless network (probably sitting in the same cafe) will have IPs that
are similar, and they would be able to access your server if you allowed
them to. But folks out on the net probably wouldn't. Only if you had
access to the admin interface of the cafe's router, and used some sort
of external DNS service like EveryDNS would it work otherwise.

The problem is DNS and port forwarding, not anything to do with vanilla.

As far as transferring files, it's a lot faster to use FTP (FileZilla,
etc.).



--

------------------------------------------------------------------------
*Pete Wason* Hy Noom Publications /codevark@.../ 508.865.5414