diff options
author | Joey Hess <joey@kodama.kitenet.net> | 2008-11-06 16:12:16 -0500 |
---|---|---|
committer | Joey Hess <joey@kodama.kitenet.net> | 2008-11-06 16:12:16 -0500 |
commit | 96d52b82edffae197ae182f7073d4b7a8d88880b (patch) | |
tree | 4e7fdd765226febeeb37bce10059970862ae06fa /doc | |
parent | db5ea4d4f01d7706c5397101ec860f8a471c1c55 (diff) |
response
Diffstat (limited to 'doc')
-rw-r--r-- | doc/bugs/messed_up_repository.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/messed_up_repository.mdwn b/doc/bugs/messed_up_repository.mdwn index 10bf5c35d..cb8aa875a 100644 --- a/doc/bugs/messed_up_repository.mdwn +++ b/doc/bugs/messed_up_repository.mdwn @@ -3,3 +3,17 @@ I messed up my local clone of my repository. It appears that there is a special clone, which contains .ikiwiki, local.css, recentchanges, and the like. How can I create a new version of this clone? + +> No, there's the srcdir, which ikiwiki populates with some of those files +> when run. Notably the .ikiwiki directory and all its contents, and the +> recentchanges directory and its contents. But not local.css. +> +> If you've lost .ikiwiki and it contained user registration info +> (passwords etc), you've lost that info. Everything else can be +> regenerated by running `ikiwiki -setup your.setup` +> +> If you still have .ikiwiki, but the git clone is messed up somehow, you +> can just make a new clone and move .ikiwiki into it before running +> ikiwiki. --[[Joey]] + +[[!tag done]] |