is it possible to change the old site that have been built so it can be accessed by something like this :
old site become : www.example.com/2021
and the new site : www.example.com
Thanks.
You can change document root or maybe just change route in config, visit https://codeigniter.com/userguide3/general/routing.html
Open the project folder on your new site. Open and edit the .env file at the new site's root project directory and change the line below:
app.baseURL = 'http://www.example.com'
Related
i have my my website like abc.com/dev now i want to transfer it to abc.com,
what minimal changes should i do to make it work .
My website is in joomla is there way that i just move folder to main folder and add db setting.
Please guide i am new to joomla
Just Drag and drop your folders from your subdomain folder to root folder through FTP.
Then only changes you need to do is in your 'configuration.php' file located at the root folder. If your DB is not changed then do not change any of its setting. Just change the path of 'LOGS and TMP' folders in config file to the root path that are :
$log_path, $tmp_path
And I hope your site will work perfectly as it was working before.
I've been successful in deploying Laravel 4 applications on shared hosts by simply editing the paths here at /bootstrap/paths.php.
However, Laravel 5 does not have that file. How does Laravel 5 manage paths? I have access to the root directory with public_html. I can upload all the files to root and public directories, but confused where to look for the paths to be maintained?
Laravel 5 is smart enough to detect all it's path. I was missing some of the files during upload. :)
What I did was upload all the files as it is structured and the content of public folder was uploaded into the www directory, that's it!
You can play with creating new Application() in bootstrap/app.php. Its constructor takes argument which tells where is rest of the application related to public/index.php
Currently app.php has
$app = new Illuminate\Foundation\Application(
realpath(__DIR__.'/../')
);
Change the /../ to something else if rest of the application folders for example in ../laravel/ compared to index.html
If you have cPanel in your shared hosting you can try these easier methods before trying to move the Laravel's public folder:
Often you also have an SSH access when you have cPanel on shared hostings, so you can replace the www folder (i.e. the website document root) with a symbolic link to [app]/public, then deploy your Laravel app inside the [app] folder.
If you are deploying on a subdomain, e.g. [app].example.com, usually with cPanel you can choose the document root, then you can simply set it to [app]/public.
I think the two methods above are both easier and safer than moving the public folder. I would keep this as the last option.
Take a look here for some more info: http://blog.netgloo.com/2016/01/29/deploy-laravel-application-on-shared-hosting/
I have a Joomla installation set up on my local server. I have duplicated with a new name the top-level Joomla folder so that all the information I have already put into the database can be edited slightly, whilst still keeping the original intact.
I have copied the database files over to a new database and made the relevant changes in Joomla admin. I've opened up configuration.php and changed all the file paths to the new one.
However, now I'm getting a server error when trying to access the web page and admin area. Are there any other files I need to edit with the new path to enable it to work under the new parent folder?
You shouldn't have to edit any files with any paths to make it work other than the tmp and log folders and the root folder line in htaccess if you have SEF URLs turned on. Turn off SEF URLs and see if the site starts working, if it does, then you need to edit htaccess. Since your admin is not working, my guess is that you messed up your configuration.php. Copy over the original unedited version to the copy site, it should work. You can then adjust the tmp and log paths within the admin in the global configuration.
I have copied a live joomla site. The original is found at [this][1] website. The copied one in found [here][2]. But all links (e.g. in the left navigation menu) result in 404 errors. The administrator backend is accessible and i can create new menu items in the copied one but they all result in 404 errors.
I did adjust the configuration.php file so var $tmp_path var $log_path point the right paths. i updated var $live_site = 'http://hosting01.hestronic.nl/~ijskoud2
The live_site was empty in the original configuration.php file.
Do i still need to run an update or something?
Thank you
PS joomla 1.5.25
Turn off search engine friendly url feature in System -> global configurations.
If you really want to enable SEF URL then you need to set your rewrite base according to your site dir in the server.
For $live_site variable, no need to modify it and keep it empty.
I ran into a similar issue where all of my links were doubling up. Fixed by prefixing http:// to $live_site
You don't need to do anything to $live_site, just leave it blank. The tmp and log paths are the only thing you need to touch. If you have SEF URLs turned on, you will also need to change the rewrite base from / to what ever the subdirectory is.
I disagree with my friend #Brent. Go to your DB to the menu table (by default its called jos_menu) and look for the "path" column. you probably need to manually fix the paths of all your menus to point to the new folder.
Check if the .htaccess file exists in your new folder. if not exists remove the sef url configuration from admin side.
I have created a sub-domian and I want that as soon as the user goes to that domain, a file named web.php should automatically open rather than showind the web directory.
Please tell me if it is possible
Place an .htaccess file in the root directory of each created sub domain and fill it with:
DirectoryIndex web.php