Ticket #332: mythweb-README.patch

File mythweb-README.patch, 4.2 KB (added by sphery <mtdean@…>, 16 years ago)
  • mythweb/README

     
    7878
    7979    cp -r . /wwww/htdocs/myMythWebDirectory
    8080
    81     Next, you need to make sure that your web server can write to a couple of
    82 directories.  This should be as simple as:  **
     81    Next, you need to make sure that your web server can write to a the
     82image cache directory.  This should be as simple as:  **
    8383
    84     chgrp -R apache /wwww/htdocs/myMythWebDirectory/{image_cache,php_sessions}
    85     chmod g+rw /wwww/htdocs/myMythWebDirectory/{image_cache,php_sessions}
     84    chgrp -R apache /wwww/htdocs/myMythWebDirectory/image_cache
     85    chmod g+rw /wwww/htdocs/myMythWebDirectory/image_cache
    8686
    8787    ** Some distributions run apache as "nobody/nogroup" so please be aware
    8888       that you may need to consult your /etc/httpd/httpd.conf file to verify
     
    103103
    104104Q: Why don't my sessions stick?  (often manifests as sorting issues or settings
    105105    not storing properly)
    106 A: Make sure the php_sessions directory has the proper permissions, and that
    107     apache's AllowOverride setting is correct, as detailed in INSTRUCTIONS
    108     above.  Check config/conf.php to make sure that the server_domain constant
    109     is set correctly so that cookies will work properly.
     106A: Make sure that apache's AllowOverride setting is correct, as detailed in
     107    INSTRUCTIONS above.  Check config/conf.php to make sure that the
     108    server_domain constant is set correctly so that cookies will work properly.
    110109
    111110Q: Why is my browser trying to display the PHP code instead of the server
    112111    executing it for me?
     
    142141    your distribution) and set the value of allow_url_fopen to On.
    143142
    144143Q: I've fixed a bug (or added a feature), how do I submit my patch?
    145 A: First, join the mythtv-dev mailing list.  Then create your patch against
    146     mythweb CVS with `cvs diff -u`, first having made sure that your code is
    147     indented with 4 spaces and not tabs.  Next, either email your patch to the
    148     mailing list, or if it is bigger than 40k or so, put it on a web page and
    149     send a URL to the mailing list.  Either way, please include a detailed
    150     description of your patch in the email.  Make sure that the email contains
    151     "mythweb" in the subject line, or I may not see it.  If you don't hear back
    152     from me right away, don't worry.  As long as you follow these instructions,
    153     I will at least get back to you one way or another -- eventually.
     144A: First, create your patch against mythweb SVN with `svn diff`, having made
     145    sure that your code is indented with 4 spaces and not tabs.  Next, post the
     146    patch on the MythTV Trac Server ( http://svn.mythtv.org/trac/ ) as
     147    described on the Trac server's home page.  Please include a detailed
     148    description of your patch on the ticket.  Select the ticket Type "patch",
     149    Component "mythweb", and type 'xris' into the "Assign To" text box.  If you
     150    don't hear back from me or see the patch committed right away, don't worry.
     151    As long as you follow these instructions, I will at least get back to you
     152    one way or another -- eventually.
    154153
    1551544.0 Plan/TODO
    156155=============
     
    1741735.0 Submitting Patches
    175174======================
    176175
    177 I'm always open to people submitting patches.  The best way to do this is to
    178 merely submit them to the mythtv mailing list (dev is best, but I subscribe
    179 to both lists), with the word "mythweb" in the subject line (if you don't, I
    180 probably won't see it), and preferably also the word "[PATCH]".
     176I'm always open to people submitting patches.  Please submit the patch as
     177described in the final FAQ above.
    181178
    182 Please create patches against the most recent version of CVS by doing
    183 "cvs diff -u".  I can deal with other "diff -u" patches, but if there have
    184 been any major changes in cvs (there occasionally are), I won't put much
    185 effort into trying to make your patch work, so please just use cvs.
     179Please create patches against the most recent version of SVN.  I can deal with
     180other "diff -u" patches, but if there have been any major changes in SVN (there
     181occasionally are), I won't put much effort into trying to make your patch work,
     182so please just use SVN.
     183