GNU-Linux

Hi, Romy here, making my first post to Open Data, sharing snippets of resources and information I come across as I venture into the fascinating world that is command line.

This was shared to me via IRC by Sam Kottler, whom you should google and be jealous.

Vagrant is a Ruby-based tool for rapidly building and distributing virtualized development environments.

http://vagrantup.com/

My previous post exalting it's qualities. I now have 7,624 entries in it.

If done manually, basic code is this:

On the test server:

Back in your project on your local computer:

This is deprecated in favor of Deploying the Agaric Way.

Run from anywhere on the test or development server:

sudo /srv/scripts/agaric-newproject.sh 5 myagaric myagaric.com my.agaricdesign.com

You'll see a fair amount of output, and the last line you see should be:

Site myagaric installed; run /etc/init.d/apache2 reload to enable.

Superseded by Deploying the Agaric way

See also: <a href="http://data.agaric.com/make-new-drupal-site-project-agaric-system

For http://adcshoes.com/ with the project name adcshoes

An extra step for moving from test to live, from the test server:

sudo svn status -u /sites/adcshoes

(This shoes -- er, shows -- you anything that isn't committed to the repository... like settings.php)

[Note, this is outdated, now using Kerberos.]

Clients don't like their test site competing with their live, production site for Google results. Therefore, we have put our entire set of test sites behind a pop-up requiring basic Apache authentication.

For ongoing maintenance — adding new people to access the test environment behind the authorization wall — the operative command is:

Superseded by a better way to force saving from in vi when read-only, noted in the comments and in Agaric's own post there as :w !sudo tee %

If you've used Debian or any other type of Linux or Unix-like for editing files on your server, at some point you will have done a whole bunch of editing without seeing the "READ ONLY" warning, and then... you try to save.

UPDATE: The reason is that vi is old and not so great, and the new Vim that replaces it is set to run in compatibility mode (reproducing vi's old way of doing things) by default.

Put a line:
set nocompatible
in your ~/.vimrc file.

This FAQ is pretty useless, since no one actually has vi anymore I don't think, so there's no reason to suffer like it says:
http://www.faqs.org/faqs/sgi/faq/apps/section-24.html

works: