Mamp Pro Redis



The MAMP app worked pretty well. But it has one major flaw: all apps share the same PHP configuration. And the same database server and cache service (like Redis), if used by the application. Docker creates isolated container for each application in which only the application runs and has access to. If you want quick results just wait a few months for MAMP PRO to include a new version of PHP. It will save you time, money and frustration (and keep you blissfully unaware of the gruesome process of compiling software from scratch). Proceed at your own risk and peril. MAMP PRO Mac MAMP PRO Windows MAMP Mac & Windows; Number of hosts: unlimited: unlimited: 1: Webserver: Apache, Nginx. Redis: Postfix / SMTP configuration. These are just a few of the new features and improvements in It. Other new features include support for MySQL 5.7, integration of Redis caching server, remote editing of the editor, redesigned toolbar, optimized host creation dialog and more. Note: MAMP PRO is 14 days trial version. MAMP can be used at no cost. Also Available: Download MAMP for Mac. In case this cookie is set, Apache routes the request to the 'debug' instance instead via some clever modproxyfcgi directives. With external object caching, like Redis, this actually works out all right. Interpreter instance specific things like APCu, probably not so well.

Jan 17th, 2012
Never
Not a member of Pastebin yet?Sign Up, it unlocks many cool features!
  1. # Note on units: when memory size is needed, it is possible to specifiy
  2. #
  3. # 1kb => 1024 bytes
  4. # 1mb => 1024*1024 bytes
  5. # 1gb => 1024*1024*1024 bytes
  6. # units are case insensitive so 1GB 1Gb 1gB are all the same.
  7. # By default Redis does not run as a daemon. Use 'yes' if you need it.
  8. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
  9. # When running daemonized, Redis writes a pid file in /var/run/redis.pid by
  10. # default. You can specify a custom pid file location here.
  11. # Accept connections on the specified port, default is 6379.
  12. # If port 0 is specified Redis will not listen on a TCP socket.
  13. # If you want you can bind a single interface, if the bind option is not
  14. # specified all the interfaces will listen for incoming connections.
  15. # bind 127.0.0.1
  16. # Specify the path for the unix socket that will be used to listen for
  17. # incoming connections. There is no default, so Redis will not listen
  18. #
  19. # Close the connection after a client is idle for N seconds (0 to disable)
  20. # it can be one of:
  21. # debug (a lot of information, useful for development/testing)
  22. # verbose (many rarely useful info, but not a mess like the debug level)
  23. # notice (moderately verbose, what you want in production probably)
  24. # warning (only very important / critical messages are logged)
  25. # Specify the log file name. Also 'stdout' can be used to force
  26. # Redis to log on the standard output. Note that if you use standard
  27. # output for logging but daemonize, logs will be sent to /dev/null
  28. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  29. # and optionally update the other syslog parameters to suit your needs.
  30. syslog-ident redis
  31. # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
  32. # Set the number of databases. The default database is DB 0, you can select
  33. # a different one on a per-connection basis using SELECT <dbid> where
  34. databases 16
  35. ################################ SNAPSHOTTING #################################
  36. # Save the DB on disk:
  37. # save <seconds> <changes>
  38. # Will save the DB if both the given number of seconds and the given
  39. # number of write operations against the DB occurred.
  40. # In the example below the behaviour will be to save:
  41. # after 900 sec (15 min) if at least 1 key changed
  42. # after 300 sec (5 min) if at least 10 keys changed
  43. #
  44. # Note: you can disable saving at all commenting all the 'save' lines.
  45. save 9001
  46. save 6010000
  47. # Compress string objects using LZF when dump .rdb databases?
  48. # For default that's set to 'yes' as it's almost always a win.
  49. # If you want to save some CPU in the saving child set it to 'no' but
  50. # the dataset will likely be bigger if you have compressible values or keys.
  51. dbfilename dump.rdb
  52. # The working directory.
  53. # The DB will be written inside this directory, with the filename specified
  54. # above using the 'dbfilename' configuration directive.
  55. # Also the Append Only File will be created inside this directory.
  56. # Note that you must specify a directory here, not a file name.
  57. ################################# REPLICATION #################################
  58. # Master-Slave replication. Use slaveof to make a Redis instance a copy of
  59. # another Redis server. Note that the configuration is local to the slave
  60. # so for example it is possible to configure the slave to save the DB with a
  61. # different interval, or to listen to another port, and so on.
  62. # slaveof <masterip> <masterport>
  63. # If the master is password protected (using the 'requirepass' configuration
  64. # directive below) it is possible to tell the slave to authenticate before
  65. # starting the replication synchronization process, otherwise the master will
  66. #
  67. # When a slave lost the connection with the master, or when the replication
  68. # is still in progress, the slave can act in two different ways:
  69. # 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
  70. # still reply to client requests, possibly with out of data data, or the
  71. # data set may just be empty if this is the first synchronization.
  72. # 2) if slave-serve-stale data is set to 'no' the slave will reply with
  73. # an error 'SYNC with master in progress' to all the kind of commands
  74. #
  75. ################################## SECURITY ###################################
  76. # Require clients to issue AUTH <PASSWORD> before processing any other
  77. # commands. This might be useful in environments in which you do not trust
  78. # others with access to the host running redis-server.
  79. # This should stay commented out for backward compatibility and because most
  80. # people do not need auth (e.g. they run their own servers).
  81. # Warning: since Redis is pretty fast an outside user can try up to
  82. # 150k passwords per second against a good box. This means that you should
  83. # use a very strong password otherwise it will be very easy to break.
  84. # requirepass foobared
  85. # Command renaming.
  86. # It is possilbe to change the name of dangerous commands in a shared
  87. # environment. For instance the CONFIG command may be renamed into something
  88. # of hard to guess so that it will be still available for internal-use
  89. #
  90. #
  91. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  92. # It is also possilbe to completely kill a command renaming it into
  93. #
  94. ################################### LIMITS ####################################
  95. # Set the max number of connected clients at the same time. By default there
  96. # is no limit, and it's up to the number of file descriptors the Redis process
  97. # is able to open. The special value '0' means no limits.
  98. # Once the limit is reached Redis will close all the new connections sending
  99. #
  100. # Don't use more memory than the specified amount of bytes.
  101. # When the memory limit is reached Redis will try to remove keys with an
  102. # EXPIRE set. It will try to start freeing keys that are going to expire
  103. # in little time and preserve keys with a longer time to live.
  104. # Redis will also try to remove objects from free lists if possible.
  105. # If all this fails, Redis will start to reply with errors to commands
  106. # that will use more memory, like SET, LPUSH, and so on, and will continue
  107. #
  108. # WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
  109. # 'state' server or cache, not as a real DB. When Redis is used as a real
  110. # database the memory usage will grow over the weeks, it will be obvious if
  111. # it is going to use too much memory in the long run, and you'll have the time
  112. # to upgrade. With maxmemory after the limit is reached you'll start to get
  113. # errors for write operations, and this may even lead to DB inconsistency.
  114. # maxmemory <bytes>
  115. # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  116. #
  117. # volatile-lru -> remove the key with an expire set using an LRU algorithm
  118. # allkeys-lru -> remove any key accordingly to the LRU algorithm
  119. # volatile-random -> remove a random key with an expire set
  120. # volatile-ttl -> remove the key with the nearest expire time (minor TTL)
  121. # noeviction -> don't expire at all, just return an error on write operations
  122. # Note: with all the kind of policies, Redis will return an error on write
  123. # operations, when there are not suitable keys for eviction.
  124. # At the date of writing this commands are: set setnx setex append
  125. # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  126. # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  127. # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  128. #
  129. #
  130. # LRU and minimal TTL algorithms are not precise algorithms but approximated
  131. # algorithms (in order to save memory), so you can select as well the sample
  132. # size to check. For instance for default Redis will check three keys and
  133. # pick the one that was used less recently, you can change the sample size
  134. #
  135. ############################## APPEND ONLY MODE ###############################
  136. # By default Redis asynchronously dumps the dataset on disk. If you can live
  137. # with the idea that the latest records will be lost if something like a crash
  138. # happens this is the preferred way to run Redis. If instead you care a lot
  139. # about your data and don't want to that a single record can get lost you should
  140. # enable the append only mode: when this mode is enabled Redis will append
  141. # every write operation received in the file appendonly.aof. This file will
  142. # be read on startup in order to rebuild the full dataset in memory.
  143. # Note that you can have both the async dumps and the append only file if you
  144. # like (you have to comment the 'save' statements above to disable the dumps).
  145. # Still if append only mode is enabled Redis will load the data from the
  146. #
  147. # IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
  148. # The name of the append only file (default: 'appendonly.aof')
  149. # The fsync() call tells the Operating System to actually write data on disk
  150. # instead to wait for more data in the output buffer. Some OS will really flush
  151. # data on disk, some other OS will just try to do it ASAP.
  152. # Redis supports three different modes:
  153. # no: don't fsync, just let the OS flush the data when it wants. Faster.
  154. # always: fsync after every write to the append only log . Slow, Safest.
  155. # everysec: fsync only if one second passed since the last fsync. Compromise.
  156. # The default is 'everysec' that's usually the right compromise between
  157. # speed and data safety. It's up to you to understand if you can relax this to
  158. # 'no' that will will let the operating system flush the output buffer when
  159. # it wants, for better performances (but if you can live with the idea of
  160. # some data loss consider the default persistence mode that's snapshotting),
  161. # or on the contrary, use 'always' that's very slow but a bit safer than
  162. #
  163. appendfsync everysec
  164. # When the AOF fsync policy is set to always or everysec, and a background
  165. # saving process (a background save or AOF log background rewriting) is
  166. # performing a lot of I/O against the disk, in some Linux configurations
  167. # Redis may block too long on the fsync() call. Note that there is no fix for
  168. # this currently, as even performing fsync in a different thread will block
  169. #
  170. # In order to mitigate this problem it's possible to use the following option
  171. # that will prevent fsync() from being called in the main process while a
  172. #
  173. # This means that while another child is saving the durability of Redis is
  174. # the same as 'appendfsync none', that in pratical terms means that it is
  175. # possible to lost up to 30 seconds of log in the worst scenario (with the
  176. #
  177. # If you have latency problems turn this to 'yes'. Otherwise leave it as
  178. # 'no' that is the safest pick from the point of view of durability.
  179. ################################ VIRTUAL MEMORY ###############################
  180. # Virtual Memory allows Redis to work with datasets bigger than the actual
  181. # amount of RAM needed to hold the whole dataset in memory.
  182. # In order to do so very used keys are taken in memory while the other keys
  183. # are swapped into a swap file, similarly to what operating systems do
  184. #
  185. # To enable VM just set 'vm-enabled' to yes, and set the following three
  186. # vm-enabled yes
  187. # This is the path of the Redis swap file. As you can guess, swap files
  188. # can't be shared by different Redis instances, so make sure to use a swap
  189. # file for every redis process you are running. Redis will complain if the
  190. #
  191. # The best kind of storage for the Redis swap file (that's accessed at random)
  192. #
  193. # *** WARNING *** if you are using a shared hosting the default of putting
  194. # the swap file under /tmp is not secure. Create a dir with access granted
  195. # only to Redis user and configure Redis to create the swap file there.
  196. # vm-max-memory configures the VM to use at max the specified amount of
  197. # RAM. Everything that deos not fit will be swapped on disk *if* possible, that
  198. # is, if there is still enough contiguous space in the swap file.
  199. # With vm-max-memory 0 the system will swap everything it can. Not a good
  200. # default, just specify the max amount of RAM you can in bytes, but it's
  201. # better to leave some margin. For instance specify an amount of RAM
  202. # that's more or less between 60 and 80% of your free RAM.
  203. # Redis swap files is split into pages. An object can be saved using multiple
  204. # contiguous pages, but pages can't be shared between different objects.
  205. # So if your page is too big, small objects swapped out on disk will waste
  206. # a lot of space. If you page is too small, there is less space in the swap
  207. # file (assuming you configured the same number of total swap file pages).
  208. # If you use a lot of small objects, use a page size of 64 or 32 bytes.
  209. # If you use a lot of big objects, use a bigger page size.
  210. vm-page-size 32
  211. # Number of total memory pages in the swap file.
  212. # Given that the page table (a bitmap of free/used pages) is taken in memory,
  213. # every 8 pages on disk will consume 1 byte of RAM.
  214. # The total swap size is vm-page-size * vm-pages
  215. # With the default of 32-bytes memory pages and 134217728 pages Redis will
  216. # use a 4 GB swap file, that will use 16 MB of RAM for the page table.
  217. # It's better to use the smallest acceptable value for your application,
  218. # but the default is large in order to work in most conditions.
  219. # Max number of VM I/O threads running at the same time.
  220. # This threads are used to read/write data from/to swap file, since they
  221. # also encode and decode objects from disk to memory or the reverse, a bigger
  222. # number of threads can help with big objects even if they can't help with
  223. # I/O itself as the physical device may not be able to couple with many
  224. #
  225. # The special value of 0 turn off threaded I/O and enables the blocking
  226. vm-max-threads 4
  227. ############################### ADVANCED CONFIG ###############################
  228. # Hashes are encoded in a special way (much more memory efficient) when they
  229. # have at max a given numer of elements, and the biggest element does not
  230. # exceed a given threshold. You can configure this limits with the following
  231. hash-max-zipmap-entries 512
  232. # Similarly to hashes, small lists are also encoded in a special way in order
  233. # to save a lot of space. The special representation is only used when
  234. list-max-ziplist-entries 512
  235. # Sets have a special encoding in just one case: when a set is composed
  236. # of just strings that happens to be integers in radix 10 in the range
  237. # The following configuration setting sets the limit in the size of the
  238. # set in order to use this special memory saving encoding.
  239. # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
  240. # order to help rehashing the main Redis hash table (the one mapping top-level
  241. # keys to values). The hash table implementation redis uses (see dict.c)
  242. # performs a lazy rehashing: the more operation you run into an hash table
  243. # that is rhashing, the more rehashing 'steps' are performed, so if the
  244. # server is idle the rehashing is never complete and some more memory is used
  245. #
  246. # The default is to use this millisecond 10 times every second in order to
  247. # active rehashing the main dictionaries, freeing memory when possible.
  248. # If unsure:
  249. # use 'activerehashing no' if you have hard latency requirements and it is
  250. # not a good thing in your environment that Redis can reply form time to time
  251. #
  252. # use 'activerehashing yes' if you don't have such hard requirements but
  253. activerehashing yes
  254. ################################## INCLUDES ###################################
  255. # Include one or more other config files here. This is useful if you
  256. # have a standard template that goes to all redis server but also need
  257. # to customize a few per-server settings. Include files can include
  258. #
  259. # include /path/to/other.conf
