Skip to content

Latest commit

 

History

History
36 lines (28 loc) · 2.73 KB

README.md

File metadata and controls

36 lines (28 loc) · 2.73 KB

Developing inside of ecore

Structure of the repository:

  • cf - CloudFormation templates
  • cron - Cron jobs, run in ECS, but can be simulated manually
  • debian - Fixes for Debian/Ubuntu shortcomings
  • docker - Docker images for production and development build
  • docs - Documentation
  • ecore - Core Everything libraries
  • ecoretool - Tool for importing and exporting database nodes
  • etc - Configuration items
  • jobs - Manual processes run by operations on the server
  • node_modules - Node.js structure
  • nodepack - Infrastructure nodes, exported to XML
  • ops - Scripts used in the operation of E2, not server utilities. Typically cloud
  • react - Modern React frontend
  • serverless - E2 Perl Layer dependencies, previously lambda support
  • t - Perl tests
  • templates - Mason2 templates used for display purposes
  • tools - Some of the tools that keep the site glued together
  • www - Basic web properties, icons and index.pl

To start to develop for e2

  • Install Docker Desktop
  • From the main directory (re-)run ./docker/devbuild.sh
  • Visit http://localhost:9080

Make changes to the source directory and re-run ./docker/devbuild.sh to relaunch the container. The database won't be touched unless you explicitly run the corresponding devclean.sh script.

Working with perl dependencies

E2 uses carton to manage the perl dependencies. In order to update them, they need to be able to build locally, which may require libmysqlclient, imagemagick, expat and other dependencies

Note that Ubuntu 22 LTS does weird things with Perlmagick6, so using the OS distribution