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
Can't download theme #182
Comments
I had the same error.
Thats it! |
I ran into a similar problem as OP when creating a theme-based site (from linux vm using windows vmware):
I'm running ubuntu 22.04. Github is configured with a ssh key created on that VM, and I tested it with:
I tried the workaround provided by @sanati, but I do not understand no. 5 (copy files/directories). I thought the idea of Plenti templates is so you can run the template with no changes and only override what you need to. Are there certain files I should be copying? If I copy all files/directories from the template, why create a new site at all. Why not simply clone the theme and make it your own site (without a "theme" enabled)? Any help would be greatly appreciated. |
That's correct @dougwinsby, you should only have to copy the files you want to override. The only required file in your base project should be a Sounds like there might be a bug here. I'll do some testing to see if I can recreate the issue to figure out what's going on. |
Trying to run ssh: handshake failed: knownhosts: key mismatch
Then unable to find any valid known_hosts file, set SSH_KNOWN_HOSTS env variable
Then ssh: handshake failed: knownhosts: key is unknown
Then doing:
So ultimately you just need your |
If I clear the contents of
Does something like that work for you @stephanieluz? |
Thank you @jimafisk for researching this. I haven't used ssh keys with github under linux before (I'm a Windows guy), so this is new to me. Unfortunately, I was unable to get things working using your suggestions. I keep getting the connect: permission denied2022/05/17 13:17:04 errs.go:57: Can't clone theme repository: error creating SSH agent: "Error connecting to SSH_AUTH_SOCK: dial unix /run/user/1000/keyring/ssh: connect: permission denied" error creating SSH agent: "Error connecting to SSH_AUTH_SOCK: dial unix /run/user/1000/keyring/ssh: connect: permission denied" (File: /home/runner/work/plenti/plenti/cmd/theme_add.go, Line: 75) 2022/05/17 13:17:04 errs.go:57: Can't get HEAD: reference not found reference not found (File: /home/runner/work/plenti/plenti/cmd/theme_add.go, Line: 84) panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x986565]I'm sure it's a problem on my end, but I was able to clone manually and Conceptually, I'm struggling with the usefulness of including a theme, though. While I'd like bug fixes from an embedded theme, I wouldn't want an external change to break my site. I think I will just clone a theme as a starting point, and take it from there. (BTW, I really like this project... thank you for your work on it.) |
Unfortunately still getting the error too. I checked and the
But it still returns |
Thanks for testing @dougwinsby and @stephanieluz. I'm thinking that running the git clone over SSH is more trouble than it's worth. Since the theme repos are public, we should be able to use HTTPS without having to enter usernames / passwords. Does something like this work instead:
|
Yes! |
Woo that worked! |
Ok great! I'll update the documentation to reflect this, I think it'll be easier for almost everyone. @dougwinsby to answer your questions:
The main advantage is to give the theme creator the ability to push out changes in a centralized way. If 100 people clone a theme and edit it directly, the theme creator would have to work with them individually to accommodate a bug fix, but with themes they can push it once and everyone can get the benefit. You don't need a theme though, you could always watch the original repository yourself and manually pull in any changes you want, or go your own way completely. The Plenti API still changes from time to time since we're not at a stable 1.0 release yet, so themes can help you avoid having to pay attention to our changelog. Alternatively if we update the API and it breaks your site, you can always lock the version of Plenti you're using in CI to an older version so your site continues to build successfully (all versions of Plenti are available on our dockerhub).
Themes should only update when you manually pull the changes into your project (i.e.
This is a perfectly valid approach. Every theme is simply a Plenti website and every Plenti website can be used as a theme. If you don't want upstream changes, simply using another Plenti site as a starting point is the approach with the least overhead. |
Docs are updated: plentico/plenti.co@3b08719 |
When I run
plenti new site my-site --theme=git@github.com:plenti-themes/bigspring
it throws:I thought it might be because I didn't have an SSH key uploaded to GitHub, but the problem still persists even after adding it.
Possibly related to src-d/go-git#454
The text was updated successfully, but these errors were encountered: