![]() ![]() Set cache to 777 and everything started working. Turns out it was the cache directory permissions. The site wouldn't load and threw myslqi errors again. ![]() ![]() So I dumped the database and tar'd the /var/html/Uncompressed the phpbb directory and restored the database. Great! Now I have a working phpBB 3.3 setup. (Simply restarting httpd doesn't work for some reason.) The /install then worked and I was able to update phpBB from 3.2.2 to 3.3.10. Ran $ sudo yum install php-mbstring php-xml and rebooted the ec2 instance. NOTE: Bitnami stacks already include a number of PHP modules. Ran the /install but it complained that the mbstring and xml PHP extensions were missing. This means that on a Web server, the PHP engine reads, parses, compiles, and executes a. Of course, I've already (and unsuccessfully) tried with what's suggested in the docs: If you already have a Web page and you want to serve its content with Apache, copy your file to the default document root directory at /opt/bitnami/apache/htdocs/. The fix is to not using relative root, but run GitLab application as root on Apache2 HTTP server. ![]() Unzipped the htdocs directory and created a phpbb database user and restored the database into Mariadb.Äownloaded the phpBB 3.2 -> 3.3 upgrade files and pushed them to the ec2 server. Bitnami GitLab 5.0 and git & Eclipse EGit quick start. I uploaded a gzip of the phpBB 3.2 htdocs directory and the mysql dump. I ended up creating an AWS ec2 instance with a LAMP stack running PHP7.2 to use as a temporary upgrade server. Kind of a PITA but it all appears to be working properly. Placing my index.html file in the DocumentRoot defined in nf would solve the problem, but this approach is neither clean nor extensible.For anyone else in the same boat, here's how I solved it. Include "/opt/bitnami/apache/conf/bitnami/nf"Ä«oth /opt/bitnami/apache/conf/vhosts/nf and /opt/bitnami/apache/conf/bitnami/nf define a virtual host listening on port 80 (the second being thus ignored) and referring to two different DocumentRoot paths. I've also tried to restore the original LocalSettings.php file but, even in this case, I cannot access the default index.html in /opt/bitnami/apache2/htdocsÄ®dit 2: The problem is rooted in /opt/bitnami/apache/conf/nf, towards the end, it contains the following lines: IncludeOptional "/opt/bitnami/apache/conf/vhosts/*.conf" If you already have a Web page and you want to serve its content with Apache, copy your file to the default document root directory at /opt/bitnami/apache/htdocs/. For example, to check server status, use the command below and enter the password for the bitnami user when prompted: sudo /opt/bitnami/ctlscript. Of course, I've already (and unsuccessfully) tried with what's suggested in the docs: Obtain root user privileges Obtain root user privileges Execute any command as the root user by prefixing it with the sudo command. DocumentRoot /opt/bitnami/apache2/htdocs.When visiting I want an index page to be displayed, while I want to be redirected to the wiki whenever accessing URLS starting by /wiki. Set up Google Cloud Platform + MEAN stack in 5mins. Whenever accessing I get redirected to the wiki, but I don't want to. We recently purchased an SSL certificate from GoDaddy which we were trying to install on our Amazon EC2 server. Both of these hypervisors are available free of charge. Using the Bitnami Virtual Machine image requires hypervisor software such as VMware Player or VirtualBox. I'm running a virtual machine for Mediawiki packaged by Bitnami ( ) and I've set a domain name for the machine so that now the wiki responds to say . We are using an AMI provided by Bitnami that consists of our MEAN stack deployed on an Ubuntu server. Bitnami Virtual Machines contain a minimal Linux operating system with MEAN installed and configured. ![]()
0 Comments
Leave a Reply. |