Is this course primarily for Software Engineers or System Administrators? or both? I could see putting higher emphasis on certain things over others depending on the type of students in the room.
Justin On Thu, Sep 18, 2014 at 4:50 PM, Brian J. Rogers <[email protected]> wrote: > I'm not sure where the idea of PHP dying is coming from, but I think that > anyone claiming such is doing some projecting. It might be in a decline but > it is nowhere near dead. > > That said, to teach a curriculum that is centered around production web > servers should probably include installing and configuring many different > combinations. > > The first thing I would suggest is to review different distros, primarily > centos, fedora, debian, ubuntu, etc. Explain pros and cons of each. > Students should probably have basic security measures in place, e.g. > jailing users, sudo access (when and when not to have it), proper file > permissions, and then SELinux (and debian equivalent). Better to know good > security from the beginning. They should also know how to compile from > source and know how to troubleshoot failed builds. They should also know > how to start, stop, enable, and disable services. Understand daemons, > sockets, and ports, and how to troubleshoot them. Learn tools like nestat, > telnet, and nmap. > > Then move on to the static page servers, Apache, nginx, lighttp. Odds are, > those would be the three most common to deal with. Teach how to install > from the repos, and how to get repos from the maintainers or 3rd party > ones. Get them serving up static HTML. > > On to languages. Get PHP, Ruby, Python, Node.js, and Perl able to work with > the three web servers mentioned above. Not at the same time necessarily, > but do try to get two working alongside each other. Learn how do > configuration of each, increase execution timeouts, memory allocation and > such. > > For databases, you can do MariaDB but I'd first do plain MySQL. Let them > know why MariaDB (or Percona) would be preferred. Also cover PostgeSQL and > a few NoSQL engines. Learn how to enable remote connections, and the > security risk that could impose. > > As mentioned, look at tools like Docker, Puppet, Ansible, and Chef. Gone > are the days of having to manually configure each server or write a > collection of bash scripts. Having a tool to provision a server quickly and > efficiently will only help them. > > That's just what I can think of off the top of my head. Hopefully it can > help. > > -Brian > On Sep 18, 2014 3:51 PM, "Aaron Luman" <[email protected]> wrote: > > > As I understand it, the LAMP stack is still the most commonly used setup > > for small business sites. As such, it still has great value for a recent > > grad. > > > > Also, a vary popular trend is the use of tools such as Vagrant to create > > test/dev environments that ensure that all developers are using the same > > system. If you design your course around Vagrant (or some similar > > alternative) + VM then a new grad would be ready to play a central IT > roll > > for any company that has multiple developers (or a single dev shop with > > multiple sites) > > > > If the students learn how to properly set up the server using PHP + MySQL > > on Apache then they will be able to easily self learn how to set up > nginx, > > postgresql, Node, or any other alternate in the LAMP stack. > > > > On Thu, Sep 18, 2014 at 2:51 PM, Aaron Luman <[email protected]> > > wrote: > > > > > As I understand it, the LAMP stack is still the most commonly used > setup > > > for small business sites. As such, it still has great value for a > recent > > > grad. > > > > > > Also, a vary popular trend is the use of tools such as Vagrant to > create > > > test/dev environments that ensure that all developers are using the > same > > > system. If you design your course around Vagrant (or some similar > > > alternative) + VM then a new grad would be ready to play a central IT > > roll > > > for any company that has multiple developers (or a single dev shop with > > > multiple sites) > > > > > > If the students learn how to properly set up the server using PHP + > MySQL > > > on Apache then they will be able to easily self learn how to set up > > nginx, > > > postgresql, Node, or any other alternate in the LAMP stack. > > > > > > On Thu, Sep 18, 2014 at 2:25 PM, Ed Felt <[email protected]> wrote: > > > > > >> I am looking for Suggestions for LAMP Curriculum for a sophomore level > > >> college class. Please share any opinions/suggestions you have. The > > goal > > >> of this class is to teach the major admin skills that are necessary to > > >> support the most popular services that run on Linux with major > emphasis > > on > > >> managing and running production Linux servers and minor emphasis on > > >> performance/coding of the databases and web technologies. It will be > > for > > >> students that have successfully completed a Linux Administration > course: > > >> setup, bash skills, etc... > > >> > > >> 1. Some are saying that PHP is dying or almost dead but what about > > >> sites > > >> like Yahoo and Facebook that still use it heavily? Should > PHP/MySQL > > >> be the > > >> main crux of a LAMP class? > > >> 2. How important is MySQL currently? Would MariaDB be better to > > teach > > >> in such a class? > > >> 3. Should this not even be a LAMP class (with focus on MySQL/Maria > > and > > >> PHP/Python/Perl) but a class that just teaches the basics of the > most > > >> popular and emerging database/web technologies that run on Linux > like > > >> Hadoop, MongoDB, NodeJS, MySQL, MariaDB, PHP, Python, Ruby, Perl > > >> etc...? > > >> > > >> The focus of the two year college I teach at is to prepare students as > > >> quickly and thoroughly as possible to go into the workforce, not just > to > > >> do > > >> two years of college to transfer to a four year. So the main focus is > > >> skills and experience as apposed to theory, (though it's important to > > have > > >> a little theory in there), enough to one could get an internship or > > entry > > >> level job by the time they graduate from the two year program. Of > > course > > >> flame wars are welcome :) > > >> > > >> Sincerely, > > >> > > >> C. Ed Felt > > >> > > >> _______________________________________________ > > >> > > >> UPHPU mailing list > > >> [email protected] > > >> http://uphpu.org/mailman/listinfo/uphpu > > >> IRC: #uphpu on irc.freenode.net > > >> > > > > > > > > > > _______________________________________________ > > > > UPHPU mailing list > > [email protected] > > http://uphpu.org/mailman/listinfo/uphpu > > IRC: #uphpu on irc.freenode.net > > > > _______________________________________________ > > UPHPU mailing list > [email protected] > http://uphpu.org/mailman/listinfo/uphpu > IRC: #uphpu on irc.freenode.net > _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
