Renaming the 'public' folder?

Evan · March 11, 2019, 5:51pm

This is a two part question…

I want the UF installation to be part of my website, and not be at the root.

My UF installation would be accessed through mysite.com/public (which is the UF public folder)

Is this ok?

Assuming the previous point stands, I would prefer to rename the public folder into something else.

Possible?

Malou · March 12, 2019, 12:07am

Technically, you just need to overwrite this constant :

github.com

userfrosting/UserFrosting/blob/develop/app/sprinkles/core/defines.php#L14


*
* @link      https://github.com/userfrosting/UserFrosting
* @copyright Copyright (c) 2019 Alexander Weissman
* @license   https://github.com/userfrosting/UserFrosting/blob/master/LICENSE.md (MIT License)
*/


namespace UserFrosting;


// Names of root directories
define('UserFrosting\BUILD_DIR_NAME', 'build');
define('UserFrosting\PUBLIC_DIR_NAME', 'public');


// Names of app directories
define('UserFrosting\CACHE_DIR_NAME', 'cache');
define('UserFrosting\DB_DIR_NAME', 'database');
define('UserFrosting\LOG_DIR_NAME', 'logs');
define('UserFrosting\SESSION_DIR_NAME', 'sessions');
define('UserFrosting\VENDOR_DIR_NAME', 'vendor');


// Names of directories within Sprinkles
define('UserFrosting\ASSET_DIR_NAME', 'assets');

It might produce unwanted behavior however, as this is not tested (at least I never have).

Another solution could be a symlink, either in your filesystem or Apache / Nginx config.

zhangchenglin · May 27, 2019, 7:37am

@Malou
Is it best to use Nginx to solve this problem without modifying the UF source code to make it easier to update the UF version later?

Amos_Folz · June 4, 2019, 3:13am

Yes you are correct, using Nginx/apache would be the best practice and make sure it is easiest to update UF later on.