...
Load the mod_include
module by adding or uncommenting the following line, near the top of the file on Mac OS X 10.10.4:
Code Block |
---|
LoadModule include_module libexec/apache2/mod_include.so |
Info |
---|
You can also use the |
#ServerName www.example.com:80
...
...
#
# Controls who can get stuff from this server.
#
Require all granted
</Directory>
Replace all that code with the one below :
Code Block | ||||
---|---|---|---|---|
| ||||
#ServerName www.example.com:80 # # Deny access to the entirety of your server's filesystem. You must # explicitly permit access to web content directories in other # <Directory> blocks below. # <Directory /> AllowOverride none Require all denied </Directory> # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "/Users/prachig/ignite-web/website/trunk" <Directory "/Users/prachig/ignite-web/website/trunk"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.4/mod/core.html#options # for more information. # Options FollowSymLinks Multiviews Includes MultiviewsMatch Any # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # AllowOverride FileInfo AuthConfig Limit # AllowOverride None # # Controls who can get stuff from this server. # Require all granted </Directory> |
Make sure to provide correct values for:
DocumentRoot "path-to-ignite-website-folder"
<Directory "path-to-ignite-website-folder">
Locate in your file:
<IfModule mime_module>
...
...
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
Add following lines after comments:
Code Block | ||||
---|---|---|---|---|
| ||||
AddType text/html .html AddOutputFilter INCLUDES .html |
Start Apache HTTP Server, in the terminal, using:
Code Block | ||
---|---|---|
| ||
$ sudo apachectl start |
If this command fails for you try this instead:
Code Block | ||
---|---|---|
| ||
sudo apachectl -k start |
In your browser, type- localhost:80
You can edit "allIf you need to change CSS styles you need to edit one of ".scss" and "ignite.scss" files. Run SCSS watchdog files located under "scss" directory.
Warning |
---|
Do NOT edit .css files directly. |
Install Gulp that can keep track of changes in .scss files and update the .css counterparts on the fly.
Once Gulp is installed run SCSS watchdog under the project's root directory using:
Code Block | ||
---|---|---|
| ||
$ compassgulp watch scss/all.scss |
Warning |
---|
Do NOT edit all.css directly. |
If it happened that the .scss files were updated without the watchdog running then use this command to regenerate .css fromTo make sure browsers upload the most recent Ignite CSS files update the css version number in HTML files by running the following script at 'trunk' level :
Code Block | ||
---|---|---|
| ||
grep -rl 'all.css?v=1.5' * | xargs sed -i '' 's/all.css?v=1.5/all.css?v=1.6/g' |
...
gulp build |