Bolt isntallation issue

Discuss PivotX 2.0.x here. Non-PivotX related discussions go in The Drain.

Bolt isntallation issue

Postby veerpartap » Fri Aug 30, 2013 9:09 am

Hello all,

I am trying to install bolt on nginx server in Ubuntu 12.xx version and I got the 502 bad gateway error. below is the configuration and settings. I have installed virtual box with Ubutnu 12 os and i m remotely connected to that machine from my main machine.

#entry in /etc/hosts file and i am remotely connected to server macine from main machine
192.168.0.170 boltsite.com

#SERVER MAHCINE SETTINGS AND CONFIGURATIONS
# http://boltsite.com/
# nginx - server setting
# Bolt virtual server
server {
server_name boltsite.com http://www.boltsite.com;
root /srv/www/boltsite;
index index.php;

location / {
try_files $uri $uri/ /index.php?$query_string;
}

location ~* /thumbs/(.*)$ {
try_files $uri $uri/ /app/classes/timthumb.php?$query_string;
}

location /app/classes/upload {
try_files $uri $uri/ /app/classes/upload/index.php?$query_string;
}

location ~* \.(?:ico|css|js|gif|jpe?g|png|ttf|woff)$ {
access_log off;
expires 30d;
add_header Pragma public;
add_header Cache-Control "public, mustrevalidate, proxy-revalidate";
}

location = /robots.txt { access_log off; log_not_found off; }
location = /favicon.ico { access_log off; log_not_found off; }

location ~ \.php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param HTTPS off;
}

location ~ /\.ht {
deny all;
}

location /app {
deny all;
}

location ~ /vendor {
deny all;
}

location ~ \.db$ {
deny all;
}
}

/////////////////////////////////

veerpartap@mainhost:/srv/www/boltsite$ ls -lah
total 40K
drwxr-xr-x 6 veerpartap veerpartap 4.0K Aug 30 09:55 .
drwxrwxrwx 7 www-data www-data 4.0K Aug 30 09:56 ..
drwxr-xr-x 12 veerpartap veerpartap 4.0K Aug 30 09:55 app
drwxrwxrwx 2 veerpartap veerpartap 4.0K Aug 30 09:55 files
-rw-r--r-- 1 veerpartap veerpartap 610 Aug 30 09:55 .htaccess
-rw-r--r-- 1 veerpartap veerpartap 322 Aug 30 09:55 index.php
-rw-r--r-- 1 veerpartap veerpartap 3.5K Aug 30 09:55 README.md
-rw-r--r-- 1 veerpartap veerpartap 49 Aug 30 09:55 robots.txt
drwxrwxrwx 3 veerpartap veerpartap 4.0K Aug 30 09:55 theme
drwxr-xr-x 17 veerpartap veerpartap 4.0K Aug 30 09:55 vendor
veerpartap@mainhost:/srv/www/boltsite$ ls -lah app/ | grep database
drwxrwxrwx 2 veerpartap veerpartap 4.0K Aug 30 09:55 database
veerpartap@mainhost:/srv/www/boltsite$ ls -lah app/ | grep cache
drwxrwxrwx 2 veerpartap veerpartap 4.0K Aug 30 09:55 cache
veerpartap@mainhost:/srv/www/boltsite$ ls -lah app/ | grep config
drwxrwxrwx 2 veerpartap veerpartap 4.0K Aug 30 10:03 config


////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
config.yml file
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
veerpartap@mainhost:/srv/www/boltsite/app/config$ cat config.yml
# Database setup. The driver can be either sqlite, mysql or postgres. For
# SQLite, only the databasename is required, while MySQL and PostgreSQL also
# require username, password and perhaps a hostname.
# If you're trying out Bolt, just keep it set to SQLite for now.
database:
driver: mysql
username: root
password: root
databasename: bolt

# The name of the website
sitename: A sample site
payoff: The amazing payoff goes here

# The theme to use. Be sure to copy the theme/base-2013 folder, and change the
# name here accordingly. Don't edit the templates in theme/base-2013, because
# they _will_ get updated in next releases
theme: base-2013

# The locale that'll be used by the application. If no locale is set the
# fallback locale is 'en_GB'. For available options, see: http://docs.bolt.cm/locales
locale: en_GB
#timezone: Zulu

# Set maintenance mode true or false
# While in maintenance mode, only users of level editor or higher can access the site.
# All other visitors are presented with a notice that the site is currently offline.
# The default template file can be found in /app/theme_defaults/ and overriden with
# this option using your own theme.
maintenance_mode: false
maintenance_template: maintenance_default.twig

# If your site is reachable under different urls (say, both blog.example.org/
# as well as example.org/), it's a good idea to set one of these as the canonical,
# so it's clear which is the primary address of the site. Don't include the
# http:// protocol prefix. Enable the following line to define a canonical url.
#canonical: example.org

# Bolt can insert a <link rel="shortcut icon"> for all pages on the site. Note
# that the location given is relative to the currently selected theme. If you
# want to set the icon yourself, just don't enable the following line.
#favicon: images/favicon-bolt.ico

# The default content to use for the homepage, and the template to render it with.
homepage: page/1
homepage_template: index.twig

# The default content for the 404 page. Uses the 'record_template' template by default.
# Make sure this is set to an existing record, otherwise visitors will get an error-page
# when the request a non-existing page.
# Note: If you are logged on, and debug is set to 'true', you will NOT see the 404 page!!
notfound: page/not-found

# The default template and amount of records to use for listing-pages on the site.
# Can be overridden for each contenttype, and for each record, if it has a
# 'templateselect' field.
record_template: record.twig

