Open strogonoff opened 3 years ago
Added a note about possible templating requirement in future.
This is a good idea. Let’s do it.
Example scaffolding project: https://github.com/paneron/glossary-site-scaffolding.
As one of the parameters, the action would be given an URL that points to a similar repository. The action would need to fetch the repository and place it in dataset root, per issue description.
(cc @CAMOBAP)
In progress
Status:
build
action is ready, test failed because there is no correct scaffolding repo providedaws-deploy
action implemented as a separate onehttps://github.com/paneron/iev-data-subset/pull/5 - ready for review https://github.com/glossarist/glossarist.org/pull/25 - ready for review
@strogonoff I need help with:
iev-data-subset
feature/first-release
to main
@strogonoff according to my understanding this task can be closed, can you confirm?
A couple of example sites that have scaffolding in their repository:
The idea is to remove the project scaffolding from data repositories, to reduce duplication and make repositories only contain the data. Scaffolding will instead live in separate repository (or, more likely, multiple repositories for different data types). Meanwhile, each data repository will just specify a single action, and pass requisite parameters to it.
We still might need to maintain different scaffolding repositories, but at least there can be one copy for each data type, rather than a copy for each data repository.
The action will receive parameters:
The action would be expected to:
package.json
,yarn.lock
, thesrc
directory, etc.)yarn build
—we’re using Yarn, althoughnpm build
could work as well)dist
directory in repository root, withindex.html
as entry pointTo be confirmed:
Caveats/possible changes in future:
static.config.js
) to provide site-specific data in project scaffolding.Related: