| Re: Learing PHP, Javascript, and Python on the Cheap, Help! [message #182735 is a reply to message #182724] |
Sat, 31 August 2013 19:31   |
bill
Messages: 310
Registered: October 2010
Karma:
|
Senior Member |
|
|
On 2013-08-31 11:52 AM, irishhacker(at)gmail(dot)com wrote:
> I want to practice Javascript/HTML/CSS and the server side (PHP & Python) on the cheap,
which means I want both the client and the server to be on the same hard
drive.
(My setup is Ubuntu Linux). I'm not sure what is already installed
(Python and Perl was installed
with the Ubuntu.)
> How do people usually do that? And once they do that, later on, how difficult is it to transition
where the server code (PHP/Python) is on a remote server? I'm hoping
that the transition from
hard drive to remote server would involve 99.9% of the PHP/Python code
still working.
>
> Obviously, that setup makes it difficult to test for Internet Explorer special annoyances and for
high-level performance testing, and I'll live with that.
Should not ever be a problem with clean code. You'll spend likely more
time learning about Security in PHP and Python than most of the rest of
it. I don't know what you mean by "special annoyances" unless it's
quirks mode or something like that. And as for performance testing,
that's done on the server, not on the browser.
>
> Thank you.
>
Those are good objectives and some pretty long learning curves but it'll
be well worth it when you've got most of it under your belt and your
research method in tune with the effort.
I don't use Linux and have only dabbled in it so I can't speak to that
at all. However, I don't think the basics are any different than with
any other OS. Anyway, I can't speak to Linux apps et al but I can
respond to other things.
1. There should be no problem IME having both client and server on the
same disc. My local server, clients, browsers et al all live on the same
disk with their "junk" offloaded to another disc drive for easy control
and to minimize the mess on the boot drive.
2. Transitioning to a remote server is simple and no problem at all.
Of course you need to be certain the remote server offers PHP (and that
is the version of PHP you should use, to avoid deprecations and such),
and that it offers Python also, in the same vein as PHP.
3. Once the local and remote servers are both running equivalent
versions of PHP, ASP, PERL, Python, etc., it's a simple matter of
setting NOF's Remote ftp settings proper and telling it to Publish to
your remote site. Most remote servers can handle PHP versions 4 or 5,
but Python, well, not so much; be sure you check it out. Usually a
php_info.php is all you need to get a full listing of information about
your account.
4. So, transitioning from local to remote servers is almost a
no-brainer once you set NOF's ftp settings properly. The only real
thing you need to know is your "root" directory on the server
(public_html, html, and a few other possibilities) and NEVER upload to
anything higher than your root directory; everything goes in, or under,
that directory.
There are some very rare occasions where you might want to use a
separate ftp program like FileZilla, ws_ftp, etc., to upload files. I do
it myself on occasion and have no problems, but NOF makes it a gazillion
times more efficient to accomplish.
BTW, 99.9% working is NOT at all acceptable: It has to be 100%. 1 wrong
character out of ten thousand or a million lines of code is enough to
trash the entire operation of the script sometimes; that's why local
servers with matching versions of the apps on the remote server helps
immensely.
I think you're in for some pretty interesting and likely frustrating
issues to meet your goals, so it'd be best to accomplish them one at a
time rather than all at once, to keep trouble-shooting easier. Assuming
you are already grounded in HTML, take PHP next. I'm not sure what you
would do with Python code, but best of luck with it.
In case you're not already aware of them, php.net and w3schools.org are
the best two "bibles" for html, CSS, php, and several other languages
too. Oh yeah: don't forget CSS either 2 or the latest is 3. I just
noticed you didn't mention CSS (cascading style sheets).
Regards,
Twayne`
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]