...
Changes to either production or test/sandbox require approval by the Atlas team for accessibility and security concerns through a pull request. Known issues for rejection include old javascript/jquery and links to external CSS files (all CSS must be in the Emory Aeon github repository and not refer to another repository). Pull requests generally take 24-48 hours for approval. Emergency changes that need a quicker turnaround should be made in the Github repository and then a ticket should be sent to Atlas support (support@atlas-sys.com) notifying them of the urgent change that is needed.
For development work, clone the fork https://github.com/AtlasSystems/hosting-aeon-emorysb , and then the PR will automatically compare to the AtlasSystems-Prod sandbox repo. Changes to Aeon webpages can be tested prior to submitting a pull request by making changes within the testweb directory. These changes take effect immediately and are designed for developers to test webpage changes. Viewing testweb pages requires being logged into VPNproxy. To see testweb changes, add /testweb to the beginning of the link address. For example the page https://emorytest.aeon.atlas-sys.com/aeon/aeon.dll?Action=10&Form=10 would be https://emorytest.aeon.atlas-sys.com/aeon/testweb/aeon.dll?Action=10&Form=10 in testweb.
...