User login

GNU-Linux

Setting up the Agaric way (svn working copy checkouts) on a new server

So, you're the latest Agaric intern (or a founder who's forgotten everything) and you need to put a client on a new server, and you want to continue using the Agaric repository system.

You've found the right page.

Resolution

If you have to begin at the beginning (but not all the way at the beginning) include this first command, throwing in sudos as required throughout:

apt-get install subversion

Taking a site standalone

Agaric procedure for taking a site that was sharing a Drupal codebase with a bunch of other sites standalone.

Download a new Drupal. http://drupal.org/project/drupal

SVN export the current agaric-sites/5/project-name/trunk/sitename.com directory to replace (and rename as) default.

Check the whole thing in.

Set up Apache, PHP, MySQL for Webserving Drupal

(If you're starting from the beginning, download a starter CD.)

Note: Take time to look at each statement and what it runs.

All of this is from: http://www.howtoforge.com/perfect_setup_debian_etch

apt-get install ssh openssh-server

vi /etc/network/interfaces

In there, this is the important part to change:

Locate command in GNU-Linux gives error

Your server telling you there's no file called locatedb when you try to locate, well, something else? The command below should fix you.

Resolution

updatedb

Edit Ubuntu or Debian locations to look for package sources

Tell Ubuntu or Debian GNU-Linux where to look for package sources, for instance, tell Ubuntu or Debian not to look at the CD.

vi /etc/apt/sources.list

Resolution

Upgrading Debian

This was tried on a completely empty installation. If it actually matters, you are advised to consult your nearest neighborhood GNU-Linux sysadmin.

And of course your first step would be to back up everything.

<

ol>

  • Back everything up, including a list of installed packages. First two commands if necessary:

    cd /
    mkdir backup
    dpkg --get-selections > /backup/installed-software.log

    dpkg --set-selections < /backup/installed-software.log
    dselect

    Check what you have now:

  • MySQL rename database- better off getting it right the first time

    It's possible now in Drupal 5:

    http://dev.mysql.com/doc/refman/5.1/en/rename-database.html

    Resolution

    But you're better off just not doing it. The process isn't any easier than exporting the DB and reimporting, as you have to associate the user by hand anyway.

    Installing and using FTP on Debian

    So I needed FTP in a pinch.

    PureFTP was the first that got me to the install instructions:
    http://www.debianhelp.co.uk/pureftp.htm

    sudo apt-get install pure-ftpd-common pure-ftpd
    sudo groupadd ftpgroup
    sudo useradd -g ftpgroup -d /dev/null -s /etc ftpuser
    sudo pure-pw useradd agaric -u ftpuser -d /home/ftpusers/agaric
    sudo pure-pw mkdb

    It appeared to be successful.

    Clean URLs don't work on test sites on a different port

    This is most curious. URL path rewriting to allow clean urls (no ?q= in Drupal) work just fine on all the sites on the server except those that are accessed through the port that directs

    I've checked out the rules in the sites-available configuration files and all of this is exactly the same.

    Somewhere there must be port-specific rules that set up URL rewriting for the normal port 80 only?

    I removed "Indexes" that followed Options and indented the Order allow etc commands, so that it looks identical to its live sibling, just a tad higher in the same file:

    Syndicate content