Extension Communications & Educational Support

Computing & Web Resources

Technical Support

 

Guidelines for Programming on Extension / CAHNRS Web Sites

Why do we have conditions for programming on CAHNRS servers?

  1. The CAHNRS web servers support over 200 web sites for multiple departments throughout the college and state.  We cannot have these web servers go down because of programming errors.
  2. The security on the servers must be maintained at the highest level, including programs developed to run on these servers.  Programs with security flaws may compromise the entire college.
  3. Security patches are applied to servers continually and they have been known to cause programs to stop working or work incorrectly.
  4. CRU systems staff are limited and do not have the resources to help develop or debug projects that are not their responsibility.

Conditions for developing programs on CAHNRS web sites

  1. All development must be done on non-CAHNRS servers.
  2. Before moving the project to a CAHNRS server it must be approved and tested by CRU systems staff.
  3. Access to any database will only be accomplished through the application interface only and not an administrative interface such as PHPAdmin, SQLyog, etc.
  4. Access to the MS Sql server is very limited and not encouraged.
    1. The project needs to have a very good reason to use MS Sql over MS Access or MySql.
    2. If the project gets access to MS Sql it will have very limited access, no administrative access.
  5. Little if any support will be given by CRU in developing the project.
  6. If problems develop after it is in production, such as upgrades to the server, language upgrades, database upgrades, CRU will not be responsible for, or commit resources to, fixing the problem.
  7. If it is determined that the program causes server problems, such as a server crash, security vulnerability, Sql database problems.
    1. The program will be disabled without prior notification.
    2. The program will be enabled only when the CRU systems staff is satisfied the problems have been fixed.
    3. Time frame of re-enabling will be at the convenience and timing of the CRU system staff, not the developing party.
  8. Projects may be developed using .NET, ASP, or PHP, MySql, MS Access.
  9. Programs may not upload files to CAHNRS servers.
  10. Applications will run under limited privileges on the server in the specific directory it resides.  There will be no global access or administrative privileges given to the application.

If you would like assistance in developing an application please contact Tony Wright at 509-335-2814, wright@wsu.edu.

 

Secondary content using h2 tag.

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

 

Life is good at WSU.

Secondary content can be almost anything. If you are not using this region delete all the content that is in between the div tags with the id ="additional".

A unique richness of students, faculty, location, activities, and organizations creates a full, lively student life at the University. This section gives you the insider's view on student life and a sampling of the opportunities here.

"Glimpses." Students talk about life at WSU

These brief posts are written by WSU students to give you a personal look through their window on campus life.

 

CWR, 303 Hulbert Hall, Washington State University, Pullman WA 99164-6244, 509-335-2838, Contact Us: Jim Boyer