Database migrations
Some times we need to change the schema of data in the database as we evolve ShareLaTeX, migration scripts are used to automate this process. They will have been run on ShareLaTeX.com first which is the largest instance of ShareLaTeX in the world so most eventualities will have been encounter already, however we make no guarantees over your data. Please backup before running any migrations.
When upgrading to a new docker image any migrations which have not yet been run will be automatically executed, this may take some time depending on the size of your dataset, tailing the logs will let you know how it is going.
If you do not use the recommended docker install and instead choose to run the update processes yourself the the grunt command grunt migrate will run the migrations for you, e.g., after upgrading from v0.1.4 to v.0.2.0.
- Quickstart Guide (Overleaf Toolkit)
- Hardware Requirements
- Database & Dependencies
- Creating and managing users
- General configuration
- Configuring Email
- SSL & Nginx reverse proxy
- Data and Backups
- Configuring Headers, Footers & Logo
- Password Restrictions
- i18n Languages
- Logging
- Common Config Options
- F.A.Q
- Troubleshooting
- Full Project History Migration