Difference between revisions of "ApiFusion.org/Modules/Import"

From ApiFusion
Jump to: navigation, search
m (1 revision imported: ImportWiki.html from http://localhost/wiki/index.php?title=Special:Export&action=submit ;ApiFusion.org/Modules/Import)
m (1 revision imported: ImportWiki.html from http://lowcost-env.pb3ahmsuf3.us-west-2.elasticbeanstalk.com/wiki/index.php?title=Special:Export&action=submit ;ApiFusion.org/Modules/Import)
(No difference)

Revision as of 04:42, 4 May 2017

Import between mediawiki

ImportWiki.html gives ability to import content of one MediaWiki into another in browser. You could choose the import of whole content, pages, or namespaces.

GIT Repositories

External git repositories could be the source and backup location for module and any branch within its hierarchy.

Different repositories could be associated with same or different paths, each holding particular type of information. For example, API documentation could reside separately from sources; contributors info structure will not match the source hierarchy leaving only top levels where particular contributor was involved.


Repository Import/Sync opens the wizard of folders/files along with recognized features. Wizard shall guide over features and help to select the relevant and updated(since last sync) ones. Once sync content selected, it will be posted under AF project/module tree.

It shall be available on any project level with ability to override the path within version control.


Back commit of AF data TBD.

UI access

The command will be available for every page over Tools menu in Sidebar

Repo sync

Two-way synchronization with exposed diffs and author/dates TBD.

Project level

Has multiple modules listed. Import action should trigger the previously configured imports on each.

Import configuration

The import configuration for module is set during the first import action and comprise

  • the repository path
  • path of (sub-)module
  • namespaces selection where imported data preserved

By default all namespaces will try to get relevant information from data at repository path.