Easy Numbered Headings

Overview

LML (LaTeX Math Lite) is currently hosted on Aerobatic, but this will be shutting down at the end of October. We should migrate to Appfire Connect platform.

This should be a relatively easy migration, since LML is purely a static (client-side) app and has no database.

https://bolosoftware.atlassian.net/browse/LML-7

Steps followed to address this:

1. From this reference we need to make sure our instance is having the prerequisites before get into the migration.

2. Once we have all the valid softwares are installed, by using

   create-appfire-app

    command we need to create standard framework and file structure that provides Webpack bundling, Babel trans-piling and code minimisation automatically so we can get started on our App code.

3. After giving required details after using the above command try executing npm install /appfire run and see you are able to get the connect json url created and able to install it in your test cloud instance.

4. Now, as we have the working base structure with Appfire Connect Framework, we can start migrating the existing macros to this framework.

5. Just start with one macro first and see it is working as expected. Here we need to make sure after building the app the folder structure should same as old App, if it is not copying the files to client/dist properly tweak the webpack.common.js to copy them accordingly.

6. If we are not properly move the files we may encounter the problems like below when you use the appfire-run command to generate ngrok connect json url dynamically.

   Cannot GET /macros/mathinline/
   App is not responding. Wait or cancel?

7. Once it is fine with ngrok url tested and move them code to dts by using appfire-deploy --env dts command. Here while we deployed we see the dynamicContentMacros entry in attlassian-connect.json is expecting index.html as well url parameters of both editor and macro, but this is not the case with ngrok, it was able to detect them without giving the index.html. If we are not giving we see the problem like below.

   <Error>
       <Code>AccessDenied</Code><Message>Access Denied</Message>
       <RequestId>ZW98EHZZYCEF2W4P</RequestId>
       <HostId>agLBj92jnDIlbgK2izaRdJ2n+ZMqqI9qBwCXG5Vq8HJcJyNOindm2D4D+RmJjWxPmhgFfLNspi0=</HostId>
   </Error>

8. After we see all the macros are working as expected, next step is to move the temporary code to actual Bitbucket project and try deploying it to Dev, Stage and Prod accordingly by using Pipeline builds.

9. Create the backup branch on the actual repo from master ( eg: aerobatic) and create another feature branch from master and merge the latest changes which we tested in our temporary repository .

10. As we are using Pipeline build make sure env.yml and bitbucket-pipelines.yml files are having right entries before Build and deploying.

11. This feature branch has the changes needed for migrate from old aerobatic to AC Framework.

{}