Re: [Tiki-devel] Asking for feedback: Tiki code organisation reorg, take ... 3?

Thank you Benoit for improving Tiki.

I have a more end-user/consultant point of view than a coder one. 
I understand the reasons behind the organization proposed and may be there is no room here for a end-user interfering with the plan 🥴 but still this is my thoughts.


I would like to point that it should be easy, easier or at least not harder 😉 to backup admin changes and users content added to a Tiki.

By those I mean the files I have to backup/copy/restore from time to time on a Tiki:

Themes
- Custom theme directory with favicons, fonts, icons, images, js, options, sass, templates (is there more ?): https://themes.tiki.org/How+To+Add+a+New+Theme
- Custom template directory (/themes/templates) - (the advantage of using this is to have custom templates available for all the themes) - (I couldn’t find documentation about it)

Languages
- The custom languages (lang/fr/custom.php for example) - couldn’t find a documentation about this: https://dev.tiki.org/item485-Custom-language-translation 🤭

Files
- File gallery and other files (storage) - (outside Tiki root for security - or is it old school now ?): https://doc.tiki.org/File-Storage#Storing_files_in_a_directory

Config files
- The .user.ini file: https://doc.tiki.org/php.ini#user.ini
- The system configuration file (tiki.ini.php file): https://doc.tiki.org/System-Configuration#Activate_the_system_configuration
- The robot.txt file

I recreate my db/local.php file each time… May be some other sees interest in having it backed up.

So as you can see it is already a little complicate (for me) and if my way are not the easiest, I have seen more complicated (attachment, tracker, forum or articles storage files, etc) and different Tikis.

May be with small changes where possible things can be improved before having THE big reorganization.
Like having lang/fr/custom.php or the config files stored inside a _custom folder.


I would like to end with a single or 2 folders to backup;
- Files uploaded (content)
- Files “custom” added (theme, templates, custom languages and configs)

Thanks again,
Bernard



> On 14 Apr 2023, at 0:27, Benoit Grégoire <[email protected]> wrote:
> 
> I've been working quite a lot on the following document in the past few weeks, with input from Marc and Victor:
> 
> https://gitlab.com/tikiwiki/tiki/-/blob/master/_PATH_DOCUMENTATION.md
> 
> I don't want to write too much here, otherwise nobody will read read the document ;)
> 
> As an experiment, I'll try to maintain a branch  for a while so people can comment line by line (or even add commits) here:  https://gitlab.com/tikiwiki/tiki/-/merge_requests/2489/diffs.
> 
> I think the document answers most questions (and links to previous discussions) except: Why now?
> 
> The main reasons are: 
> 
> 1) We have several major projects in JavaScript.  Storing the generated files in storage/public/vue-mf and serving them from there was always supposed to be temporary.  In the next weeks I will work on unifying the build system (so we don't have to manually build each vue component when we modify code), and get the generated files out of git.
> 
> 2) I need things to be easier to find and understand so I can help other developers more efficiently.
> 
> Nothing is set in stone in the plan, but files are likely to start moving soon so...
> --
> Benoit Grégoire
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel