I have an htaccess file with a simple rewrite rule.
RewriteEngine On
RewriteRule ^([a-zA-Z0-9]+)/?$ index.php?page=$1
On my web server, the index.php file is in /var/www, and it works normally.
On my local host, the index.php fle is in /var/www/projects/porto and while the file runs normally, no linked content ( images, css, etc ) is loaded.
I am totally new to htaccess files. Any ideas on how to work around it so I can do my testing in my locan environment?
All I've tried is changing my .htaccess file to
RewriteEngine On
RewriteRule ^([a-zA-Z0-9]+)/?$ /running/Porto/index.php?page=$1
But no luck.
Okay, so continuing our discussion on setting up a VirtualHost on your local machine/environment, it is roughly the same as on your other server. If you can copy the Apache configuration file from the web server then that will be a good start. At a minimum you will need something like this:
<VirtualHost *:80>
ServerName localdevsite.com
DocumentRoot /var/www/running/Proto
</VirtualHost>
(This assumes that somewhere in the file you have NameVirtualHost *:80)
The one additional thing you will need to do in your local environment is add a hosts entry:
In Linux you usually do this in /etc/hosts with something like:
127.0.0.1 localdevsite.com
Related
So today I realised my VPS still had 3 domains pointing to the origin IP - I have never worked with Apache conf files and have just attempted to add my own .htaccess from my own research:
Options FollowSymLinks
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^www.infamystudio.com$
RewriteRule ^/?(.*) https://www.infamystudio.com/$1 [QSA,R=301,L]
This was placed into the var/www folder and has had no effect on rewriting other domains pointing to the origin back to my IP.
Is there any good tutorials or can anyone help me write a rewrite so I can stop this.
Your .htaccess file should be in the root folder of your website, but it will only be used by Apache if the Virtualhost configuration allow a override. So because I don't know what kind of VPS you have you have to find it yourself.
In Debian like servers this is usual in /etc/apache2/site-enable/<virtual-host>.conf (all files in site-enable are only links to the the files in the folder site-available)
Allowing rewrite for your VirtualHost
<Directory "/var/www/path/to/public">
AllowOverride All
</Directory>
If this step is missing, nothing in your .htaccess file will work. If you have already a Directory-Direktive just only add AllowOverride All You may want to restrict this later but just for testing ALL would be good.
You also can have multiple Virtual host configurations for different IP or domain names.
https://httpd.apache.org/docs/current/vhosts/examples.html
I am building an application in Laravel which will be in construction for some time. In the meantime, I have 2 "conventional" websites, one static html and one php, which I'd like to include in my source control and make publicly accessible as I build the laravel application.
I have my public folder set up like this :
public/website1/many folders and files
public/website2/many folders and files
public/index.php
I would like to route / redirect users in the following way (lets use my development environment "localhost" as the domain):
localhost/laravelapp/ -> index.php
localhost/website1/ -> website1/index.html
localhost/website2/ -> website2/index.php
This way I can maintain all my code within a single project / source control / server.
But how do I route this!?
I have tried:
Route::get('/website1', function() {
return File::get(public_path() . '/website1/index.html');
});
but this just returns a static file with no relative links to the css folder or other linked files. How can I redirect the user properly to the correct area? Rebuilding the existing sites in Laravel framework is not an option. Thanks.
This should be pretty simple. I assume that you are using apache?
If you put a separate .htaccess file inside public/website1 and public/website2 then those rules will apply instead when you are visiting those routes, ignoring the rewrite rules in public/.htaccess.
You can configure your new .htaccess-files however you want, but all you need is
<IfModule mod_rewrite.c>
RewriteEngine On
</IfModule>
This is rerouted on the webserver level. Nothing is passed through laravel. This is what you want.
Now, we have solved this part:
localhost/website1/ -> website1/index.html
localhost/website2/ -> website2/index.php
But the laravel app acts like this:
localhost/ -> index.php
instad of:
localhost/laravelapp/ -> index.php
To solve this part, create a new directory inside public called laravelapp
and move public/.htaccess to public\laravelapp\.htaccess and change the following line
RewriteRule ^ index.php [L]
to
RewriteRule ^ ../index.php [L]
This was solved by by doing a couple of things:
1) VirtualHosts on the webserver to handle the domain name routing. Create a file on the Apache server:
httpd/conf.d/vhost.conf
NameVirtualHost *:80
<VirtualHost *>
ServerName domain1.com
ServerAlias dev.domain1.com
DocumentRoot /var/www/html/public
</VirtualHost>
<VirtualHost *>
ServerName domain2.com
ServerAlias dev.domain2.com
DocumentRoot /var/www/html/public/website2
</VirtualHost>
This routed my domains to their subfolders
2) The localhost environment was not working well. I switched from using "php -S server.php" (Laravels own server script configuration) to MAMP for OSX. This instantly cleared up my remaining permissions issues.
I hope this answer can help someone else in the future.
I've been building on localhost and all this stuff works perfectly. Now trying to load the site on a shared host. I've worked through most of the issues and actually have a working site but without any css.
Layout:
My app is in: /home/cake/app
public_html is in: /home/public_html
In public_html/index.php, the only way I was able to get rid of missing file errors was to do this...
require '../cake/app/webroot' . DIRECTORY_SEPARATOR . 'index.php';
The .htaccess in public_html:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ index.php [QSA,L]
</IfModule>
My app was baked from the command line.
All of the index.php and .htaccess files up through the chain are untouched.
/cake
/cake/webroot
/cake/app
/cake/app/webroot
It just can't find the path to all the css and js files.
in my default.ctp, I used the standard html helper links.
echo $this->Html->css('default');
I'm at the end of the proverbial rope. Any help appreciated.
On localhost, I point the apache directory at /cake/app, but I'm pretty sure I don't have access to apache config files on a shared host, hence the reason I pointed the public_html index.php at /cake/app. Probably not right, but it felt like I was moving in the right direction since the site started working.
All your CSS & JS should be inside the app/webroot directory.
It sounds like you've setup your virtual hosts incorrectly. (This is why the CSS works in public_html but not in the webroot directory).
Basically, We only allow access to our application through app/webroot/. This will load the index.php inside the webroot which is provided by cakePHP to load the controllers for every request.
Your virtual host file should look like this:
<VirtualHost *:80>
# Correct: Notice the "/app/webroot/"
DocumentRoot "/path/to/app/public_html/app/webroot/"
# Below is INCORRECT
# Incorrect: DocumentRoot "/path/to/app/public_html/app/"
ServerName yourdomain.com
</VirtualHost>
Now.. the ONLY directory accessible from the outside world is everything in webroot, this can be JS, CSS, Images, Files or whatever other assets you require.
This is how it should be setup, you dont want people to be able to access files outside of your webroot (ie all other CakePHP files).
On shared hosting providers, you will require a slightly different setup (you wont have access to the vhosts of the shared server). This explains the slightly different directory structure the OP has said. Read here for more info on deploying cakephp on a shared host.
http://bakery.cakephp.org/articles/gedm/2009/08/29/installing-cakephp-on-shared-hosting
Instead of including the index.php from the webroot in another index.php (inside your public_html), consider changing the webroot folder entirley to your public_html.
View here for more info on change cakephp webroot folder: CAKEPHP - Change default path to webroot
Change AllowOverride none to AllowOverride FileInfo in /etc/apache2/sites-available/default.
<VirtualHost *:80>
ServerAdmin webmaster#localhost
DocumentRoot /home/user/app/
<Directory />
Options FollowSymLinks
AllowOverride FileInfo
</Directory>
<Directory /home/user/app/>
Options Indexes FollowSymLinks MultiViews
AllowOverride FileInfo
Order allow,deny
allow from all
</Directory>
It worked for me.
Finally this one was the command wich worked for me to enable mod_rewrite:
$ a2enmod rewrite
Well, not sure whether this is all "right" or not, but I copied all the folders with the css and js files into public_html, which kind of makes sense. All of those assets need to be publicly accessible. Site works now.
I was confused when I want to upload all applications using the framework laravel. In the hosting I want to access directly :
www.mydomain.com
(without /public)
Please help me
As per the installation instructions you must point the Virtual Host to the public folder, for example:
<VirtualHost *:80>
DocumentRoot /Users/JonSnow/Sites/MySite/public
ServerName mysite.dev
</VirtualHost>
If you're not using Virtual Hosts and are simply specifying the DocumentRoot you would do something like:
DocumentRoot "/var/www/public"
An alternative option on shared hosting is to place everything outside of the 'public_html' folder, and then place the contents of 'public' into 'public_html'.
You will then just need to update $paths['public'] = 'public'; to $paths['public'] = 'public_html'; inside the paths.php file in the root.
Are you using shared hosting? Some hosts only give you access to the web root (never ideal).
If so a hacky workaround would be to use a .htaccess file to redirect web-root to web-root/public but this is not a good place to put a framework.
Untested but something like this should work:
# Send user to /public/
Options +FollowSymlinks
RewriteEngine on
RewriteRule ^(.*)$ /public/$1 [NC]
As the title states, I cannot get my site to redirect. I've made several attempts and am about to lose it.
My .htaccess file is as follows:
Options +FollowSymLinks
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]
I have this file placed in the www/Laravel/public folder as well as www directory
mod_rewrite is enabled
AllowOverride is set to All
My host file is as follows
127.0.0.1 localhost
Here is the code for route contained in routes.php
Route::get('authors', array('uses'=>'authors#index'));
I have a controller named authors.php, here is the code
class Authors_Controller extends Base_Controller {
public $restful = true;
public function get_index () {
return View::make('authors.index');}
}
I am using Windows 7 Ultimate. I'm about to blow my brains out. Please help me, I suck.
If your laravel project is located in c:\wamp\laravel\ then you should be able to call
http://localhost/laravel/public
and see the default laravel welcome page or your own.
If thats the case, you have to check two thins:
Open your /app/config/app.php file and check that the value of url directs to your project.
'url'=>'http://localhost/laravel/
Then open your .htaccess file and add the RewriteBase rule under the RewriteEngine On Line
RewriteBase /laravel/public/
Hope that helps! :)
I had the same problem. I used the solution above and it worked.
Apache rewrite_module must be enable in wamp as well.
You need to setup a virtual host pointing to your public directory...
in httpd.conf file.
Which can be found under the Apache menu...
Like so...
<VirtualHost *:80>
DocumentRoot c:\wamp\www\laravel\public
ServerName testing.com
</VirtualHost>
And your hosts file will reflect the url you choose...in this case...testing.com
127.0.0.1 testing.com
Checking rewrite_module
Go to
wamp icon
Apache
Apache modules
check rewrite_module
And cheers , there you are after some headache
Apache rewrite_module must be enabled in WAMP as well. It works with my wampserver.
Actually it has a pretty easy solution. All you have to do just check the rewrite module in apache. Check the steps in image
laravel problem with wamp server solution
Create an index.php file in the root.
<?php
header("refresh: 0; http://localhost/appnamehere/public");
?>
If you have multiple sites under one domain, you may not be able to change your public webroot.
I had all the correct settings, and the right .htaccess files in the right place, but it would not redirect. This fixed it for me.
This article was helpful in getting the wampserver/wampmanager links working.
Project Links do not work on Wamp Server
Post Script:
If you add to the virtual host file at:
E:\wamp\bin\apache\apache2.4.23\conf\extra\httpd-vhosts.conf
and you create a virtual host that points to the public directory like this:
<VirtualHost *:80>
ServerName Blog
ServerAlias Blog
DocumentRoot E:/wamp/www/Blog/public
<Directory "E:/wamp/www/Blog/public/">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require local
</Directory>
</VirtualHost>
#
and you add to C:\Windows\System32\drivers\etc\hosts
# localhost name resolution is handled within DNS itself.
127.0.0.1 localhost
::1 localhost
127.0.0.1 Blog
::1 Blog
You do not need the index.php file I suggested. That file works if you are NOT creating a virtual host, both are not needed. It's one or the other (although it does no harm to have it).
They only right way to do this is to point web server to public directory. For example, if you've installed Laravel in C:/xampp/htdocs/ directory, you need to use these settings:
DocumentRoot "C:/xampp/htdocs/public"
<Directory "C:/xampp/htdocs/public">
Never edit .htaccess inside public folder. If you did this, you need to get original file back. Restart Apache after you make these changes.