| Re: can't get includes to load [message #180938 is a reply to message #180934] |
Wed, 27 March 2013 09:35   |
Cal Dershowitz
Messages: 36
Registered: February 2013
Karma:
|
Member |
|
|
On 03/26/2013 11:53 PM, J.O. Aho wrote:
> On 27/03/13 03:14, Jim Higgins wrote:
>> On Tue, 26 Mar 2013 14:50:20 -0700, in
>> <3bednVqnL5qAhc_MnZ2dnUVZ_q6dnZ2d(at)supernews(dot)com>, Cal Dershowitz
>
>>> I have simple questions at this point: how do you try something new on
>>> your server without stomping all over the last thing that worked?
>>
>>
>> Let's say the page you want to work on is named ORIGINAL.PHP. You
>> make a copy of that file and you call it something like
>> ORIGINAL.PHP.BAK. Then you work on ORIGINAL.PHP. If you need more
>> copies og that original, you can append a date or a letter or whatever
>> after BAK to differentiate them.
>
> I would say this is a medieval method and sadly I have seen this done by
> consults who been working on web sites. I do not recommend this method,
> use git or similar to keep track of files and it even allow you fast
> switch between branches where you test different things.
>
> http://wiki.freegeek.org/index.php/Git_for_dummies
> http://www.ralfebert.de/tutorials/git/
>
> far easier to just do a "git checkout index.php" if you want to revert
> to the old version and you do not have to worry that you by mistake
> edited a file without making a "BAK/BUP" copy of it.
>
JO,
This is very impressive software.
http://www.ralfebert.de/blog/tools/git_screencast/
http://en.wikipedia.org/wiki/GitHub
$ sudo apt-get install git
[sudo] password for fred:
....
$ git --version
git version 1.7.9.5
Good enough for me to want to try it. Now ... where to install. I've
been developing my web capabilities through a mix of perl and bash
scripts. These have lain in a "parent" directory which heretofore has
been called 'migrate'. As the the name suggests, it's been moving
around to find a home. Subdirectories were projects that resulted in
web pages which I have used for my various and sundry purposes:
$ pwd
/home/sites/migrate
$ ls
a.html index.php nikon_bash1.sh~ reg1.pl
bash3.sh index.php~ nikon_bash2.sh reg1.pl~
bash3.sh~ melancholia nikon_bash2.sh~ reg2.pl
cleaning mel_ftp2.pl nikon_bash3.sh reg2.pl~
cp_1.pl micah nikon_bash3.sh~ reg2.pl.bak
dog migrate_ftp1.pl nikon_bash4.sh sos
food migrate_ftp1.pl~ nikon_bash4.sh~ style.css
food_1.html music nra style.css~
fredify2.sh music1.pl php Untitled Document 1
fredify2.sh~ music1.pl~ php1.sh variables
includes music2.pl phpini.sh
index.html~ nikon_bash1.sh phpini.sh~
Beyond being the directory that localhost looks to as root, it's gotten
pretty junked up, in the sense that there's a lot in there that
shouldn't get loaded to the remote server. There are scripts to take
images from my camera and resize them in a child directory, such as this
new one:
$ cd php
$ ls -l
total 12
drwxr-xr-x 3 fred automation 4096 Mar 26 17:14 php1
drwxr-xr-x 3 fred automation 4096 Mar 26 17:14 php2
drwxr-xr-x 3 fred automation 4096 Mar 26 17:14 template
$ cd php1
$ ls -l
total 12
drwxr-xr-x 2 fred automation 4096 Mar 27 00:13 includes
-rw-r--r-- 1 fred automation 2208 Mar 26 14:36 index.php
-rwxr-xr-x 1 fred automation 896 Mar 25 21:49 style.css
$
In php1, I have a copy of what exists on my remote server now. php2
was a copy I made of it just to start tapping away at. I was thinking
that php would be the place where I would want to run the init command.
Sound ok so far?
--
Cal
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]