Skip to content
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Developer installation of esm-server and eao-public too complicated #506

Open
ActionAnalytics opened this issue Feb 25, 2019 · 0 comments
Open

Comments

@ActionAnalytics
Copy link
Contributor

ActionAnalytics commented Feb 25, 2019

Setting up esm-server and eao-public should not require so many manual configuration steps.

Another project that has a smoother approach is MDS. See:
https://github.com/bcgov/mds/blob/develop/USAGE.md
https://github.com/bcgov/mds/blob/develop/Makefile

Which uses two commands, 'make local-dev' and 'make rebuild-all-local' to set up the local developer environment.

The approach needs to be able to run on Mac, Linux and Windows. MDS uses make but esm-server/eao-public does not need to use make, as long as whatever solution is created works on all three development platforms.

A nice to have would also be an additional separate script to set up the tools and prerequisites via package managers (brew, apt, rpm, and choco) so that VS Code is present with all the plugins needed to easily start making changes to the project.

Addressing this issue would help us facilitate community contribution.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant