Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make getmeza.sh configurable #21

Closed
3 tasks done
freephile opened this issue Feb 28, 2024 · 0 comments
Closed
3 tasks done

Make getmeza.sh configurable #21

freephile opened this issue Feb 28, 2024 · 0 comments
Assignees
Labels
bash shell scripting best practices doing the right stuff code health best practices enhancement New feature or request git version control
Milestone

Comments

@freephile
Copy link
Owner

freephile commented Feb 28, 2024

This issue is one instance of issue #1

getmeza.sh currently looks like this:

# if /opt/meza doesn't exist, clone into and use master branch (which is the
# default, but should we make this configurable?)
if [ ! -d "${INSTALL_DIR}/meza" ]; then
	git clone https://github.com/enterprisemediawiki/meza.git ${INSTALL_DIR}/meza --branch master
fi
  1. We need to make the repo configurable (so forking is easy)
  2. We need to make the branch configurable (so you don't need an immediate extra step to work on a new release)
  3. We need to add a 'depth' parameter (because the full .git object database for MediaWiki is over 2GB!!)
@freephile freephile changed the title Remove / replace the hard-coded enterprisemediawiki Make getmeza.sh configurable Feb 28, 2024
@freephile freephile added enhancement New feature or request git version control code health best practices best practices doing the right stuff bash shell scripting labels Mar 1, 2024
@freephile freephile self-assigned this Mar 1, 2024
@freephile freephile added this to the Release 1.39 milestone Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bash shell scripting best practices doing the right stuff code health best practices enhancement New feature or request git version control
Projects
None yet
Development

No branches or pull requests

1 participant