I need to configure Magento 2.4.5 on RHEL. I need recommendation/best practices for below:
Should I go with RHEL 8.6 or 9.0? Don't want to go with Ubuntu or CentOS.
Should I host the database on a separate server, rather than running the database server and the
web server on the same machine?
What should be the minimum VM configuration in terms of RAM, processor, disk and cache for
Magento and mySQL. Considering the load on website can be around 3K users during peak time.
Regards,
Rajesh
Related
I bought "Hetzer" server so I can create my own database and practice a little bit. My server is using Ubuntu. I plan to also create a script (probably in node or asp) so my android application can communicate with database.
How to start with creating database, what to do?
Firstly https://www.hetzner.com/ is one of the best professional web hosting providers. In order to set up your Mysql server to your ubuntu machine. Install lamp stack. There are many tutorials about installing lamp. Then open your DB for remote connection or do kind of restful service to access your data in DB.
I heard that MySQL is a database server. If it is a database server, then what is the need of installing other servers like xampp or lampp? Do xampp or wamp or lampp do other jobs than being a Database server?
XAMPP, WAMP and LAMPP are all stacks for creating web solutions. The acronyms come from A Apache (web server), M MySQL or MariaDb (Database), and P for Perl or PHP for the scripting component.
MySQL itself is just a database server (RDBMS) so you would require additional components to build an overall web solution (provided in the stacks above).
Depending on your operating system, W(Windows), L(Linux) , X(All) then we have Apache, Mysql running at different ports.
PHP including the rest of your code files stored in htdocs as they have corresponding engines in relative XAMP directories (eg php.ini). All these will give you a look and feel of a typical server environment and accommodate your frameworks (laravel, noodle etc) you can't get all that from mysql server alone.
I have a Mercurial server on a simple server (Virtual Machine (VM)), and about 100 users with access. And from time to time, requests have been slow.
And since I can not change the hardware of this server, because the VM server no longer has available resources, and migrating it would do a great job.
I would like to know it is possible to have 2 mercurial servers, using the same database, because this would balance the load, and in one server would put a large team, and in the other the other teams. In short, I can not mess with the server you're on today.
VM:
Windows Server 2003 SP2
1.5GB Memory
60GB HD
Settings:
Python 2.7.2
Mercurial 2.5.4
RhodeCode 1.6.0rc1
Note:
Sorry if you're confused, this question was translated via google. If you can edit and rearrange it, I'll be very grateful.
This is certainly possible. If you have shares storage RhodeCode can use the same DB and load-balance load between machines.
Btw, 1.6.0 is very old I'd take a chance at upgrading this.
is it ideal to have MySQL running on different machine than on the server machine that runs Apache or php . I was think of a scenario if two different web server installed physically on different machine accessing database than it can be useful that if one web server goes down other server would still be running if MySQL is deployed on a separate machine ?
of course.
Same resources shared between apache/php and MySQL are not a good option.
Divide and conquer my brother!
I have a running sql server installation on which I would like to install the reporting services module. Now because it is very important that the sql server it self keeps available and running without any interruptions I get a little scary about this step.
Now my question. Are there any pittfalls I have to be aware of before I install the module? E.g. does the server restart during the installation?
Can you try this change in a virtual machine first?
For example, use the Disk2vhd application (http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx) to make a snapshot of your current production system. Then, use the VHD that was created in Microsoft Virtual PC, Hyper-V, or Windows 7 native VHD boot.
If you try a virtual machine for testing, disable networking or create a private network before starting the virtual machine! Having two servers with the same name and SID on your network is a Bad Thing.
(If you're not using virtual machines, isn't it time? :)