I was trying to setup redis cache for moodle server. My moodle serve is very slow. So I installed redis server to change the cache from file cache to redis. But when I open moodle server and try to configure redis cache, I am not getting the option of add instance for redis. Can someone guide me how to configure redis server to enable redis cache for moodle server ??
There is official docs at https://docs.moodle.org/39/en/Redis_cache_store that explains the rquired steps.
Make sure that you have installed Redis php driver and the green tick mark is visible as the doc states When installed, you should see a tick next to "Redis" under "Installed cache stores" and a link to add an instance.
Related
I have created a project with MERN stack and want to host it. But as i came to know that netlify.app hosting site doesnt support hosting for database related projects as my project includes mongodb as a backend.
It will be a great help if anyone can suggest where should i host my project which can support mongodb as a backend also. And also any methods to do it that will be great help.
You can use AWS EC2 Linux instance, where you can keep your project and at the same time you can store your data. For the initial phase of your project, you can install MongoDB on the same machine.
I created a typo3 Command for the scheduler and when I execute it manually it works fine. But when its executed automatically (via cronjob), there is the following error:
The APC backend cannot be used because apc is disabled on CLI
I googled this but the results are not helpful, does anyone know what exactly this means?
TYPO3 CMS uses the APC Cache backend for the extbase object and reflection caches.
If you do not want to use the APC cache backend, then you can do so in the Install Tool in the menu point Configuration Presets. There is one where you can choose between Database cache backend and APC cache backend. The APC cache is chosen automatically during installation if it is available.
You can also change your server configuration and make the APC cache backend available from CLI. http://php.net/manual/en/apc.configuration.php#ini.apc.enable-cli
Please note that the CLI cache is no persisted across requests, therefore there is no gain from doing this.
You can read more about the Caching Framework in the TYPO3 CMS Documentation: https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/CachingFramework/Index.html
I am trying to change site url from http://localhost/yiiwebsite/backend/web/index.php url to http://localhost/yiiwebsite/admin and http://localhost/yiiwebsite/frontend/web/index.php url to http://localhost/yiiwebsite/.
Can anyone help me to do this.
It's described in official docs here.
Here is some basic info:
The application installed according to the above instructions should
work out of box with either an Apache HTTP server or an Nginx HTTP
server, on Windows, Mac OS X, or Linux running PHP 5.4 or higher. Yii
2.0 is also compatible with facebook's HHVM. However, there are some edge cases where HHVM behaves different than native PHP, so you have
to take some extra care when using HHVM.
On a production server, you may want to configure your Web server so
that the application can be accessed via the URL
http://www.example.com/index.php instead of
http://www.example.com/basic/web/index.php. Such configuration
requires pointing the document root of your Web server to the
basic/web folder. You may also want to hide index.php from the URL, as
described in the Routing and URL Creation section. In this subsection,
you'll learn how to configure your Apache or Nginx server to achieve
these goals.
By setting basic/web as the document root, you also prevent end users
from accessing your private application code and sensitive data files
that are stored in the sibling directories of basic/web. Denying
access to those other folders is a security improvement.
If your application will run in a shared hosting environment where you
do not have permission to modify its Web server configuration, you may
still adjust the structure of your application for better security.
Further configuration depends on chosen web server (Nginx / Apache), which is not even mentioned in the questoin. But both options are covered in official docs by the given link.
For shared hosting environment there is special section too.
And by the way this was asked before many times here on SO, just do a better research.
We have the New Relic PHP agent running on our 8 app servers. we have two memcached servers and would like to add the New Relic/ Meet Me Memcached plugin to grab memcached metrics. Should the memcached plugin be installed on the app servers or memcached servers? I read up on the installation instructions however this is not entirely clear.
When I haven't used memcached plugin yet, I do use MySQL, MongoDB and RabbitMQ plugings.
All of the can be installed or locally (on the same server where application located) or remotely.
I choosed the second way - so I installed all these plugins on my management server and plugins collect metrics from all my mysql,mongo and rabbit servers. [other way you should install plugins and JRE on many servers].
Hi I was looking for a place to host my bigger projects with a philosophy "pay for what you use". I found Amazon WS. I want to set up a site with CMS (Modx) on Amazon WS. I basically need to setup a database (mysql?) and a webserver. Can someone provide me with some info on that or point to a tutorial or something?
Well, AWS gives you EC2 (CPU) and EBS (Hard Disk). You will need to choose an OS, setup Apache/Nginx and mysql.
In their basic form, the installation procedure is fairly simple.
sudo apt-get install apache2
sudo apt-get install mysql
Look around the web for more complete tutorials for the OS you choose. These are for ubuntu.
As for Modx, their instructions are available.
Good luck.
Also, you can also use a PaaS solution to assist you with the setup. Such as:
https://bitnami.com/stack/modx/cloud/amazon
This will enable you to build a CMS on any Cloud provider: AWS, Azure, etc. and add a layer of support and management on top of it.
I have came across a tutorial available here: http://blog.jelastic.com/2013/06/25/deploy-modx-cms/
The tutorial seems to be more than comprehensive.
Seems you just need to pick up the needed instances, upload the application and configure the database.