-
Notifications
You must be signed in to change notification settings - Fork 3
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
locks up forever on init.sh on RHEL linux releases / wrong instructions / bad location / bad name #11
Comments
This is your mistake:-
(missing backslash) should be
|
has this in your installer
but has this in your hooks:
... those are not the same place... |
also does not have any restore hooks |
Hello @gitcnd 👋 Here myself facing the same issue of the init hanging; but still hadn't time to fix this and, plus, the issues you've just reported. Thank you for taking your time to try this script and find my mistakes on it; hopefully I'll fix these right this year. Please note I've recently introduced breaking changes (presenting the .gitmeta-cid file), starting from the commit fc4e662 (with the help of CursorGPT, as my time nows' quite limited compared to 2021 and StackOverflow can become a hell). BTW, the endgame for git-meta is being able to apply the repo's .git-meta metadata at checkout! |
I re-wrote the entire thing: it's here, tested, working nicely https://github.com/gitcnd/git-meta I also added a feature I like: https://www.instructables.com/How-to-Use-git-on-Your-Own-Machines-to-Manage-Web-/ |
my "ps" says it's locked up at "cat".
dodgy bash script probably?
Also - instructions seem wrong?
Copy git-meta.sh and init.sh into your repo
seems like a less-than-ideal idea to stick the script in the repo itself? Shouldn't this be in /usr/local/bin/ ?
/usr/bin is the wrong place to put local scripts
init.sh is a bad name. should be git-meta-init.sh or something more sensible.
this is not portable (centos/redhat/etc):
sudo apt install
it's also a bad idea to install stuff without asking or checking if it's already there anyhow. Don't do that - just tell people it's a dependency, and stop if it's missing.
The text was updated successfully, but these errors were encountered: