mirror of
https://github.com/Poniverse/Pony.fm.git
synced 2024-11-25 06:27:59 +01:00
Added Vagrant file.
This commit is contained in:
Nelson LaQuet
parent
d5fb0fe2ee
commit
f484caf9e6
33 changed files with 1819 additions and 272 deletions
10
Vagrantfile
vendored
Normal file
10
Vagrantfile
vendored
Normal file
|
|
@ -0,0 +1,10 @@
|
||||||
|
Vagrant.configure("2") do |config|
|
||||||
|
config.vm.box = 'laravel/homestead'
|
||||||
|
|
||||||
|
config.vm.network :private_network, ip: "192.168.33.11"
|
||||||
|
config.vm.synced_folder ".", "/vagrant", type: "nfs"
|
||||||
|
|
||||||
|
config.vm.provision "shell", path: "vagrant/install.sh"
|
||||||
|
|
||||||
|
config.vm.synced_folder "../pony.fm.files", "/vagrant-files"
|
||||||
|
end
|
||||||
|
|
@ -74,7 +74,7 @@ App::down(function()
|
||||||
});
|
});
|
||||||
|
|
||||||
Auth::extend('pfm', function() {
|
Auth::extend('pfm', function() {
|
||||||
return new Guard(new PFMAuth(), App::make('session'));
|
return new Guard(new PFMAuth(), App::make('session.store'));
|
||||||
});
|
});
|
||||||
|
|
||||||
Validator::resolver(function($translator, $data, $rules, $messages)
|
Validator::resolver(function($translator, $data, $rules, $messages)
|
||||||
|
|
|
||||||
File diff suppressed because it is too large
Load diff
|
|
@ -27,7 +27,7 @@ $app->redirectIfTrailingSlash();
|
||||||
*/
|
*/
|
||||||
|
|
||||||
$env = $app->detectEnvironment([
|
$env = $app->detectEnvironment([
|
||||||
'local' => ['dev.spa.pony.fm']
|
'local' => ['pony.fm.local', 'api.pony.fm.local', 'homestead']
|
||||||
]);
|
]);
|
||||||
|
|
||||||
/*
|
/*
|
||||||
|
|
|
||||||
|
|
@ -30,5 +30,5 @@
|
||||||
"config": {
|
"config": {
|
||||||
"preferred-install": "dist"
|
"preferred-install": "dist"
|
||||||
},
|
},
|
||||||
"minimum-stability": "dev"
|
"minimum-stability": "stable"
|
||||||
}
|
}
|
||||||
|
|
|
||||||
BIN
composer.phar
BIN
composer.phar
Binary file not shown.
2
logs/.gitignore
vendored
Normal file
2
logs/.gitignore
vendored
Normal file
|
|
@ -0,0 +1,2 @@
|
||||||
|
*
|
||||||
|
!.gitignore
|
||||||
8
pony.fm.iml
Normal file
8
pony.fm.iml
Normal file
|
|
@ -0,0 +1,8 @@
|
||||||
|
<?xml version="1.0" encoding="UTF-8"?>
|
||||||
|
<module type="WEB_MODULE" version="4">
|
||||||
|
<component name="NewModuleRootManager" inherit-compiler-output="true">
|
||||||
|
<exclude-output />
|
||||||
|
<content url="file://$MODULE_DIR$" />
|
||||||
|
<orderEntry type="sourceFolder" forTests="false" />
|
||||||
|
</component>
|
||||||
|
</module>
|
||||||
|
|
@ -1,5 +1,5 @@
|
||||||
@import-once 'base/bootstrap/bootstrap';
|
@import 'base/bootstrap/bootstrap';
|
||||||
@import-once 'mixins';
|
@import 'mixins';
|
||||||
|
|
||||||
ul.playlists {
|
ul.playlists {
|
||||||
overflow-y: auto;
|
overflow-y: auto;
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,5 @@
|
||||||
@import-once 'base/bootstrap/bootstrap';
|
@import 'base/bootstrap/bootstrap';
|
||||||
@import-once 'mixins';
|
@import 'mixins';
|
||||||
|
|
||||||
.fade-hide, .fade-show {
|
.fade-hide, .fade-show {
|
||||||
.transition(all cubic-bezier(0.250, 0.460, 0.450, 0.940) 350ms);
|
.transition(all cubic-bezier(0.250, 0.460, 0.450, 0.940) 350ms);
|
||||||
|
|
|
||||||
|
|
@ -196,7 +196,7 @@
|
||||||
.navbar-static-top .container,
|
.navbar-static-top .container,
|
||||||
.navbar-fixed-top .container,
|
.navbar-fixed-top .container,
|
||||||
.navbar-fixed-bottom .container {
|
.navbar-fixed-bottom .container {
|
||||||
#grid > .core > .span(@gridColumns);
|
width: (@gridColumnWidth * @gridColumns) + (@gridGutterWidth * (@gridColumns - 1));
|
||||||
}
|
}
|
||||||
|
|
||||||
// Fixed to top
|
// Fixed to top
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,5 @@
|
||||||
@import-once 'variables';
|
@import 'variables';
|
||||||
@import-once 'base/bootstrap/bootstrap';
|
@import 'base/bootstrap/bootstrap';
|
||||||
|
|
||||||
a {
|
a {
|
||||||
color: #C2889C;
|
color: #C2889C;
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
@import-once 'base/bootstrap/bootstrap';
|
@import 'base/bootstrap/bootstrap';
|
||||||
@import-once 'mixins';
|
@import 'mixins';
|
||||||
@import-once 'variables';
|
@import 'variables';
|
||||||
|
|
||||||
.stretch-to-bottom {
|
.stretch-to-bottom {
|
||||||
overflow-y: auto;
|
overflow-y: auto;
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
@import-once 'base/bootstrap/bootstrap';
|
@import 'base/bootstrap/bootstrap';
|
||||||
@import-once 'mixins';
|
@import 'mixins';
|
||||||
@import-once 'variables';
|
@import 'variables';
|
||||||
|
|
||||||
@media (max-width: 1300px) and (min-width: 720px) {
|
@media (max-width: 1300px) and (min-width: 720px) {
|
||||||
html {
|
html {
|
||||||
|
|
|
||||||
|
|
@ -1,4 +1,4 @@
|
||||||
@import-once "base/bootstrap/bootstrap";
|
@import "base/bootstrap/bootstrap";
|
||||||
|
|
||||||
.dashboard {
|
.dashboard {
|
||||||
h1 {
|
h1 {
|
||||||
|
|
|
||||||
|
|
@ -1,4 +1,4 @@
|
||||||
@import-once "base/bootstrap/bootstrap";
|
@import "base/bootstrap/bootstrap";
|
||||||
|
|
||||||
.form-row {
|
.form-row {
|
||||||
margin-bottom: 10px;
|
margin-bottom: 10px;
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
@import-once 'base/bootstrap/bootstrap';
|
@import 'base/bootstrap/bootstrap';
|
||||||
@import-once 'mixins';
|
@import 'mixins';
|
||||||
@import-once 'variables';
|
@import 'variables';
|
||||||
|
|
||||||
html, body {
|
html, body {
|
||||||
}
|
}
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,5 @@
|
||||||
@import-once 'variables';
|
@import 'variables';
|
||||||
@import-once 'mixins';
|
@import 'mixins';
|
||||||
|
|
||||||
body.is-logged {
|
body.is-logged {
|
||||||
.track-player {
|
.track-player {
|
||||||
|
|
|
||||||
|
|
@ -1,4 +1,4 @@
|
||||||
@import-once 'variables';
|
@import 'variables';
|
||||||
|
|
||||||
.uploader {
|
.uploader {
|
||||||
h1 {
|
h1 {
|
||||||
|
|
|
||||||
14
vagrant/config/app.php
Normal file
14
vagrant/config/app.php
Normal file
|
|
@ -0,0 +1,14 @@
|
||||||
|
<?php
|
||||||
|
|
||||||
|
return array(
|
||||||
|
'sendfile' => true,
|
||||||
|
'uglify-js' => 'uglifyjs',
|
||||||
|
'uglify-css' => 'uglifycss',
|
||||||
|
'coffee' => 'coffee',
|
||||||
|
'debug' => true,
|
||||||
|
'url' => 'pony.fm.local',
|
||||||
|
'files_directory' => '/vagrant-files/',
|
||||||
|
'node' => null,
|
||||||
|
'node_paths' => ['node'],
|
||||||
|
'secure' => false,
|
||||||
|
);
|
||||||
5
vagrant/config/cache.php
Normal file
5
vagrant/config/cache.php
Normal file
|
|
@ -0,0 +1,5 @@
|
||||||
|
<?php
|
||||||
|
|
||||||
|
return array(
|
||||||
|
'driver' => 'database',
|
||||||
|
);
|
||||||
85
vagrant/config/database.php
Normal file
85
vagrant/config/database.php
Normal file
|
|
@ -0,0 +1,85 @@
|
||||||
|
<?php
|
||||||
|
|
||||||
|
return array(
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Default Database Connection Name
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| Here you may specify which of the database connections below you wish
|
||||||
|
| to use as your default connection for all database work. Of course
|
||||||
|
| you may use many connections at once using the Database library.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'default' => 'mysql',
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Database Connections
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| Here are each of the database connections setup for your application.
|
||||||
|
| Of course, examples of configuring each database platform that is
|
||||||
|
| supported by Laravel is shown below to make development simple.
|
||||||
|
|
|
||||||
|
|
|
||||||
|
| All database work in Laravel is done through the PHP PDO facilities
|
||||||
|
| so make sure you have the driver for your particular database of
|
||||||
|
| choice installed on your machine before you begin development.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'connections' => array(
|
||||||
|
|
||||||
|
'mysql' => array(
|
||||||
|
'driver' => 'mysql',
|
||||||
|
'host' => 'localhost',
|
||||||
|
'database' => 'homestead',
|
||||||
|
'username' => 'homestead',
|
||||||
|
'password' => 'secret',
|
||||||
|
'charset' => 'utf8',
|
||||||
|
'collation' => 'utf8_unicode_ci',
|
||||||
|
'prefix' => '',
|
||||||
|
),
|
||||||
|
|
||||||
|
),
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Migration Repository Table
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| This table keeps track of all the migrations that have already run for
|
||||||
|
| your application. Using this information, we can determine which of
|
||||||
|
| the migrations on disk have not actually be run in the databases.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'migrations' => 'migrations',
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Redis Databases
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| Redis is an open source, fast, and advanced key-value store that also
|
||||||
|
| provides a richer set of commands than a typical key-value systems
|
||||||
|
| such as APC or Memcached. Laravel makes it easy to dig right in.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'redis' => array(
|
||||||
|
|
||||||
|
'cluster' => true,
|
||||||
|
|
||||||
|
'default' => array(
|
||||||
|
'host' => '127.0.0.1',
|
||||||
|
'port' => 6379,
|
||||||
|
'database' => 0,
|
||||||
|
),
|
||||||
|
|
||||||
|
),
|
||||||
|
|
||||||
|
);
|
||||||
12
vagrant/config/poniverse.php
Normal file
12
vagrant/config/poniverse.php
Normal file
|
|
@ -0,0 +1,12 @@
|
||||||
|
<?php
|
||||||
|
return [
|
||||||
|
'version' => 1,
|
||||||
|
'urls' => [
|
||||||
|
'api' => 'http://api.poniverse.dev:83/v1/',
|
||||||
|
'register' => 'http://poniverse.dev:83/register?site=ponyfm',
|
||||||
|
'auth' => 'http://poniverse.dev:83/login/authorize',
|
||||||
|
'token' => 'http://api.poniverse.dev:83/v1/oauth2/token'
|
||||||
|
],
|
||||||
|
'client_id' => 'spa-ponyfm',
|
||||||
|
'secret' => 'mwRW6lfm19G9TaN60J0oMq2kapzU83n4'
|
||||||
|
];
|
||||||
125
vagrant/config/session.php
Normal file
125
vagrant/config/session.php
Normal file
|
|
@ -0,0 +1,125 @@
|
||||||
|
<?php
|
||||||
|
|
||||||
|
return array(
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Default Session Driver
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| This option controls the default session "driver" that will be used on
|
||||||
|
| requests. By default, we will use the lightweight native driver but
|
||||||
|
| you may specify any of the other wonderful drivers provided here.
|
||||||
|
|
|
||||||
|
| Supported: "native", "cookie", "database", "apc",
|
||||||
|
| "memcached", "redis", "array"
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'driver' => 'native',
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session Lifetime
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| Here you may specify the number of minutes that you wish the session
|
||||||
|
| to be allowed to remain idle for it is expired. If you want them
|
||||||
|
| to immediately expire when the browser closes, set it to zero.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'lifetime' => 120,
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session File Location
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| When using the native session driver, we need a location where session
|
||||||
|
| files may be stored. A default has been set for you but a different
|
||||||
|
| location may be specified. This is only needed for file sessions.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'files' => storage_path().'/sessions',
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session Database Connection
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| When using the "database" session driver, you may specify the database
|
||||||
|
| connection that should be used to manage your sessions. This should
|
||||||
|
| correspond to a connection in your "database" configuration file.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'connection' => null,
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session Database Table
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| When using the "database" session driver, you may specify the table we
|
||||||
|
| should use to manage the sessions. Of course, a sensible default is
|
||||||
|
| provided for you; however, you are free to change this as needed.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'table' => 'sessions',
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session Sweeping Lottery
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| Some session drivers must manually sweep their storage location to get
|
||||||
|
| rid of old sessions from storage. Here are the chances that it will
|
||||||
|
| happen on a given request. By default, the odds are 2 out of 100.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'lottery' => array(2, 100),
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session Cookie Name
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| Here you may change the name of the cookie used to identify a session
|
||||||
|
| instance by ID. The name specified here will get used every time a
|
||||||
|
| new session cookie is created by the framework for every driver.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'cookie' => 'laravel_session',
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session Cookie Path
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| The session cookie path determines the path for which the cookie will
|
||||||
|
| be regarded as available. Typically, this will be the root path of
|
||||||
|
| your application but you are free to change this when necessary.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'path' => '/',
|
||||||
|
|
||||||
|
/*
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
| Session Cookie Domain
|
||||||
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
||||||
|
| Here you may change the domain of the cookie used to identify a session
|
||||||
|
| in your application. This will determine which domains the cookie is
|
||||||
|
| available to in your application. A sensible default has been set.
|
||||||
|
|
|
||||||
|
*/
|
||||||
|
|
||||||
|
'domain' => null,
|
||||||
|
|
||||||
|
);
|
||||||
13
vagrant/copy-and-restart-configs.sh
Normal file
13
vagrant/copy-and-restart-configs.sh
Normal file
|
|
@ -0,0 +1,13 @@
|
||||||
|
sudo cp /vagrant/vagrant/pony.fm.nginx.config /etc/nginx/nginx.conf
|
||||||
|
sudo cp /vagrant/vagrant/pony.fm.nginx.site.config /etc/nginx/sites-enabled/pony.fm
|
||||||
|
|
||||||
|
sudo cp /vagrant/vagrant/pony.fm.mysql.config /etc/mysql/my.cnf
|
||||||
|
|
||||||
|
sudo cp /vagrant/vagrant/pony.fm.redis.config /etc/redis/redis.conf
|
||||||
|
|
||||||
|
sudo service nginx restart
|
||||||
|
sudo service php5-fpm restart
|
||||||
|
|
||||||
|
sudo service mysql restart
|
||||||
|
|
||||||
|
# todo: figure out how to restart redis
|
||||||
BIN
vagrant/elevator.exe
Normal file
BIN
vagrant/elevator.exe
Normal file
Binary file not shown.
19
vagrant/install.sh
Normal file
19
vagrant/install.sh
Normal file
|
|
@ -0,0 +1,19 @@
|
||||||
|
mkdir /vagrant/logs
|
||||||
|
/vagrant/vagrant/copy-and-restart-configs.sh
|
||||||
|
|
||||||
|
cd /vagrant
|
||||||
|
|
||||||
|
/usr/local/bin/composer self-update
|
||||||
|
composer install
|
||||||
|
|
||||||
|
sudo npm install -g bower
|
||||||
|
sudo npm install -g coffee-script
|
||||||
|
sudo npm install -g less
|
||||||
|
|
||||||
|
bower install --allow-root
|
||||||
|
|
||||||
|
cp -r /vagrant/vagrant/config/* "/vagrant/app/config/local"
|
||||||
|
|
||||||
|
php artisan migrate
|
||||||
|
php artisan migrate:refresh
|
||||||
|
php artisan db:seed
|
||||||
127
vagrant/pony.fm.mysql.config
Normal file
127
vagrant/pony.fm.mysql.config
Normal file
|
|
@ -0,0 +1,127 @@
|
||||||
|
#
|
||||||
|
# The MySQL database server configuration file.
|
||||||
|
#
|
||||||
|
# You can copy this to one of:
|
||||||
|
# - "/etc/mysql/my.cnf" to set global options,
|
||||||
|
# - "~/.my.cnf" to set user-specific options.
|
||||||
|
#
|
||||||
|
# One can use all long options that the program supports.
|
||||||
|
# Run program with --help to get a list of available options and with
|
||||||
|
# --print-defaults to see which it would actually understand and use.
|
||||||
|
#
|
||||||
|
# For explanations see
|
||||||
|
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
|
||||||
|
|
||||||
|
# This will be passed to all mysql clients
|
||||||
|
# It has been reported that passwords should be enclosed with ticks/quotes
|
||||||
|
# escpecially if they contain "#" chars...
|
||||||
|
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
|
||||||
|
[client]
|
||||||
|
port = 3306
|
||||||
|
socket = /var/run/mysqld/mysqld.sock
|
||||||
|
|
||||||
|
# Here is entries for some specific programs
|
||||||
|
# The following values assume you have at least 32M ram
|
||||||
|
|
||||||
|
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
|
||||||
|
[mysqld_safe]
|
||||||
|
socket = /var/run/mysqld/mysqld.sock
|
||||||
|
nice = 0
|
||||||
|
|
||||||
|
[mysqld]
|
||||||
|
#
|
||||||
|
# * Basic Settings
|
||||||
|
#
|
||||||
|
user = mysql
|
||||||
|
pid-file = /var/run/mysqld/mysqld.pid
|
||||||
|
socket = /var/run/mysqld/mysqld.sock
|
||||||
|
port = 3306
|
||||||
|
basedir = /usr
|
||||||
|
datadir = /var/lib/mysql
|
||||||
|
tmpdir = /tmp
|
||||||
|
lc-messages-dir = /usr/share/mysql
|
||||||
|
skip-external-locking
|
||||||
|
#
|
||||||
|
# Instead of skip-networking the default is now to listen only on
|
||||||
|
# localhost which is more compatible and is not less secure.
|
||||||
|
bind-address = 0.0.0.0
|
||||||
|
#
|
||||||
|
# * Fine Tuning
|
||||||
|
#
|
||||||
|
key_buffer = 16M
|
||||||
|
max_allowed_packet = 16M
|
||||||
|
thread_stack = 192K
|
||||||
|
thread_cache_size = 8
|
||||||
|
# This replaces the startup script and checks MyISAM tables if needed
|
||||||
|
# the first time they are touched
|
||||||
|
myisam-recover = BACKUP
|
||||||
|
#max_connections = 100
|
||||||
|
#table_cache = 64
|
||||||
|
#thread_concurrency = 10
|
||||||
|
#
|
||||||
|
# * Query Cache Configuration
|
||||||
|
#
|
||||||
|
query_cache_limit = 1M
|
||||||
|
query_cache_size = 16M
|
||||||
|
#
|
||||||
|
# * Logging and Replication
|
||||||
|
#
|
||||||
|
# Both location gets rotated by the cronjob.
|
||||||
|
# Be aware that this log type is a performance killer.
|
||||||
|
# As of 5.1 you can enable the log at runtime!
|
||||||
|
#general_log_file = /var/log/mysql/mysql.log
|
||||||
|
#general_log = 1
|
||||||
|
#
|
||||||
|
# Error log - should be very few entries.
|
||||||
|
#
|
||||||
|
log_error = /vagrant/logs/mysql-error.log
|
||||||
|
#
|
||||||
|
# Here you can see queries with especially long duration
|
||||||
|
#log_slow_queries = /var/log/mysql/mysql-slow.log
|
||||||
|
#long_query_time = 2
|
||||||
|
#log-queries-not-using-indexes
|
||||||
|
#
|
||||||
|
# The following can be used as easy to replay backup logs or for replication.
|
||||||
|
# note: if you are setting up a replication slave, see README.Debian about
|
||||||
|
# other settings you may need to change.
|
||||||
|
#server-id = 1
|
||||||
|
#log_bin = /var/log/mysql/mysql-bin.log
|
||||||
|
expire_logs_days = 10
|
||||||
|
max_binlog_size = 100M
|
||||||
|
#binlog_do_db = include_database_name
|
||||||
|
#binlog_ignore_db = include_database_name
|
||||||
|
#
|
||||||
|
# * InnoDB
|
||||||
|
#
|
||||||
|
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
|
||||||
|
# Read the manual for more InnoDB related options. There are many!
|
||||||
|
#
|
||||||
|
# * Security Features
|
||||||
|
#
|
||||||
|
# Read the manual, too, if you want chroot!
|
||||||
|
# chroot = /var/lib/mysql/
|
||||||
|
#
|
||||||
|
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
|
||||||
|
#
|
||||||
|
# ssl-ca=/etc/mysql/cacert.pem
|
||||||
|
# ssl-cert=/etc/mysql/server-cert.pem
|
||||||
|
# ssl-key=/etc/mysql/server-key.pem
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
[mysqldump]
|
||||||
|
quick
|
||||||
|
quote-names
|
||||||
|
max_allowed_packet = 16M
|
||||||
|
|
||||||
|
[mysql]
|
||||||
|
#no-auto-rehash # faster start of mysql but no tab completition
|
||||||
|
|
||||||
|
[isamchk]
|
||||||
|
key_buffer = 16M
|
||||||
|
|
||||||
|
#
|
||||||
|
# * IMPORTANT: Additional settings that can override those from this file!
|
||||||
|
# The files must end with '.cnf', otherwise they'll be ignored.
|
||||||
|
#
|
||||||
|
!includedir /etc/mysql/conf.d/
|
||||||
85
vagrant/pony.fm.nginx.config
Normal file
85
vagrant/pony.fm.nginx.config
Normal file
|
|
@ -0,0 +1,85 @@
|
||||||
|
user vagrant;
|
||||||
|
worker_processes 4;
|
||||||
|
pid /run/nginx.pid;
|
||||||
|
|
||||||
|
events {
|
||||||
|
worker_connections 768;
|
||||||
|
# multi_accept on;
|
||||||
|
}
|
||||||
|
|
||||||
|
http {
|
||||||
|
|
||||||
|
##
|
||||||
|
# Basic Settings
|
||||||
|
##
|
||||||
|
|
||||||
|
sendfile on;
|
||||||
|
tcp_nopush on;
|
||||||
|
tcp_nodelay on;
|
||||||
|
keepalive_timeout 65;
|
||||||
|
types_hash_max_size 2048;
|
||||||
|
# server_tokens off;
|
||||||
|
|
||||||
|
server_names_hash_bucket_size 64;
|
||||||
|
# server_name_in_redirect off;
|
||||||
|
|
||||||
|
include /etc/nginx/mime.types;
|
||||||
|
default_type application/octet-stream;
|
||||||
|
|
||||||
|
##
|
||||||
|
# SSL Settings
|
||||||
|
##
|
||||||
|
|
||||||
|
ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
|
||||||
|
ssl_prefer_server_ciphers on;
|
||||||
|
|
||||||
|
##
|
||||||
|
# Logging Settings
|
||||||
|
##
|
||||||
|
|
||||||
|
access_log /var/log/nginx/access.log;
|
||||||
|
error_log /var/log/nginx/error.log;
|
||||||
|
|
||||||
|
##
|
||||||
|
# Gzip Settings
|
||||||
|
##
|
||||||
|
|
||||||
|
gzip on;
|
||||||
|
gzip_disable "msie6";
|
||||||
|
|
||||||
|
# gzip_vary on;
|
||||||
|
# gzip_proxied any;
|
||||||
|
# gzip_comp_level 6;
|
||||||
|
# gzip_buffers 16 8k;
|
||||||
|
# gzip_http_version 1.1;
|
||||||
|
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;
|
||||||
|
|
||||||
|
##
|
||||||
|
# Virtual Host Configs
|
||||||
|
##
|
||||||
|
|
||||||
|
include /etc/nginx/conf.d/*.conf;
|
||||||
|
include /etc/nginx/sites-enabled/*;
|
||||||
|
}
|
||||||
|
|
||||||
|
|
||||||
|
#mail {
|
||||||
|
# # See sample authentication script at:
|
||||||
|
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
|
||||||
|
#
|
||||||
|
# # auth_http localhost/auth.php;
|
||||||
|
# # pop3_capabilities "TOP" "USER";
|
||||||
|
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
|
||||||
|
#
|
||||||
|
# server {
|
||||||
|
# listen localhost:110;
|
||||||
|
# protocol pop3;
|
||||||
|
# proxy on;
|
||||||
|
# }
|
||||||
|
#
|
||||||
|
# server {
|
||||||
|
# listen localhost:143;
|
||||||
|
# protocol imap;
|
||||||
|
# proxy on;
|
||||||
|
# }
|
||||||
|
#}
|
||||||
46
vagrant/pony.fm.nginx.site.config
Normal file
46
vagrant/pony.fm.nginx.site.config
Normal file
|
|
@ -0,0 +1,46 @@
|
||||||
|
server {
|
||||||
|
listen 80;
|
||||||
|
|
||||||
|
gzip on;
|
||||||
|
gzip_comp_level 4;
|
||||||
|
gzip_min_length 1280;
|
||||||
|
gzip_types text/plain text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript image/x-icon image/bmp application/json;
|
||||||
|
gzip_vary on;
|
||||||
|
|
||||||
|
server_name pony.fm.local api.pony.fm.local;
|
||||||
|
access_log /vagrant/logs/nginx-access.log;
|
||||||
|
error_log /vagrant/logs/nginx-error.log;
|
||||||
|
root /vagrant/public;
|
||||||
|
|
||||||
|
location / {
|
||||||
|
index index.html index.php;
|
||||||
|
location ~* \.(?:ttf|ttc|otf|eot|woff|font.css)$ {
|
||||||
|
add_header "Access-Control-Allow-Origin" "*";
|
||||||
|
}
|
||||||
|
|
||||||
|
if (!-e $request_filename) {
|
||||||
|
rewrite ^/(.*)$ /index.php?/$1 last;
|
||||||
|
break;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
location ~ \.php$ {
|
||||||
|
fastcgi_split_path_info ^(.+\.php)(/.+)$;
|
||||||
|
fastcgi_pass unix:/var/run/php5-fpm.sock;
|
||||||
|
fastcgi_index index.php;
|
||||||
|
include fastcgi_params;
|
||||||
|
}
|
||||||
|
|
||||||
|
expires off;
|
||||||
|
|
||||||
|
rewrite ^/(.*\.(?:coffee))$ /asset.php?type=coffee&file=/$1 break;
|
||||||
|
rewrite ^/(.*\.(?:less))$ /asset.php?type=less&file=/$1 break;
|
||||||
|
|
||||||
|
error_page 404 /index.php;
|
||||||
|
error_page 403 /403.html;
|
||||||
|
|
||||||
|
location /vagrant-files {
|
||||||
|
internal;
|
||||||
|
alias /vagrant-files/;
|
||||||
|
}
|
||||||
|
}
|
||||||
696
vagrant/pony.fm.redis.config
Normal file
696
vagrant/pony.fm.redis.config
Normal file
|
|
@ -0,0 +1,696 @@
|
||||||
|
# Redis configuration file example
|
||||||
|
|
||||||
|
# Note on units: when memory size is needed, it is possible to specify
|
||||||
|
# it in the usual form of 1k 5GB 4M and so forth:
|
||||||
|
#
|
||||||
|
# 1k => 1000 bytes
|
||||||
|
# 1kb => 1024 bytes
|
||||||
|
# 1m => 1000000 bytes
|
||||||
|
# 1mb => 1024*1024 bytes
|
||||||
|
# 1g => 1000000000 bytes
|
||||||
|
# 1gb => 1024*1024*1024 bytes
|
||||||
|
#
|
||||||
|
# units are case insensitive so 1GB 1Gb 1gB are all the same.
|
||||||
|
|
||||||
|
# By default Redis does not run as a daemon. Use 'yes' if you need it.
|
||||||
|
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
|
||||||
|
daemonize yes
|
||||||
|
|
||||||
|
# When running daemonized, Redis writes a pid file in /var/run/redis.pid by
|
||||||
|
# default. You can specify a custom pid file location here.
|
||||||
|
pidfile /var/run/redis/redis.pid
|
||||||
|
|
||||||
|
# Accept connections on the specified port, default is 6379.
|
||||||
|
# If port 0 is specified Redis will not listen on a TCP socket.
|
||||||
|
port 6379
|
||||||
|
|
||||||
|
# By default Redis listens for connections from all the network interfaces
|
||||||
|
# available on the server. It is possible to listen to just one or multiple
|
||||||
|
# interfaces using the "bind" configuration directive, followed by one or
|
||||||
|
# more IP addresses.
|
||||||
|
#
|
||||||
|
# Examples:
|
||||||
|
#
|
||||||
|
# bind 192.168.1.100 10.0.0.1
|
||||||
|
# bind 127.0.0.1
|
||||||
|
|
||||||
|
# Specify the path for the unix socket that will be used to listen for
|
||||||
|
# incoming connections. There is no default, so Redis will not listen
|
||||||
|
# on a unix socket when not specified.
|
||||||
|
#
|
||||||
|
# unixsocket /tmp/redis.sock
|
||||||
|
# unixsocketperm 755
|
||||||
|
|
||||||
|
# Close the connection after a client is idle for N seconds (0 to disable)
|
||||||
|
timeout 0
|
||||||
|
|
||||||
|
# TCP keepalive.
|
||||||
|
#
|
||||||
|
# If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
|
||||||
|
# of communication. This is useful for two reasons:
|
||||||
|
#
|
||||||
|
# 1) Detect dead peers.
|
||||||
|
# 2) Take the connection alive from the point of view of network
|
||||||
|
# equipment in the middle.
|
||||||
|
#
|
||||||
|
# On Linux, the specified value (in seconds) is the period used to send ACKs.
|
||||||
|
# Note that to close the connection the double of the time is needed.
|
||||||
|
# On other kernels the period depends on the kernel configuration.
|
||||||
|
#
|
||||||
|
# A reasonable value for this option is 60 seconds.
|
||||||
|
tcp-keepalive 0
|
||||||
|
|
||||||
|
# Specify the server verbosity level.
|
||||||
|
# This can be one of:
|
||||||
|
# debug (a lot of information, useful for development/testing)
|
||||||
|
# verbose (many rarely useful info, but not a mess like the debug level)
|
||||||
|
# notice (moderately verbose, what you want in production probably)
|
||||||
|
# warning (only very important / critical messages are logged)
|
||||||
|
loglevel notice
|
||||||
|
|
||||||
|
# Specify the log file name. Also the emptry string can be used to force
|
||||||
|
# Redis to log on the standard output. Note that if you use standard
|
||||||
|
# output for logging but daemonize, logs will be sent to /dev/null
|
||||||
|
logfile /dev/null
|
||||||
|
|
||||||
|
# To enable logging to the system logger, just set 'syslog-enabled' to yes,
|
||||||
|
# and optionally update the other syslog parameters to suit your needs.
|
||||||
|
syslog-enabled yes
|
||||||
|
|
||||||
|
# Specify the syslog identity.
|
||||||
|
# syslog-ident redis
|
||||||
|
|
||||||
|
# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
|
||||||
|
# syslog-facility local0
|
||||||
|
|
||||||
|
# Set the number of databases. The default database is DB 0, you can select
|
||||||
|
# a different one on a per-connection basis using SELECT <dbid> where
|
||||||
|
# dbid is a number between 0 and 'databases'-1
|
||||||
|
databases 16
|
||||||
|
|
||||||
|
################################ SNAPSHOTTING #################################
|
||||||
|
#
|
||||||
|
# Save the DB on disk:
|
||||||
|
#
|
||||||
|
# save <seconds> <changes>
|
||||||
|
#
|
||||||
|
# Will save the DB if both the given number of seconds and the given
|
||||||
|
# number of write operations against the DB occurred.
|
||||||
|
#
|
||||||
|
# In the example below the behaviour will be to save:
|
||||||
|
# after 900 sec (15 min) if at least 1 key changed
|
||||||
|
# after 300 sec (5 min) if at least 10 keys changed
|
||||||
|
# after 60 sec if at least 10000 keys changed
|
||||||
|
#
|
||||||
|
# Note: you can disable saving at all commenting all the "save" lines.
|
||||||
|
#
|
||||||
|
# It is also possible to remove all the previously configured save
|
||||||
|
# points by adding a save directive with a single empty string argument
|
||||||
|
# like in the following example:
|
||||||
|
#
|
||||||
|
# save ""
|
||||||
|
|
||||||
|
save 900 1
|
||||||
|
save 300 10
|
||||||
|
save 60 10000
|
||||||
|
|
||||||
|
# By default Redis will stop accepting writes if RDB snapshots are enabled
|
||||||
|
# (at least one save point) and the latest background save failed.
|
||||||
|
# This will make the user aware (in an hard way) that data is not persisting
|
||||||
|
# on disk properly, otherwise chances are that no one will notice and some
|
||||||
|
# distater will happen.
|
||||||
|
#
|
||||||
|
# If the background saving process will start working again Redis will
|
||||||
|
# automatically allow writes again.
|
||||||
|
#
|
||||||
|
# However if you have setup your proper monitoring of the Redis server
|
||||||
|
# and persistence, you may want to disable this feature so that Redis will
|
||||||
|
# continue to work as usually even if there are problems with disk,
|
||||||
|
# permissions, and so forth.
|
||||||
|
stop-writes-on-bgsave-error yes
|
||||||
|
|
||||||
|
# Compress string objects using LZF when dump .rdb databases?
|
||||||
|
# For default that's set to 'yes' as it's almost always a win.
|
||||||
|
# If you want to save some CPU in the saving child set it to 'no' but
|
||||||
|
# the dataset will likely be bigger if you have compressible values or keys.
|
||||||
|
rdbcompression yes
|
||||||
|
|
||||||
|
# Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
|
||||||
|
# This makes the format more resistant to corruption but there is a performance
|
||||||
|
# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
|
||||||
|
# for maximum performances.
|
||||||
|
#
|
||||||
|
# RDB files created with checksum disabled have a checksum of zero that will
|
||||||
|
# tell the loading code to skip the check.
|
||||||
|
rdbchecksum yes
|
||||||
|
|
||||||
|
# The filename where to dump the DB
|
||||||
|
dbfilename redis.rdb
|
||||||
|
|
||||||
|
# The working directory.
|
||||||
|
#
|
||||||
|
# The DB will be written inside this directory, with the filename specified
|
||||||
|
# above using the 'dbfilename' configuration directive.
|
||||||
|
#
|
||||||
|
# The Append Only File will also be created inside this directory.
|
||||||
|
#
|
||||||
|
# Note that you must specify a directory here, not a file name.
|
||||||
|
dir /var/lib/redis/
|
||||||
|
|
||||||
|
################################# REPLICATION #################################
|
||||||
|
|
||||||
|
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
|
||||||
|
# another Redis server. Note that the configuration is local to the slave
|
||||||
|
# so for example it is possible to configure the slave to save the DB with a
|
||||||
|
# different interval, or to listen to another port, and so on.
|
||||||
|
#
|
||||||
|
# slaveof <masterip> <masterport>
|
||||||
|
|
||||||
|
# If the master is password protected (using the "requirepass" configuration
|
||||||
|
# directive below) it is possible to tell the slave to authenticate before
|
||||||
|
# starting the replication synchronization process, otherwise the master will
|
||||||
|
# refuse the slave request.
|
||||||
|
#
|
||||||
|
# masterauth <master-password>
|
||||||
|
|
||||||
|
# When a slave loses its connection with the master, or when the replication
|
||||||
|
# is still in progress, the slave can act in two different ways:
|
||||||
|
#
|
||||||
|
# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
|
||||||
|
# still reply to client requests, possibly with out of date data, or the
|
||||||
|
# data set may just be empty if this is the first synchronization.
|
||||||
|
#
|
||||||
|
# 2) if slave-serve-stale-data is set to 'no' the slave will reply with
|
||||||
|
# an error "SYNC with master in progress" to all the kind of commands
|
||||||
|
# but to INFO and SLAVEOF.
|
||||||
|
#
|
||||||
|
slave-serve-stale-data yes
|
||||||
|
|
||||||
|
# You can configure a slave instance to accept writes or not. Writing against
|
||||||
|
# a slave instance may be useful to store some ephemeral data (because data
|
||||||
|
# written on a slave will be easily deleted after resync with the master) but
|
||||||
|
# may also cause problems if clients are writing to it because of a
|
||||||
|
# misconfiguration.
|
||||||
|
#
|
||||||
|
# Since Redis 2.6 by default slaves are read-only.
|
||||||
|
#
|
||||||
|
# Note: read only slaves are not designed to be exposed to untrusted clients
|
||||||
|
# on the internet. It's just a protection layer against misuse of the instance.
|
||||||
|
# Still a read only slave exports by default all the administrative commands
|
||||||
|
# such as CONFIG, DEBUG, and so forth. To a limited extend you can improve
|
||||||
|
# security of read only slaves using 'rename-command' to shadow all the
|
||||||
|
# administrative / dangerous commands.
|
||||||
|
slave-read-only yes
|
||||||
|
|
||||||
|
# Slaves send PINGs to server in a predefined interval. It's possible to change
|
||||||
|
# this interval with the repl_ping_slave_period option. The default value is 10
|
||||||
|
# seconds.
|
||||||
|
#
|
||||||
|
# repl-ping-slave-period 10
|
||||||
|
|
||||||
|
# The following option sets the replication timeout for:
|
||||||
|
#
|
||||||
|
# 1) Bulk transfer I/O during SYNC, from the point of view of slave.
|
||||||
|
# 2) Master timeout from the point of view of slaves (data, pings).
|
||||||
|
# 3) Slave timeout from the point of view of masters (REPLCONF ACK pings).
|
||||||
|
#
|
||||||
|
# It is important to make sure that this value is greater than the value
|
||||||
|
# specified for repl-ping-slave-period otherwise a timeout will be detected
|
||||||
|
# every time there is low traffic between the master and the slave.
|
||||||
|
#
|
||||||
|
# repl-timeout 60
|
||||||
|
|
||||||
|
# Disable TCP_NODELAY on the slave socket after SYNC?
|
||||||
|
#
|
||||||
|
# If you select "yes" Redis will use a smaller number of TCP packets and
|
||||||
|
# less bandwidth to send data to slaves. But this can add a delay for
|
||||||
|
# the data to appear on the slave side, up to 40 milliseconds with
|
||||||
|
# Linux kernels using a default configuration.
|
||||||
|
#
|
||||||
|
# If you select "no" the delay for data to appear on the slave side will
|
||||||
|
# be reduced but more bandwidth will be used for replication.
|
||||||
|
#
|
||||||
|
# By default we optimize for low latency, but in very high traffic conditions
|
||||||
|
# or when the master and slaves are many hops away, turning this to "yes" may
|
||||||
|
# be a good idea.
|
||||||
|
repl-disable-tcp-nodelay no
|
||||||
|
|
||||||
|
# Set the replication backlog size. The backlog is a buffer that accumulates
|
||||||
|
# slave data when slaves are disconnected for some time, so that when a slave
|
||||||
|
# wants to reconnect again, often a full resync is not needed, but a partial
|
||||||
|
# resync is enough, just passing the portion of data the slave missed while
|
||||||
|
# disconnected.
|
||||||
|
#
|
||||||
|
# The biggest the replication backlog, the longer the time the slave can be
|
||||||
|
# disconnected and later be able to perform a partial resynchronization.
|
||||||
|
#
|
||||||
|
# The backlog is only allocated once there is at least a slave connected.
|
||||||
|
#
|
||||||
|
# repl-backlog-size 1mb
|
||||||
|
|
||||||
|
# After a master has no longer connected slaves for some time, the backlog
|
||||||
|
# will be freed. The following option configures the amount of seconds that
|
||||||
|
# need to elapse, starting from the time the last slave disconnected, for
|
||||||
|
# the backlog buffer to be freed.
|
||||||
|
#
|
||||||
|
# A value of 0 means to never release the backlog.
|
||||||
|
#
|
||||||
|
# repl-backlog-ttl 3600
|
||||||
|
|
||||||
|
# The slave priority is an integer number published by Redis in the INFO output.
|
||||||
|
# It is used by Redis Sentinel in order to select a slave to promote into a
|
||||||
|
# master if the master is no longer working correctly.
|
||||||
|
#
|
||||||
|
# A slave with a low priority number is considered better for promotion, so
|
||||||
|
# for instance if there are three slaves with priority 10, 100, 25 Sentinel will
|
||||||
|
# pick the one wtih priority 10, that is the lowest.
|
||||||
|
#
|
||||||
|
# However a special priority of 0 marks the slave as not able to perform the
|
||||||
|
# role of master, so a slave with priority of 0 will never be selected by
|
||||||
|
# Redis Sentinel for promotion.
|
||||||
|
#
|
||||||
|
# By default the priority is 100.
|
||||||
|
slave-priority 100
|
||||||
|
|
||||||
|
# It is possible for a master to stop accepting writes if there are less than
|
||||||
|
# N slaves connected, having a lag less or equal than M seconds.
|
||||||
|
#
|
||||||
|
# The N slaves need to be in "online" state.
|
||||||
|
#
|
||||||
|
# The lag in seconds, that must be <= the specified value, is calculated from
|
||||||
|
# the last ping received from the slave, that is usually sent every second.
|
||||||
|
#
|
||||||
|
# This option does not GUARANTEES that N replicas will accept the write, but
|
||||||
|
# will limit the window of exposure for lost writes in case not enough slaves
|
||||||
|
# are available, to the specified number of seconds.
|
||||||
|
#
|
||||||
|
# For example to require at least 3 slaves with a lag <= 10 seconds use:
|
||||||
|
#
|
||||||
|
# min-slaves-to-write 3
|
||||||
|
# min-slaves-max-lag 10
|
||||||
|
#
|
||||||
|
# Setting one or the other to 0 disables the feature.
|
||||||
|
#
|
||||||
|
# By default min-slaves-to-write is set to 0 (feature disabled) and
|
||||||
|
# min-slaves-max-lag is set to 10.
|
||||||
|
|
||||||
|
################################## SECURITY ###################################
|
||||||
|
|
||||||
|
# Require clients to issue AUTH <PASSWORD> before processing any other
|
||||||
|
# commands. This might be useful in environments in which you do not trust
|
||||||
|
# others with access to the host running redis-server.
|
||||||
|
#
|
||||||
|
# This should stay commented out for backward compatibility and because most
|
||||||
|
# people do not need auth (e.g. they run their own servers).
|
||||||
|
#
|
||||||
|
# Warning: since Redis is pretty fast an outside user can try up to
|
||||||
|
# 150k passwords per second against a good box. This means that you should
|
||||||
|
# use a very strong password otherwise it will be very easy to break.
|
||||||
|
#
|
||||||
|
# requirepass foobared
|
||||||
|
|
||||||
|
# Command renaming.
|
||||||
|
#
|
||||||
|
# It is possible to change the name of dangerous commands in a shared
|
||||||
|
# environment. For instance the CONFIG command may be renamed into something
|
||||||
|
# hard to guess so that it will still be available for internal-use tools
|
||||||
|
# but not available for general clients.
|
||||||
|
#
|
||||||
|
# Example:
|
||||||
|
#
|
||||||
|
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
|
||||||
|
#
|
||||||
|
# It is also possible to completely kill a command by renaming it into
|
||||||
|
# an empty string:
|
||||||
|
#
|
||||||
|
# rename-command CONFIG ""
|
||||||
|
#
|
||||||
|
# Please note that changing the name of commands that are logged into the
|
||||||
|
# AOF file or transmitted to slaves may cause problems.
|
||||||
|
|
||||||
|
################################### LIMITS ####################################
|
||||||
|
|
||||||
|
# Set the max number of connected clients at the same time. By default
|
||||||
|
# this limit is set to 10000 clients, however if the Redis server is not
|
||||||
|
# able to configure the process file limit to allow for the specified limit
|
||||||
|
# the max number of allowed clients is set to the current file limit
|
||||||
|
# minus 32 (as Redis reserves a few file descriptors for internal uses).
|
||||||
|
#
|
||||||
|
# Once the limit is reached Redis will close all the new connections sending
|
||||||
|
# an error 'max number of clients reached'.
|
||||||
|
#
|
||||||
|
# maxclients 10000
|
||||||
|
|
||||||
|
# Don't use more memory than the specified amount of bytes.
|
||||||
|
# When the memory limit is reached Redis will try to remove keys
|
||||||
|
# accordingly to the eviction policy selected (see maxmemmory-policy).
|
||||||
|
#
|
||||||
|
# If Redis can't remove keys according to the policy, or if the policy is
|
||||||
|
# set to 'noeviction', Redis will start to reply with errors to commands
|
||||||
|
# that would use more memory, like SET, LPUSH, and so on, and will continue
|
||||||
|
# to reply to read-only commands like GET.
|
||||||
|
#
|
||||||
|
# This option is usually useful when using Redis as an LRU cache, or to set
|
||||||
|
# an hard memory limit for an instance (using the 'noeviction' policy).
|
||||||
|
#
|
||||||
|
# WARNING: If you have slaves attached to an instance with maxmemory on,
|
||||||
|
# the size of the output buffers needed to feed the slaves are subtracted
|
||||||
|
# from the used memory count, so that network problems / resyncs will
|
||||||
|
# not trigger a loop where keys are evicted, and in turn the output
|
||||||
|
# buffer of slaves is full with DELs of keys evicted triggering the deletion
|
||||||
|
# of more keys, and so forth until the database is completely emptied.
|
||||||
|
#
|
||||||
|
# In short... if you have slaves attached it is suggested that you set a lower
|
||||||
|
# limit for maxmemory so that there is some free RAM on the system for slave
|
||||||
|
# output buffers (but this is not needed if the policy is 'noeviction').
|
||||||
|
#
|
||||||
|
# maxmemory <bytes>
|
||||||
|
|
||||||
|
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
|
||||||
|
# is reached. You can select among five behaviors:
|
||||||
|
#
|
||||||
|
# volatile-lru -> remove the key with an expire set using an LRU algorithm
|
||||||
|
# allkeys-lru -> remove any key accordingly to the LRU algorithm
|
||||||
|
# volatile-random -> remove a random key with an expire set
|
||||||
|
# allkeys-random -> remove a random key, any key
|
||||||
|
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
|
||||||
|
# noeviction -> don't expire at all, just return an error on write operations
|
||||||
|
#
|
||||||
|
# Note: with any of the above policies, Redis will return an error on write
|
||||||
|
# operations, when there are not suitable keys for eviction.
|
||||||
|
#
|
||||||
|
# At the date of writing this commands are: set setnx setex append
|
||||||
|
# incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
|
||||||
|
# sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
|
||||||
|
# zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
|
||||||
|
# getset mset msetnx exec sort
|
||||||
|
#
|
||||||
|
# The default is:
|
||||||
|
#
|
||||||
|
# maxmemory-policy volatile-lru
|
||||||
|
|
||||||
|
# LRU and minimal TTL algorithms are not precise algorithms but approximated
|
||||||
|
# algorithms (in order to save memory), so you can select as well the sample
|
||||||
|
# size to check. For instance for default Redis will check three keys and
|
||||||
|
# pick the one that was used less recently, you can change the sample size
|
||||||
|
# using the following configuration directive.
|
||||||
|
#
|
||||||
|
# maxmemory-samples 3
|
||||||
|
|
||||||
|
############################## APPEND ONLY MODE ###############################
|
||||||
|
|
||||||
|
# By default Redis asynchronously dumps the dataset on disk. This mode is
|
||||||
|
# good enough in many applications, but an issue with the Redis process or
|
||||||
|
# a power outage may result into a few minutes of writes lost (depending on
|
||||||
|
# the configured save points).
|
||||||
|
#
|
||||||
|
# The Append Only File is an alternative persistence mode that provides
|
||||||
|
# much better durability. For instance using the default data fsync policy
|
||||||
|
# (see later in the config file) Redis can lose just one second of writes in a
|
||||||
|
# dramatic event like a server power outage, or a single write if something
|
||||||
|
# wrong with the Redis process itself happens, but the operating system is
|
||||||
|
# still running correctly.
|
||||||
|
#
|
||||||
|
# AOF and RDB persistence can be enabled at the same time without problems.
|
||||||
|
# If the AOF is enabled on startup Redis will load the AOF, that is the file
|
||||||
|
# with the better durability guarantees.
|
||||||
|
#
|
||||||
|
# Please check http://redis.io/topics/persistence for more information.
|
||||||
|
|
||||||
|
appendonly no
|
||||||
|
|
||||||
|
# The name of the append only file (default: "appendonly.aof")
|
||||||
|
# appendfilename appendonly.aof
|
||||||
|
|
||||||
|
# The fsync() call tells the Operating System to actually write data on disk
|
||||||
|
# instead to wait for more data in the output buffer. Some OS will really flush
|
||||||
|
# data on disk, some other OS will just try to do it ASAP.
|
||||||
|
#
|
||||||
|
# Redis supports three different modes:
|
||||||
|
#
|
||||||
|
# no: don't fsync, just let the OS flush the data when it wants. Faster.
|
||||||
|
# always: fsync after every write to the append only log . Slow, Safest.
|
||||||
|
# everysec: fsync only one time every second. Compromise.
|
||||||
|
#
|
||||||
|
# The default is "everysec", as that's usually the right compromise between
|
||||||
|
# speed and data safety. It's up to you to understand if you can relax this to
|
||||||
|
# "no" that will let the operating system flush the output buffer when
|
||||||
|
# it wants, for better performances (but if you can live with the idea of
|
||||||
|
# some data loss consider the default persistence mode that's snapshotting),
|
||||||
|
# or on the contrary, use "always" that's very slow but a bit safer than
|
||||||
|
# everysec.
|
||||||
|
#
|
||||||
|
# More details please check the following article:
|
||||||
|
# http://antirez.com/post/redis-persistence-demystified.html
|
||||||
|
#
|
||||||
|
# If unsure, use "everysec".
|
||||||
|
|
||||||
|
# appendfsync always
|
||||||
|
appendfsync everysec
|
||||||
|
# appendfsync no
|
||||||
|
|
||||||
|
# When the AOF fsync policy is set to always or everysec, and a background
|
||||||
|
# saving process (a background save or AOF log background rewriting) is
|
||||||
|
# performing a lot of I/O against the disk, in some Linux configurations
|
||||||
|
# Redis may block too long on the fsync() call. Note that there is no fix for
|
||||||
|
# this currently, as even performing fsync in a different thread will block
|
||||||
|
# our synchronous write(2) call.
|
||||||
|
#
|
||||||
|
# In order to mitigate this problem it's possible to use the following option
|
||||||
|
# that will prevent fsync() from being called in the main process while a
|
||||||
|
# BGSAVE or BGREWRITEAOF is in progress.
|
||||||
|
#
|
||||||
|
# This means that while another child is saving, the durability of Redis is
|
||||||
|
# the same as "appendfsync none". In practical terms, this means that it is
|
||||||
|
# possible to lose up to 30 seconds of log in the worst scenario (with the
|
||||||
|
# default Linux settings).
|
||||||
|
#
|
||||||
|
# If you have latency problems turn this to "yes". Otherwise leave it as
|
||||||
|
# "no" that is the safest pick from the point of view of durability.
|
||||||
|
no-appendfsync-on-rewrite no
|
||||||
|
|
||||||
|
# Automatic rewrite of the append only file.
|
||||||
|
# Redis is able to automatically rewrite the log file implicitly calling
|
||||||
|
# BGREWRITEAOF when the AOF log size grows by the specified percentage.
|
||||||
|
#
|
||||||
|
# This is how it works: Redis remembers the size of the AOF file after the
|
||||||
|
# latest rewrite (if no rewrite has happened since the restart, the size of
|
||||||
|
# the AOF at startup is used).
|
||||||
|
#
|
||||||
|
# This base size is compared to the current size. If the current size is
|
||||||
|
# bigger than the specified percentage, the rewrite is triggered. Also
|
||||||
|
# you need to specify a minimal size for the AOF file to be rewritten, this
|
||||||
|
# is useful to avoid rewriting the AOF file even if the percentage increase
|
||||||
|
# is reached but it is still pretty small.
|
||||||
|
#
|
||||||
|
# Specify a percentage of zero in order to disable the automatic AOF
|
||||||
|
# rewrite feature.
|
||||||
|
|
||||||
|
auto-aof-rewrite-percentage 100
|
||||||
|
auto-aof-rewrite-min-size 64mb
|
||||||
|
|
||||||
|
################################ LUA SCRIPTING ###############################
|
||||||
|
|
||||||
|
# Max execution time of a Lua script in milliseconds.
|
||||||
|
#
|
||||||
|
# If the maximum execution time is reached Redis will log that a script is
|
||||||
|
# still in execution after the maximum allowed time and will start to
|
||||||
|
# reply to queries with an error.
|
||||||
|
#
|
||||||
|
# When a long running script exceed the maximum execution time only the
|
||||||
|
# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
|
||||||
|
# used to stop a script that did not yet called write commands. The second
|
||||||
|
# is the only way to shut down the server in the case a write commands was
|
||||||
|
# already issue by the script but the user don't want to wait for the natural
|
||||||
|
# termination of the script.
|
||||||
|
#
|
||||||
|
# Set it to 0 or a negative value for unlimited execution without warnings.
|
||||||
|
lua-time-limit 5000
|
||||||
|
|
||||||
|
################################## SLOW LOG ###################################
|
||||||
|
|
||||||
|
# The Redis Slow Log is a system to log queries that exceeded a specified
|
||||||
|
# execution time. The execution time does not include the I/O operations
|
||||||
|
# like talking with the client, sending the reply and so forth,
|
||||||
|
# but just the time needed to actually execute the command (this is the only
|
||||||
|
# stage of command execution where the thread is blocked and can not serve
|
||||||
|
# other requests in the meantime).
|
||||||
|
#
|
||||||
|
# You can configure the slow log with two parameters: one tells Redis
|
||||||
|
# what is the execution time, in microseconds, to exceed in order for the
|
||||||
|
# command to get logged, and the other parameter is the length of the
|
||||||
|
# slow log. When a new command is logged the oldest one is removed from the
|
||||||
|
# queue of logged commands.
|
||||||
|
|
||||||
|
# The following time is expressed in microseconds, so 1000000 is equivalent
|
||||||
|
# to one second. Note that a negative number disables the slow log, while
|
||||||
|
# a value of zero forces the logging of every command.
|
||||||
|
slowlog-log-slower-than 10000
|
||||||
|
|
||||||
|
# There is no limit to this length. Just be aware that it will consume memory.
|
||||||
|
# You can reclaim memory used by the slow log with SLOWLOG RESET.
|
||||||
|
slowlog-max-len 128
|
||||||
|
|
||||||
|
############################# Event notification ##############################
|
||||||
|
|
||||||
|
# Redis can notify Pub/Sub clients about events happening in the key space.
|
||||||
|
# This feature is documented at http://redis.io/topics/keyspace-events
|
||||||
|
#
|
||||||
|
# For instance if keyspace events notification is enabled, and a client
|
||||||
|
# performs a DEL operation on key "foo" stored in the Database 0, two
|
||||||
|
# messages will be published via Pub/Sub:
|
||||||
|
#
|
||||||
|
# PUBLISH __keyspace@0__:foo del
|
||||||
|
# PUBLISH __keyevent@0__:del foo
|
||||||
|
#
|
||||||
|
# It is possible to select the events that Redis will notify among a set
|
||||||
|
# of classes. Every class is identified by a single character:
|
||||||
|
#
|
||||||
|
# K Keyspace events, published with __keyspace@<db>__ prefix.
|
||||||
|
# E Keyevent events, published with __keyevent@<db>__ prefix.
|
||||||
|
# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
|
||||||
|
# $ String commands
|
||||||
|
# l List commands
|
||||||
|
# s Set commands
|
||||||
|
# h Hash commands
|
||||||
|
# z Sorted set commands
|
||||||
|
# x Expired events (events generated every time a key expires)
|
||||||
|
# e Evicted events (events generated when a key is evicted for maxmemory)
|
||||||
|
# A Alias for g$lshzxe, so that the "AKE" string means all the events.
|
||||||
|
#
|
||||||
|
# The "notify-keyspace-events" takes as argument a string that is composed
|
||||||
|
# by zero or multiple characters. The empty string means that notifications
|
||||||
|
# are disabled at all.
|
||||||
|
#
|
||||||
|
# Example: to enable list and generic events, from the point of view of the
|
||||||
|
# event name, use:
|
||||||
|
#
|
||||||
|
# notify-keyspace-events Elg
|
||||||
|
#
|
||||||
|
# Example 2: to get the stream of the expired keys subscribing to channel
|
||||||
|
# name __keyevent@0__:expired use:
|
||||||
|
#
|
||||||
|
# notify-keyspace-events Ex
|
||||||
|
#
|
||||||
|
# By default all notifications are disabled because most users don't need
|
||||||
|
# this feature and the feature has some overhead. Note that if you don't
|
||||||
|
# specify at least one of K or E, no events will be delivered.
|
||||||
|
notify-keyspace-events ""
|
||||||
|
|
||||||
|
############################### ADVANCED CONFIG ###############################
|
||||||
|
|
||||||
|
# Hashes are encoded using a memory efficient data structure when they have a
|
||||||
|
# small number of entries, and the biggest entry does not exceed a given
|
||||||
|
# threshold. These thresholds can be configured using the following directives.
|
||||||
|
hash-max-ziplist-entries 512
|
||||||
|
hash-max-ziplist-value 64
|
||||||
|
|
||||||
|
# Similarly to hashes, small lists are also encoded in a special way in order
|
||||||
|
# to save a lot of space. The special representation is only used when
|
||||||
|
# you are under the following limits:
|
||||||
|
list-max-ziplist-entries 512
|
||||||
|
list-max-ziplist-value 64
|
||||||
|
|
||||||
|
# Sets have a special encoding in just one case: when a set is composed
|
||||||
|
# of just strings that happens to be integers in radix 10 in the range
|
||||||
|
# of 64 bit signed integers.
|
||||||
|
# The following configuration setting sets the limit in the size of the
|
||||||
|
# set in order to use this special memory saving encoding.
|
||||||
|
set-max-intset-entries 512
|
||||||
|
|
||||||
|
# Similarly to hashes and lists, sorted sets are also specially encoded in
|
||||||
|
# order to save a lot of space. This encoding is only used when the length and
|
||||||
|
# elements of a sorted set are below the following limits:
|
||||||
|
zset-max-ziplist-entries 128
|
||||||
|
zset-max-ziplist-value 64
|
||||||
|
|
||||||
|
# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
|
||||||
|
# order to help rehashing the main Redis hash table (the one mapping top-level
|
||||||
|
# keys to values). The hash table implementation Redis uses (see dict.c)
|
||||||
|
# performs a lazy rehashing: the more operation you run into an hash table
|
||||||
|
# that is rehashing, the more rehashing "steps" are performed, so if the
|
||||||
|
# server is idle the rehashing is never complete and some more memory is used
|
||||||
|
# by the hash table.
|
||||||
|
#
|
||||||
|
# The default is to use this millisecond 10 times every second in order to
|
||||||
|
# active rehashing the main dictionaries, freeing memory when possible.
|
||||||
|
#
|
||||||
|
# If unsure:
|
||||||
|
# use "activerehashing no" if you have hard latency requirements and it is
|
||||||
|
# not a good thing in your environment that Redis can reply form time to time
|
||||||
|
# to queries with 2 milliseconds delay.
|
||||||
|
#
|
||||||
|
# use "activerehashing yes" if you don't have such hard requirements but
|
||||||
|
# want to free memory asap when possible.
|
||||||
|
activerehashing yes
|
||||||
|
|
||||||
|
# The client output buffer limits can be used to force disconnection of clients
|
||||||
|
# that are not reading data from the server fast enough for some reason (a
|
||||||
|
# common reason is that a Pub/Sub client can't consume messages as fast as the
|
||||||
|
# publisher can produce them).
|
||||||
|
#
|
||||||
|
# The limit can be set differently for the three different classes of clients:
|
||||||
|
#
|
||||||
|
# normal -> normal clients
|
||||||
|
# slave -> slave clients and MONITOR clients
|
||||||
|
# pubsub -> clients subcribed to at least one pubsub channel or pattern
|
||||||
|
#
|
||||||
|
# The syntax of every client-output-buffer-limit directive is the following:
|
||||||
|
#
|
||||||
|
# client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
|
||||||
|
#
|
||||||
|
# A client is immediately disconnected once the hard limit is reached, or if
|
||||||
|
# the soft limit is reached and remains reached for the specified number of
|
||||||
|
# seconds (continuously).
|
||||||
|
# So for instance if the hard limit is 32 megabytes and the soft limit is
|
||||||
|
# 16 megabytes / 10 seconds, the client will get disconnected immediately
|
||||||
|
# if the size of the output buffers reach 32 megabytes, but will also get
|
||||||
|
# disconnected if the client reaches 16 megabytes and continuously overcomes
|
||||||
|
# the limit for 10 seconds.
|
||||||
|
#
|
||||||
|
# By default normal clients are not limited because they don't receive data
|
||||||
|
# without asking (in a push way), but just after a request, so only
|
||||||
|
# asynchronous clients may create a scenario where data is requested faster
|
||||||
|
# than it can read.
|
||||||
|
#
|
||||||
|
# Instead there is a default limit for pubsub and slave clients, since
|
||||||
|
# subscribers and slaves receive data in a push fashion.
|
||||||
|
#
|
||||||
|
# Both the hard or the soft limit can be disabled by setting them to zero.
|
||||||
|
client-output-buffer-limit normal 0 0 0
|
||||||
|
client-output-buffer-limit slave 256mb 64mb 60
|
||||||
|
client-output-buffer-limit pubsub 32mb 8mb 60
|
||||||
|
|
||||||
|
# Redis calls an internal function to perform many background tasks, like
|
||||||
|
# closing connections of clients in timeot, purging expired keys that are
|
||||||
|
# never requested, and so forth.
|
||||||
|
#
|
||||||
|
# Not all tasks are performed with the same frequency, but Redis checks for
|
||||||
|
# tasks to perform accordingly to the specified "hz" value.
|
||||||
|
#
|
||||||
|
# By default "hz" is set to 10. Raising the value will use more CPU when
|
||||||
|
# Redis is idle, but at the same time will make Redis more responsive when
|
||||||
|
# there are many keys expiring at the same time, and timeouts may be
|
||||||
|
# handled with more precision.
|
||||||
|
#
|
||||||
|
# The range is between 1 and 500, however a value over 100 is usually not
|
||||||
|
# a good idea. Most users should use the default of 10 and raise this up to
|
||||||
|
# 100 only in environments where very low latency is required.
|
||||||
|
hz 10
|
||||||
|
|
||||||
|
# When a child rewrites the AOF file, if the following option is enabled
|
||||||
|
# the file will be fsync-ed every 32 MB of data generated. This is useful
|
||||||
|
# in order to commit the file to the disk more incrementally and avoid
|
||||||
|
# big latency spikes.
|
||||||
|
aof-rewrite-incremental-fsync yes
|
||||||
|
|
||||||
|
################################## INCLUDES ###################################
|
||||||
|
|
||||||
|
# Include one or more other config files here. This is useful if you
|
||||||
|
# have a standard template that goes to all Redis server but also need
|
||||||
|
# to customize a few per-server settings. Include files can include
|
||||||
|
# other files, so use this wisely.
|
||||||
|
#
|
||||||
|
# include /path/to/local.conf
|
||||||
|
# include /path/to/other.conf
|
||||||
|
include /etc/redis/conf.d/local.conf
|
||||||
2
vagrant/reload-config.bat
Normal file
2
vagrant/reload-config.bat
Normal file
|
|
@ -0,0 +1,2 @@
|
||||||
|
cd ../
|
||||||
|
vagrant ssh -c /vagrant/vagrant/copy-and-restart-configs.sh
|
||||||
1
vagrant/reload-config.vmware.bat
Normal file
1
vagrant/reload-config.vmware.bat
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
elevator ../ vagrant ssh -c /vagrant/vagrant/copy-and-restart-configs.sh
|
||||||
Loading…
Reference in a new issue