Re: Restricting access to a website [message #174853 is a reply to message #174815] |
Wed, 13 July 2011 18:44 |
Graham Hobbs
Messages: 42 Registered: September 2010
Karma:
|
Member |
|
|
Folks,
Am replying to all who contributed. I learned much, in particular,
stuff that would not have been gleaned had I referred to just the
manuals. I now have a feeling of what I can/can't do, pathways I
should follow after my associates have done with their access, in
general, a fair idea of what's going on.
Thanks to all,
Graham
A Bill B posted a while ago about some facility to collect all the
posts into one document in one shot instead of the cutting and pasting
I did for this topic - doesn't exist, right?
'Salient bits' would be even nicer!
---
On Mon, 11 Jul 2011 16:08:53 -0400, Graham Hobbs <ghobbs(at)cdpwise(dot)net>
wrote:
> On Sun, 10 Jul 2011 22:21:41 -0400, Jerry Stuckle
> <jstucklex(at)attglobal(dot)net> wrote:
>
>> On 7/10/2011 10:01 PM, Graham Hobbs wrote:
>>> Hello,
>>>
>>> I 'very laboriously' coded my index.php (close to novice level), for
>>> my website and it is up and running. It's not public yet and needs to
>>> stay that way. I need to give the address to two people who will help
>>> with my product's development .. but they could reveal the address
>>> anywhere, inadvertently or otherwise.
>>>
>>> If, for example, my website is www .lahdedah. com, I want to allow
>>> full access to these two people (and me:-)) .. others would get a
>>> 'Sorry, not yet available' screen. I envision hard coding their home
>>> address's into my index.php?? Am not interested in any additional
>>> typing by these three.
>>>
>>> Hope I've been clear. Is this feasible, easy/hard/unusual?
>>> Please, thanks
>>> Graham
>>
>> There are any number of ways to do it, none of which require PHP or any
>> other server-side language. Try alt.apache.configuration (assuming, of
>> course, you're using Apache).
>>
>> Also, unless you are David Small of Small Expressions, you shouldn't be
>> using his domain name in an example. Use www.example.com, which is
>> reserved for just such a purpose.
> ---
> Jerry, folks, thanks,
>
> Will check into alt.apache.configuration and apologies about lahdedah,
> didn't know about example.com.
>
> But I wasn't emphatic enough .. yes I would know their IP addresses so
> CAN I hard code them in my index.php? Yes or no would do and a PHP
> buzzword I might search on to get started .. I just prefer all my code
> in one place.
>
> .. am definitely not interested in extra keying of passwords by my two
> associates.
>
> Thanks,
> Graham
|
|
|