# The default template and amount of records to use for listing-pages on the site.
# Can be overridden for each contenttype.
listing_template: listing.twig
listing_records: 6
listing_sort: datepublish DESC

# Template for showing the search results. If not defined, uses the settings
# for listing_template and listing_records
search_results_template: listing.twig
search_results_records: 10

# The list of enabled extensions. For Example:
# GoogleAnalytics, FacebookLike, TwitterButton, FacebookComments, Disqus, RSSFeed, SimpleForms.
# Read each 'readme.md' from the Bolt Extensions screen, to see what they do.
enabled_extensions: [ ]

# Add jQuery to the rendered HTML, whether or not it's added by an extension.
add_jquery: false

# The default amount of records to show on overview pages. Can be overridden
# for each contenttype.
recordsperpage: 10

# sitemap settings
#sitemap:
# template: sitemap.twig
# xml_template: sitemap_xml.twig
# ignore:
# - /page/home
# - /page/error404
# - /page/private

# Default settings for thumbnails. Quality should be between 0 (horrible) and
# 100 (best, huge image). Cropping is one of either crop, fit, borders, resize.
# default_thumbnail is the default size of images, when using {{ record.image|thumbnail() }}
# default_image is the default size of images, when using {{ record.image|image() }}
# Note: if you change these values, you might need to clear the cache before they show up.
thumbnails:
default_thumbnail: [ 160, 120 ]
default_image: [ 1000, 750 ]
quality: 80
cropping: crop
notfound_image: view/img/default_notfound.png
error_image: view/img/default_error.png

# If you want to 'brand' the Bolt backend for a client, you can change some key variables
# here, that determine the name of the backend, and adds a primary support/contact link
# to the footer. Additionally you can change the mount-point for the backend, either for
# convenience or to obscure it from prying eyes. The Bolt backend is accessible as /bolt/
# by default, if you change it here, it will only be accessible through the value set in
# 'path'. Keep the path simple: lowercase only, no extra slashes or other special characters.
#branding:
# name: SuperCMS
# path: /admin
# provided_by: [ supercool@example.org, "Supercool Webdesign Co." ]

# Show the 'debug' nut in the lower right corner for logged-in user. By default,
# the debugbar is only shown to logged-in users. Use the 'debug_show_loggedoff'
# option to show it to all users. You probably do not want to use this in a
# production environment.
debug: true
developer_notices: false
debug_show_loggedoff: false

# Use strict variables. This will make Bolt complain if you use {{ foo }},
# when foo doesn't exist.
strict_variables: false

# There are several options for giving editors more options to insert images, video,
# etc in the Wysiwyg areas. But, as you give them more options, that means they also have
# more ways of breaking the preciously designed layout. By default the most 'dangerous'
# options are set to 'false'. If you choose to enable them for your editors, please
# instruct them thoroughly on their responsibilty not to break the layout.
wysiwyg:
images: true
anchor: false
tables: false
fontcolor: false
align: false
subsuper: false
embed: true,
anhor: true,
ck:
allowedContent: true # If set to 'true', any elements and attributes are allowed in Wysiwg Elements
autoParagraph: true # If set to 'true', any pasted content is wrapped in <p> tags for multiple line-breaks
#contentsCss: '' # Absolute Path to CSS File on Server because it's loaded by JavaScript stylesheetparser
filebrowserWindowWidth: '640'
filebrowserWindowHeight: '480'

# Bolt allows some modifications to how 'strict' login sessions are. For every option
# that is set to true, it becomes harder for a bad-willing person to spoof your login
# session. However, it also requires you to re-authenticate more often if you change
# location(ip-address) or your browser has frequent upgrades. Only change these if
# you know what you're doing, and you're having issues with the default settings.
# note: if you change any of these, all current users will automatically be logged off.
cookies_use_remoteaddr: true
cookies_use_browseragent: false
cookies_use_httphost: true
cookies_https_only: false # note: this is on the TODO list.

# The length of time a user stays 'logged in'. Change to 0 to end the session when the browser
# is closed. The default is 1209600: two weeks in seconds.
cookies_lifetime: 1209600

# Set the session cookie to a specific domain. Leave blank, unless you know what you're doing.
# When set incorrectly, you might not be able to log on at all.
# If you'd like it to be valid for all subdomains of 'www.example.org', set this to '.example.org'.
cookies_domain:

# The hash_strength determines the amount of iterations for encrypting passwords. A higher number means
# a harder to decrypt password, but takes longer to compute. '8' is the minimum, '10' is the default,
# '12' is better.
hash_strength: 10

# If you want Bolt installation get news through a proxy
#httpProxy:
# host: my.proxy.server
# user: usr
# password: pwd


///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
These are the files permission which i have in my local virtual machine I tried installing bolt with " Option 1: The easy way, using the command-line. "

once I hit boltsite.com url I am getting 5020 error. Please provide help on this error.
veerpartap
 
Posts: 3
Joined: Fri Aug 30, 2013 8:29 am

Re: Bolt isntallation issue

Postby veerpartap » Fri Aug 30, 2013 9:45 am

Change the below settings for php fpm 5

php-fpm to listen on the correct host/port. In /etc/php5/fpm/pool.d/www.conf change the following line from:

listen = /var/run/php5-fpm.sock

To:

listen = 127.0.0.1:9000

and it works but this change makes my durpal multisite installation to stops i don't know WHY ?
any suggestions would be appreciated
veerpartap
 
Posts: 3
Joined: Fri Aug 30, 2013 8:29 am


Return to 2.x Discussion

Who is online

Users browsing this forum: No registered users and 3 guests