re: . ~/.bashrc permission denied: it's best to login/logout. But if you insist do this first: chmod 700 ~/.bashrc

So I am rather restricted on what is possible!

No! Don't forget: you (as root) are the most powerful user within the bytes and circuits you rented from them for as long as your credit flows. You can do anything (unless something changed in hosting when I looked away)

Please take advice from other Monks on this one: All these use cPanelUserConfig; and especially #!/usr/bin/perlml seem to me to constrain you. For example, in future migrations to other hostings. Plus, when you ftp your code from home into the site you must then manually edit each and every script to incorporate these special headers. This is not practical (for me). So why don't you just re-install all your modules from commandline, try to replicate your home environment onto the host, and do without these use statements on each and every script/module ? Btw, when you are more confident command-line user can save some money if they charge for cPanel.

Additionally using #!/usr/bin/perlml in a perl script which you execute, tells the shell that the script text which follows that *shebang line* should be interpreted (run through) the command /usr/bin/perlml . Which, I guess, is some perl the host installed to be compatible with cPanel module installations etc. Or, perhaps it's a shell script which sets various ENV vars in order for Perl to load modules from certain paths etc. If you are running a perl-based website you must control 100% the Perl version and the Perl modules. But again, I am not running a commercial website myself (a tiny one anyway which does not count), so please seek advice from other Monks more experienced with this situation.

bw, bliako


In reply to Re^3: CPAN PREFIX or INSTALL_BASE by bliako
in thread CPAN PREFIX or INSTALL_BASE by Bod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.