-
Notifications
You must be signed in to change notification settings - Fork 26
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
Path to Hugo binary #41
Comments
Hi @max-arnold .
I think that if your site don't work on the latest stable version of hugo you should correct the cause of your source.
I don't want to support a method that doesn't conform to UNIX standards. Hope that helps! |
Ok, more details about my use case:
The binary is actually in the PATH, but only after I activate virtualenv by doing So, because supporting virtualenvs is out of scope of this project, what I'm asking is to allow me to customize hugo path on per-blog basis. |
I found multiple |
If customizing the binary path permit you to solve the problem, I can respond. |
The following runs the Rakefile. You can do it in the following way. deploy.sh
Rakefile
M-x easy-hugo-github-deploy |
Yes, this would solve my case. |
And sorry, but I do not understand your Rakefile example. If it is about deployment tasks, then I do not plan to change my deployment method or switch to Rake. |
Hi @max-arnold . Make hugo's binary changeable for each blog at 3b0516c It will be reflected in melpa in around 6 hours. sample setting (setq easy-hugo-url "https://yourdomain") (setq easy-hugo-bloglist '(((easy-hugo-basedir . "~/yoursource2/") |
Thanks a lot! Will try it tomorrow and report here if it works. |
Sorry, I forgot to inform you that my use case is solved and everything works just fine. You are great! |
Hi @max-arnold . |
How to specify different Hugo binaries for different blogs (for example if I they require different versions or I do not want to place hugo in PATH)?
The text was updated successfully, but these errors were encountered: