-
Pierre Ozoux authoreda450375d
migration-format.md 1.75 KiB
IndieHosters migration format
Deprecated
Deprecated by the web app migration procedure
Version 0.2.2 (deprecated)
When a user exports their data for domain.com, they get a zip or tar file that contains different files, depending on which application is running on their domain:
If using the 'static' application
- TLS/domain.com.pem - Concatenation of the unencrypted private and public key of the TLS certificate, and intermediate CA cert if applicable.
- static/www-content - static content to be placed in the web root
If using the 'static-git' application
- TLS/domain.com.pem - Concatenation of the unencrypted private and public key of the TLS certificate, and intermediate CA cert if applicable.
- static-git/GITURL - git url to pull the static website content from
If using the 'WordPress' application
- TLS/domain.com.pem - Concatenation of the unencrypted private and public key of the TLS certificate, and intermediate CA cert if applicable.
- mysql/dump.sql - the dump of all their MySQL databases
- mysql/.env - contains the MySQL password
- wordpress/.env - contains the MySQL password
- wordpress/login.txt - username and password for the WordPress admin panel
- wordpress/.htaccess - htaccess file for WordPress
- wordpress/wp-content - php files to be placed in the web root
If using the 'Known' application
- TLS/domain.com.pem - Concatenation of the unencrypted private and public key of the TLS certificate, and intermediate CA cert if applicable.
- mysql/dump.sql - the dump of all their MySQL databases
- mysql/.env - contains the MySQL password
- known/ - php files to be placed in the web root
- known/.env - contains the MySQL password
- known/login.txt - email address and password for the Known admin panel