Should Wedge allow you to change all of its paths?
Advantages of changing paths:
- You can move your source files to a non-accessible path, meaning no one can see their contents, even if you server fails.
Advantages of keeping paths the same across all copies of Wedge:
- Moving your Wedge install to another folder is a no-brainer, because all paths are automatically updated.
- Seriously, even if someone could see your source file contents... Who cares? They can already see them on GitHub anyway!
To me, the only file that MIGHT warrant being moved to a non-web space is Settings.php, and even SMF doesn't support that... If you're not modifying your Settings.php file (i.e. keeping away from the admin area), you could consider turning Settings.php into a file saying "include (__DIR__ . '../../somewhere/Settings.php')", but because Wedge may not have write access to said path, it's not realistic to expect it to handle this kind of redirection easily.
It might be possible to create a hardlink to that file, but I'm not sure it wouldn't simply be shown in the same circumstances at a regular file.
Can anyone think of a GOOD reason to move your folders around..?
PS: media and attachment folders are a special case, though. It's likely that I'll keep the ability to move them around, because of potential disk space concerns.
- You can move your source files to a non-accessible path, meaning no one can see their contents, even if you server fails.
Advantages of keeping paths the same across all copies of Wedge:
- Moving your Wedge install to another folder is a no-brainer, because all paths are automatically updated.
- Seriously, even if someone could see your source file contents... Who cares? They can already see them on GitHub anyway!
To me, the only file that MIGHT warrant being moved to a non-web space is Settings.php, and even SMF doesn't support that... If you're not modifying your Settings.php file (i.e. keeping away from the admin area), you could consider turning Settings.php into a file saying "include (__DIR__ . '../../somewhere/Settings.php')", but because Wedge may not have write access to said path, it's not realistic to expect it to handle this kind of redirection easily.
It might be possible to create a hardlink to that file, but I'm not sure it wouldn't simply be shown in the same circumstances at a regular file.
Can anyone think of a GOOD reason to move your folders around..?
PS: media and attachment folders are a special case, though. It's likely that I'll keep the ability to move them around, because of potential disk space concerns.
