• Created by user-d970c, last modified by user-ef11d on Nov 15, 2011
  1. How do I open/close/change CUWebAuth requirements for my sites?
    LAMP provides a variety of customization options for CUWA2. Please see this guide here: Restricting and Opening Access To Your LAMP Site
  2. My .ht/.wdaccess settings aren't being picked up! What gives?
    The way those ACL files work, they must be named PRECISELY .htaccess or .wdaccess - htaccess, wdaccess.txt, etc. will all not be recognized by the web server as an ACL file. If your configuration isn't being applied for some reason, double check that the filename is exact - if using Windows, also double check that file extensions are shown, because Windows tends to append .txt. If you continue to experience issues, please contact webservices-l for assistance.
  3. Oops! I deleted my splash page/default index.php. Can I get that info back?
    Sure, just visit /admin/splash.php, e.g. che-lamp.cit.cornell.edu/admin/splash.php. If you would like it restored as your base index.php, just submit a request to webservices-l.
  4. What's the deal with the permit I got with the instance?
    By default, your LAMP instance comes with a permit of the form cit.lamp.foo, with foo replaced with a name more appropriate to your instance. Its default membership will be all authorized users and the primary and secondary contacts. Also, the primary and secondary contacts will have the update ACL right in order to add or remove users as needed. See An Introduction To Your LAMP Space for more details.
  5. Can I get additional databases? What about additional database users?
    Yes. Contact the LAMP DBA team at dba-support@cornell.edu for these and any other database-related questions. Please reference the fact that this is a LAMP MySQL request, and include your lampuser (e.g. lampuser24) and your account number.
  6. Is FTP available for LAMP?
    No, LAMP uses WebDAV as an alternative to FTP. WebDAV integrates directly with CUWA2 and allows highly customizable access configuration. See the "Getting Connected" section at An Introduction To Your LAMP Space.
  7. Can I use both kProxy 2 and DAVPortal?
    Yes, both kProxy 2 and DAVPortal are available to all LAMP instances since LAMP 1.1. Use either or both, whichever you prefer.
  8. Why are my CGI scripts throwing errors?
    There are a few common issues with CGI in LAMP. First is that the eXecute bit must be set for a CGI script to work; there is a tool linked from your splash page under "CGI Utilities" to set that bit and allow your scripts to run. Second, LAMP relies on the /bin/env convention for the #! line: your best bet is to use #!/bin/env python or #!/bin/env perl for your CGIs. Please feel free to take a look at the demo CGIs included for both Python and Perl to get a sense for how the LAMP CGI environment is set up and how best to get started. And, as always, please feel free to direct really sticky issues or any other questions to webservices-l.
  9. I use Vista and I'm having problems with .ht/.wdaccess files
    Vista's GUI will not allow you to rename a file to something that starts with a dot. There are a couple of workarounds for this:
    • Open the file in Notepad and "Save as..." .htaccess or .wdaccess. Make sure it's set to "All Files" so it won't append .txt. More info here
    • Open a command shell (cmd.exe) and use the command copy con .htaccess followed by Ctrl-Z to create a blank .htaccess file that can then be edited with Notepad. More info here just above the second heading.
  10. How do I start and stop my instance?
    This function, along with several other utilities such as disk space monitoring, instance status and instance upgrades (see "What's this dotrelease thing?", below), is available via the LAMP Monitor. Simply click the "Stop" button next to the instance you wish to restart; the instance will be stopped, and the button will change to "Start". Click "Start" to bring it back online again; voila, the instance has been restarted!
  11. What's this dotrelease thing?
    LAMP upgrades are going to be a) batched and b) self-service. We will put together a new "release" of the service, with upgraded versions of PHP, Python, Perl, and other essential pieces of the system, and announce it to the hosting customers. Once a new release is out, it will be available for customers to upgrade to from the LAMP Monitor page in the timeframe that fits their schedule. It will require an Apache restart to complete the upgrade, but can be rolled back (or forward) at any time. Update your instance when you're ready, in a schedule that fits your needs.
  12. How is my site backed up?
    The mySQL database is backed up using using the MySQL utility 'mysqldump' to export the data(and object DDL) for all databases.  This happens at 8:05PM each evening. These exports are kept on disk for 1 week. The disk is also backed up to tape which is kept for 60 days.
  • No labels