Unable to install Waves on Ubuntu
I'm trying to install Waves on an Ubuntu webserver allocated in an AWS EC2.
From a fresh Ubuntu installation I installed apache2 and php8.1 with the extensions required. Then, I installed compose and modified my apache web server to point to the folder where I cloned saas. Moreover, I also added user www-data to the same group as my ubuntu user. Finally, I created my database and follow the 4 steps at https://github.com/thedevdojo/wave.
After performing these operations I didn't had any error. And if I try to enter to my IP assigned by AWS for my EC2 I can see the splash default screen (like in video 1. Installing Wave in https://devdojo.com/wave?videos=true at minute 2:17. Even the image on the right is showing correctly.
However, if I click at any link that goes to a different url, like docs, sign up or sign in, or if I put myip/admin, I get a 404 error. What's going on?
This is my config for apache in case you need it:
<VirtualHost *:80>
ServerAdmin webmaster@localhost
ServerName myweb
ServerAlias www.myweb
DocumentRoot /home/ubuntu/website/public
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
<Directory /home/ubuntu/website/>
Options +FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
Require all granted
</Directory>
</VirtualHost>
Hi there,
You need to make sure that Apache mod rewrite is enabled in order for the sub pages to work:
sudo a2enmod rewrite
And then restart Apache.
Let me know how it goes!
Best,
Bobby
Works nice! Thank you!
Can I ask you another question am I curious about? Should I do something related with files/folders permissions? I mean I just downloaded and executed the commands present in the github, but I'm not sure if I should change any file/folder permissions just for security porpoises of displaying this website publicly.
Hi there,
Do you get any permission errors in your logs?
Usually your webserver, should have access to the following directories:
storage/framework/sessions
storage/framework/views
storage/framework/cache
So you could change the group to www-data which should be the default user that the Apache service is running with, and then set the permissions of those directories to 775.
The rest of the files could be owned by your own user so you could make changes to them when deploying new changes.
Best,
Bobby