No problem, I realized that I don't actually really need my created_at and published_at to be different, so I just ran "update contents set created_at = published_at" as a work around for the problem.  I just had some old entries that I migrated over from a different blog, and I wanted them to show up with the original published_at.

This is really helpful, because setting up everything is kind of overwhelming and painful.  I like the idea that you are saying mongrel/sqlite is the way to go for a basic vps hosted blog, that should make the install a lot less painful for other people.

On 7/6/06, Scott Laird <[EMAIL PROTECTED]> wrote:
Thanks.  I haven't fully dealt with the "upgrade an existing typo" case yet, and the created_at/published_at fix went into the trunk after 3.99.1 was frozen.  I'll try to spit out 3.99.2 in the next 24 hours, once I've had a few more bug reports.


Scott

On 7/6/06, Paul Barry < [EMAIL PROTECTED]> wrote:
I did a clean install first, that worked.  Then I tried to upgrade an existing typo, and I got this:

  copying /test/mocks/themes/123-numbers-in-path/about.markdown
  copying /test/mocks/themes/CamelCaseDirectory/about.markdown
  copying /test/mocks/themes/azure/about.markdown
/usr/lib/ruby/1.8/fileutils.rb:243:in `mkdir': File exists - /home/paulbarry/typo/test/mocks/themes/azure (Errno::EEXIST)
        from /usr/lib/ruby/1.8/fileutils.rb:243:in `fu_mkdir'
        from /usr/lib/ruby/1.8/fileutils.rb:217:in `mkdir_p'
        from /usr/lib/ruby/1.8/fileutils.rb:215:in `mkdir_p'

So then I just did a clean install again, then copied over my sqlite files and my theme files, ran rake db:migrate (which did nothing) and then I got my "upgraded" site.

The main page still sorts by created_at and the permalinks are generated from created_at.

On 7/6/06, Paul Barry < [EMAIL PROTECTED]> wrote:
I just ran gem install typo and it seemed to work.  I can't test it yet though, I think because my host blocks port 4517, which seems to be the port typo choose to start mongrel on.  At the end of the install, if says this:

Look in installer/apache.conf.example to see how to integrate with Apache.

Except there is no file called apache.conf.example in there.


On 7/6/06, Scott Laird <[EMAIL PROTECTED]> wrote:
Still?  It should have been copied to all GEM mirrors by now.  It worked fine for me this morning.

I need to figure out how to do 'gem install --verbose typo', and I need to figure out where the 'master' gem server lives.  As things stand, it takes 3+ hours from the time I upload a gem until it's usable.


Scott

On 7/6/06, Juan Lupión < [EMAIL PROTECTED]> wrote:
I'm getting a '404 Not found' error when running 'sudo get imstall
typo' on my Mac.


On 7/6/06, Scott Laird < [EMAIL PROTECTED]> wrote:
> I released a pair of Typo 4.0 pre-release gems yesterday to test out the new
> Typo installer.  Can I get a few people to test out the new Typo 3.99.1 gem?
>  Do this:
>
>     $ gem install typo


--
----------------------------------------------------
http://hronia.blogalia.com
_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list


_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list




_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list



_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list


_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list

Reply via email to