Pyret Integration Notes

[anzook]

Initializing this space as a way to document general progress and ideas regarding the integration of Pyret and VMT.

Link to Documentation and Architectural Notes

Major updates and changes should be documented there, this space is for documenting thoughts and work in progress.

[anzook]

14-Mar Notes

• investigated using Github Codespaces:
  This would allow for a shared workspace to both
• discussed which env (origin) the Horizon deployment should forward messages
  Planning to limit Pyret to staging, but investigate options on implementing an origins checker or plans to migrate to Prod
• investigated masking the Pyret server address with the new server established on Github Codespaces
  This would allow VMT-test/staging environments to be easily tied into the shared development environment and server. Therefore, devs can also do testing with multiple clients without having to make deviations from how Pyret is integrated in staging/production.

Current priorities for the project:

• Establish a method of shared development for the integration work
• Persist outputs in the interaction pane (right-hand side of the editor) when a user joins late or refreshes
• Overbearing control strategy prevents scrolling/viewing code

[anzook]

VMT-Team due outs:

• limit Pyret deployment to staging
• investigate control strategy as it relates to scrolling/code view of the editor and interaction pane

[anzook]

CodeSpaces notes:
Exposed server url: https://jpolitz-brownplt-code-pyret-org-g7xprrh994-5000.githubpreview.dev/

Notes:
Port must be reopened after restarting the server after edits (not yet a supported port attribute