Okay, so I am following helpful tips for get setup having a Rails production server, also it states the next within the Apache2 setup:
We must produce a virtual host by developing a file within the "/etc/apache2/sites-available" directory (we'll title it "site" - the file will not have extension but it will likely be a text file). $ sudo nano /etc/apache2/sites-available/site (this can produce the file named "site" - could be any title - AND open it up for editing)
Copy this into that file (compare also using what the notes after setting up mod_rails informs you):
After I was initially testing the waters with Apache Used to do because it stated, creating a fake scaffolded Rails application known as "site". Now I wish to use my real site, which we'll call "realthing." And So I did
# sudo mv /etc/apache2/sites-available/site /etc/apache2/sites-available/realthing
And set my new configurations in to the re-named file. To date so great.
I Quickly visited restart Apache. Problems begin.
# sudo a2ensite realthing Enabling site realthing. To activate the new configuration, you need to run: service apache2 reload
Okay, I'm able to do this.
# sudo service apache2 reload apache2: Syntax error on line 230 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/site: No such file or directory Action 'configtest' failed. The Apache error log may have more information. ...fail!
Fail indeed. Nothing I'm able to appear to complete could possibly get this factor to restart without flipping out concerning the missing "site" file. I check line 230 of /etch/apache2/apache2.conf for just about any specific references. Not a chance:
It is a generic mention of folder that contains "site". But no reference to "site".
So what's going on? How do you get Apache to overlook the fake site "site" and move onto the actual factor "realthing"? It's driving me insane that a superuser reload is failing because Apache aren't able to find personal files that so far as I will tell it's pointless to anticipate finding.
A hard sudo service apache2 stop and sudo service apache2 start does not work. Again using the
* Starting web server apache2 apache2: Syntax error on line 230 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/site: No such file or directory Action 'start' failed.
This really is driving me crazy. Any ideas?
The Apache error log may have more information.
You most likely have a symlink from sites-enabled/site towards the now missing sites-available/site