yogthos / yuggoth

my blog engine (no longer maintained)

Home Page:http://yogthos.net

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Update site that is using yuggoth?

leontalbot opened this issue · comments

Hi!

I was looking for an authentification mecanism in cljs and found yuggoth! Great app!

I noticed that the app is not anymore the blog engine of http://yogthos.net

Could you update and provide examples of sites that are using yuggoth?

Thanks a lot!

Leon

Hi Leon,

I'm actually not sure if anybody else is using the engine. I'm using a lot of concepts from it in other apps, but I don't have any open source projects that demo them at the moment. I'm keeping it around as a sample resource, but not using it directly in other projects.

Thank a lot! I'm testing the site, seems I getting a problem with the initial conf.
Here is the error message:

FATAL: no pg_hba.conf entry for host {IP}, user {user}, database {databasename}, SSL off

Any clue?

I am using Heroku.

Thanks again!

BTW, I've notice your links to blog article all lead to the last blog entry:
http://yogthos.net/#/blog/52
http://yogthos.net/#/blog/51
http://yogthos.net/#/blog/44

I suspect it has to do with your blog engine switch.

Cheers!

From the error it looks like you might be missing postrges db config for Heroku. I haven't tried running it on Heroku myself since I use a VPS.

And yeah, the new blog is static, so the links just take you to the current page. In the old blog they got resolved on the client to a specific blog entry.

Dunno if this will help Leon.

This is all I had to do to get it running on Heroku. However I havent
updated to Dmitris latest code base, so not sure if its still valid.

https://blogofamadman.herokuapp.com/blog/1-how+to+setup+yuggoth+blog+engine+on+heroku

There is a part two on the blog as well

Cheers

On 22 January 2015 at 14:30, Dmitri Sotnikov notifications@github.com
wrote:

From the error it looks like you might be missing postrges db config for
Heroku. I haven't tried running it on Heroku myself since I use a VPS.

And yeah, the new blog is static, so the links just take you to the
current page. In the old blog they got resolved on the client to a specific
blog entry.


Reply to this email directly or view it on GitHub
#12 (comment).

Go it to work with another DB as a service! So ignore my question!