First of all, thanks to Flarum for providing such a simple and innovative forum.
We have been using it for 3 months and it is running perfectly.
Install the test environment in aaPanel
aaPanel
Nginx 1.17
Mariadb 10.0
PHP 71
Create a website and enter your domain name
Choose to create a database
![](https://forum.aapanel.com/assets/files/2019-10-12/1570875295-995659-add-site.jpeg)
Install composer
If you have multiple php,Check if your php cli is 71
php -v
If not, please go to the panel switch
![](https://forum.aapanel.com/assets/files/2019-10-12/1570874884-869818-phpcli.jpeg)
Start installing composer
Go to your site root directory
cd /www/wwwroot/test/
curl -sS https://getcomposer.org/installer | php
Check if composer works
php composer.phar
Set up the php environment
Remove these php functions that are disabled by default by the panel
putenv
pcntl_signal
proc_open
![](https://forum.aapanel.com/assets/files/2019-10-12/1570874977-667415-phpfunctions.jpeg)
Install the file_info extension
![](https://forum.aapanel.com/assets/files/2019-10-12/1570874963-579531-fileinfo.jpeg)
Install FLARUM
composer create-project flarum/flarum . --stability=beta
If the process is killed during the installation process
![](https://forum.aapanel.com/assets/files/2019-10-12/1570875131-962809-killed.jpeg)
Please add Swap in Linux Tools
![](https://forum.aapanel.com/assets/files/2019-10-12/1570875173-646872-sawp.jpeg)
If you see this prompt after the installation is complete, don't panic,
This is just a warning message for developers and means that Laravel / Flarum should take the time to update the Carbon dependency. It shouldn't cause any problems for you.
https://discuss.flarum.org/d/20607-upgrade-carbon-beta-9
Carbon 1 is deprecated, see how to migrate to Carbon 2.
https://carbon.nesbot.com/docs/#api-carbon-2
You can run './vendor/bin/upgrade-carbon' to get help in updating carbon and other frameworks and libraries that depend on it.
Now you can access your FLARUM domain name.
If permissions denied,
![](https://forum.aapanel.com/assets/files/2019-10-12/1570875552-913313-permission.jpeg)
Go to the site settings settings directory owner for www
Change your running directory to public
![](https://forum.aapanel.com/assets/files/2019-11-26/1574738824-418184-rundir.png)
We also need to add this code to url-rewrite
![](https://forum.aapanel.com/assets/files/2019-10-21/1571624650-365795-tmp.jpeg)
# Pass requests that don't refer directly to files in the filesystem to index.php
location / {
try_files $uri $uri/ /index.php?$query_string;
}
# The following directives are based on best practices from H5BP Nginx Server Configs
# https://github.com/h5bp/server-configs-nginx
# Expire rules for static content
location ~* \.(?:manifest|appcache|html?|xml|json)$ {
add_header Cache-Control "max-age=0";
}
location ~* \.(?:rss|atom)$ {
add_header Cache-Control "max-age=3600";
}
location ~* \.(?:jpg|jpeg|gif|png|ico|cur|gz|svg|mp4|ogg|ogv|webm|htc)$ {
add_header Cache-Control "max-age=2592000";
access_log off;
}
location ~* \.(?:css|js)$ {
add_header Cache-Control "max-age=31536000";
access_log off;
}
location ~* \.(?:ttf|ttc|otf|eot|woff|woff2)$ {
add_header Cache-Control "max-age=2592000";
access_log off;
}
# Gzip compression
gzip on;
gzip_comp_level 5;
gzip_min_length 256;
gzip_proxied any;
gzip_vary on;
gzip_types
application/atom+xml
application/javascript
application/json
application/ld+json
application/manifest+json
application/rss+xml
application/vnd.geo+json
application/vnd.ms-fontobject
application/x-font-ttf
application/x-web-app-manifest+json
application/xhtml+xml
application/xml
font/opentype
image/bmp
image/svg+xml
image/x-icon
text/cache-manifest
text/css
text/plain
text/vcard
text/vnd.rim.location.xloc
text/vtt
text/x-component
text/x-cross-domain-policy;
You can now go to the FLARUM installation page.
Finally turn on firewall protection to our forum
![](https://forum.aapanel.com/assets/files/2019-11-26/1574739197-606313-ngfw.png)
I am very sorry if there is any violation, please close it.
Thanks for reading