shish / votabo

1 stars 1 forks source link

How do I make this work? #1

Open Azula opened 11 years ago

Azula commented 11 years ago

Is this another shimmie board project? If it is, is it an extension? or is it a separate project?

How do I install this? I tried uploading it to my directory and it didn't work.

Please give steps on how to do this.

shish commented 11 years ago

It's an experiment for my own amusement, to see if I could recreate shimmie in a different programming language. So far it has about 1% of shimmie's features, is much harder to install, and has no real benefits to anyone except developers :P

(The plan is that one day it will be better than shimmie, since the foundations are cleaner and more suitable, but that day is not today~)

Azula commented 11 years ago

I am just curious, but how about the paheal-beta site for rule34? Isn't that ran by the same so called 1% shimmie features of Votabo? The exact code repository for the beta version you used for rule34-beta would be enough for me to experiment and add more features on my own.

And if the current code repository that this votabo has is exactly the same thing, then if you would be so kind to please give me steps on what I should do to activate it accordingly? Because I am thoroughly at an end point.

shish commented 11 years ago

This repository is the one used for rule34-beta (if you look at the HTML templates you'll note that there aren't even separate themes yet, just rule34 stuff hardcoded into it...)

Anyway, if you're not put off by some fairly major parts being missing:

# get the code, create a virtual environment with all the necessary libraries
$ git clone https://github.com/shish/votabo.git
$ cd votabo
$ virtualenv env
$ ./env/bin/pip install -e ./

# If you want to use an existing database, edit development.ini
# and point sqlalchemy.url to it, and install a database driver:
$ ./env/bin/pip install psycopg2 # for postgres
$ ./env/bin/pip install MySQLdb # for mysql (not tested)

# if you want a new, blank, sqlite database to play with:
$ ./env/bin/initialize_votabo_db development.ini

# see if the self-tests pass:
$ ./env/bin/nosetests votabo/tests/*.py

# run the server
$ ./env/bin/pserve development.ini

# view the site
$ firefox http://localhost:6543/
Azula commented 11 years ago

I'm grateful for your help and wisdom - but damn, I'm still kinda lost.

Could you just provide a repository where I see an install "PHP script". I just want to input the Host datatype MySQL info and get it working as a test. All these "#" & "$" symbols confuse the heck out of me. I the first option (combine the shimmie libraries with the votabo) but it didn't work.

I don't know why this is giving me a hard time. It seems to be a much difficult install than Shimmie.

shish commented 11 years ago

This isn't written in PHP ^^;

TL;DR: it's an app rather than a script, it needs to be installed and run rather than just dropped into a folder

That said, I do have a half-working PHP-to-app bridge; still needs some more work before it would be suitable here though...

Azula commented 11 years ago

I see. Now it all makes sense - I thought I was going crazy. But it turns out I'm currently limited to one way of doing things. I will look forward to your code-conversion bridge.

By the way, I'm kinda curious if you have an idea on how I could add something like github's comment-style as a feature into the comments template on shimmie? -

  1. https://github.com/yuku-t/jquery-textcomplete
  2. https://github.com/m2w/talaria
  3. https://github.com/evansolomon/wp-github-flavored-markdown-comments
  4. https://help.github.com/articles/github-flavored-markdown

Is this something that must be programmed into shimmie? Or could I implement it myself? Because, it would be cool to consider this type of thing when making Votabo. Especially the "preview" feature that Github has. I mean, I know that GitHub uses, what they call, "GitHub Flavored Markdown" for messages, issues, and comments. But it differs from the standard-Markdown in a few significant ways and adds some additional functionality.

And I'm guessing that asking for live-comments as a future optional feature is probably asking too much.