RAW Paste Data

Just recently I wanted to install Redis and the fast, because written in C, PHP extension PHPRedis on my Macbook Pro.

I learned, that I would need to recompile my PHP and decided to switch from the convenient, but not really extendable MAMP.app, to the more Linux-alike (apt get …) Macports. At the end of this article I will post some further links relating Getting-Started with Macports. I assume that you correctly installed Apache 2 and PHP 5.3.5 with Macports.

Installation of Redis Server
Head to your terminal and type the following:

sudo port selfupdate
sudo port upgrade outdated
sudo port install redis

Mamp

You now installed the Redis Server! To run Redis type

sudo port install redis

… and to stop it type

sudo killall redis-server

Mamp Pro Php Redis

Installation of the PHP Extension
At first, we create a new directory where we put all the source code inside, then we get the latest code via GIT and then we build it for PHP. To make it easy, just copy & paste the following lines to your terminal:

Mamp Pro Redis

cd /usr/local
sudo mkdir src
cd /usr/local/src
sudo mkdir phpredis-build
cd phpredis-build
sudo git clone --depth 1 git://github.com/owlient/phpredis.git
cd phpredis
sudo phpize
sudo ./configure
sudo make
sudo make install

Mamp pro redis extension

Now just create the necessary ini-file for the extension:

cd /opt/local/var/db/php5/
sudo nano redis.ini
add the line: extension = redis.so into the file and save it

Now just restart your Apache and you´re ready to go!

Mamp Pro Discount

Links for the installation of Macports:

https://trac.macports.org/wiki/howto/MAMP
http://blogwaffe.com/2010/01/22/php-5-apache-2-mysql-5-on-os-x-via-macports/