I also found the same issue with Cherokee 1.2.98. In particular, my application was also Redmine, and I accidentally 'cleaned' it up because it was considered an orphaned installation.
After losing my install, I went ahead and reinstalled via the Cherokee Market, and found the same issue happening again. This time though, I've remembered to avoid using the clean up function, and ensured to move the installed application where it shouldn't get touched. Is there a bug report in for this issue? On 22 August 2011 23:41, Kev <[email protected]> wrote: > Yes I got the really same on installing redmine some time ago. > Installation was always fine, works great but cherokee think it's > orphan as you describe it. Don't know which cherokee version it was. I > removed it afterwards and ended up installing redmine "the old way"... > > 2011/7/3 Sangwhan Moon <[email protected]>: > > Hello, > > > > I've been giving this new marketplace thing a spin on 1.2.98, and noticed > something weird - everything I install becomes a orphan installation, even > if it's perfectly functioning. I didn't know that it could do something > potentially volatile, and went ahead and cleaned-up a redmine installation > that I've been configuring for a entire day. Now I'm doing it again, and it > still thinks it's orphaned. > > > > Has anyone else seen this behavior? > > > > Sincerely, > > Sangwhan > > _______________________________________________ > > Cherokee mailing list > > [email protected] > > http://lists.octality.com/listinfo/cherokee > > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
