| Re: can't get includes to load [message #180939 is a reply to message #180938] |
Wed, 27 March 2013 10:00   |
J.O. Aho
Messages: 194
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 27/03/13 10:35, Cal Dershowitz wrote:
> 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:
first of all, I would remove all the files ending with ~
find /home/sites/migrate -name "*~" -exec rm -f {} \;
just copy paste that one, if you feel insure, then make a backup of the
directory:
cd /home/sites/ && tar -cf ~/migrate.tar migrate && cd && gzip migrate.tar
(I know, you can simplify that)
Keep in mind, both are "one liners" and just copy past from this post.
> $ 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:
I would clean up things a bit, have your handy scripts in a directory
outside and give it a better name than php, so you remember what you
have there.
When you have structured up things a bit, so you find you stuff easily,
just make a git repository for it all
cd /home/sites && git init && git commit -m "initial commit" -a
now you will have everything in the git repository and you are ready to
work. You have your tarball if you by mistake did delete a file you
shouldn't have.
> $ 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.
I would ditch the php2, no use of it, all work you do should origin from
what you have live. Don't forget to create a new branch when you start
to work with something, when you put something live, you merge that
branch to master branch. So master should always be what you have in
live, other branches are for what you are working on or testing.
--
//Aho
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]