This site is a static archive of the Aegir community site. Documentation has moved to http://docs.aegirproject.org. Other community resources can be found on the Contacting the community page.
Skip navigation

Can I Install a Non-Drupal Site on My Aegir Server

Help

Can I Install a Non-Drupal Site on My Aegir Server

I have an Aegir 2.0 installation that is working well. Currently, I host only drupal sites on the server and all the sites are managed by Aegir.

I have a need to test something that requires me to install non-drupal software on the server. I would like to install it in /var/www. Can I do so without messing up my Aegir installation? If so, I assume that I must create a vhost entry somewhere to point the test domain to /var/www. Is there documentation on how to do this?

#1

Assuming Aegir only, not BOA here.

Sure you can! You could even plop one in where the rest of the Drupal sites' vhost files are (the ones created by Aegir). Substitute the token [server] for apache or nginx in the next line: /var/aegir/config/server_master/[server]/vhost.d/

Otherwise, you could devise your own method of including vhost files, but an Aegir-only setup will not take over the server in a way that will make this difficult.

#2

Thanks for such a quick response.

So, I am not sure what "BOA" means.

And, I think I understand your post to say that I can create a new vhosts file in the vhost.d directory and place the appropriate directives in that vhosts file to point Apache to /var/www in response to a certain domain name (e.g., notdrupal.myserver.com. Correct?

Thanks

#3

Sorry, BOA = "Barracuda Octopus Aegir". https://drupal.org/project/barracuda It takes over the whole box, down to the system level, and when performing OS level upgrades, it can overwrite settings files. I don't think it would overwrite arbitrary vhost files, but if you were to do something like edit Apache's core httpd.conf file to tell it to read an include directory you set up for non-Aegir managed sites, it would probably overwrite that.

Anyway, not something you have to worry about :)

"And, I think I understand your post to say that I can create a new vhosts file in the vhost.d directory and place the appropriate directives in that vhosts file to point Apache to /var/www in response to a certain domain name"

-Yep

#4

Awesome. Thanks for the great help.

Need help?

Discussion

The discussion area lets your team communicate by posting updates and discussing issues. It is a great place for sharing progress, discussing challenges, and exploring ideas.