Skip to content

Instantly share code, notes, and snippets.

What would you like to do?

Abhinav Khare | CosmicCoder96 | FOSSASIA : Making Open Event/ Eventyay production ready


This summer, I worked on FOSSASIA's Open Event project, and making FOSSASIA's deployment of the project called Eventyay production ready. The Open Event Project enables organizers to manage events like conferences and helps them customize according to their event requirements. It offers features like call for speakers, and can accommodate events with several tracks, venues and sessions. The Open Event project has an API server which is consumed by the clients, I contributed code to both the API server as well as the Frontend called Open Event Frontend. I also handled the devOps of the project while transferring from Google Cloud Platform to Hetzner cloud platform.

Community Bonding:

  • Solved bugs and continued to refactor the legacy database to make it suitable for the new system, as all changes were not covered via migration files.

Phase 1:

  • Created the devOps infrastruture for Eventyay. Set up auto-deployment pipelines for the frontend using docker hub.
  • Shut down and dismantled the legacy version of eventyay deployed on kubernetes cluster to save resources.
  • Created a domain called, and transferred all the data from the buckets in Google cloud storage to it, ann redeployed the legacy version on Hetzner cloud at as a back up.
  • Solved numerous issues related to fastboot deployment, to increase the load times of the app.
  • Solved all the issues which arised after project was upgraded from Ember 3.3 to 3.10, along with all the dependencies.

Phase 2:

  • Revamped sessions speakers submission to smoothen the flow of submission process.
  • Created a download service to set a standard for downloading files from the api server including order tickets and invoices.
  • Using ember table as a reference, modified and reopened it as a component to create a standard table of the app to begint the switch from Ember model tables to Ember tables.
  • Implemented search, sort, pagination and size-select menus for Ember tables.
  • Redesigned the order flow for new users to be able to purchase tickets without registering.

Phase 3:

  • Implemented test email module.
  • Expanding upon the existing custom forms, Implemented complex custom forms to allow the user to create fields himself, with complex sub options like radio buttons and check boxes.
  • Converted the 18 tables of the app to ember tables to make use of the module developed in phase 2.
  • Redesigned role invites flow,

Code Contributions:

Social Outreach:

Other Links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment