[DEFUNCT] Online manga reader
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.virtualenv
frontend
lib
pytaku
tests
.agignore
.bowerrc
.gitignore
.lvimrc
CONTRIBUTING.markdown
Gulpfile.js
LICENSE.txt
Makefile
README.markdown
app.yaml
appengine_config.py
bower.json
main.py
package.json
queue.yaml
requirements-dev.txt
requirements.txt
vendor.py

README.markdown

DEPRECATION NOTICE!!

No Maintenance Intended

I've decided to rewrite Pytaku from scratch to a) migrate away from Google App Engine and b) restructure frontend code to make a bit more sense. This repo will not be maintained anymore, but the production site will be kept live for the foreseeable future.

I'll announce Pytaku 2 once it's ready. Stay tuned!

Pytaku

... is the only online manga reader you'll ever need!

Join the chat room for latest development updates and official support:
Gitter chat

How to use

Read more about it on my blog post.

Pytaku currently gets data from batoto and kissmanga. Manga info is saved to Pytaku's own database after first view, so naturally popular manga titles will be blazing fast because somebody else has probably triggered the first view before you :)

The latest development version is deployed at https://pytaku-dev.appspot.com. Note that I might regularly break stuff there so don't use it if you want stability.

How to develop

Download and get familiar with Google App Engine Python SDK if you haven't already.

Frontend

To build client side assets, you'll need gulp. If you're not familiar with nodejs, I suggest installing it with nvm. When you have done that, clone this repo, cd into it and run:

$ npm install -g gulp bower
$ npm install
$ bower install
$ gulp init
# You only need to run `gulp init` once. After that, calling `gulp` is enough to recompile
# everything. If you want to minify css/js, use `gulp deploy` instead of `gulp`.

All the frontend code is in frontend/ directory, except for Gulpfile.js and bower.json. Built assets will go to frontend-dist/.

You can also use gulp watch to watch for frontend code changes and trigger livereload. Check out Gulpfile.js for more.

Backend

I strongly recommend using virtualenv + virtualenvwrapper. If you're not already using them, Google is your friend.

Once you've made and activated a virtualenv for pytaku, install the neccessary libraries in to ./lib/:

$ pip install -r requirements.txt -t ./lib

It's optional but recommended to install the packages in requirements-dev.txt:

$ pip install -r requirements-dev.txt

Remember to create a ./pytaku/config.py file that stores a secret key of your choosing. Example file can be found at ./pytaku/config.py.sample.

Then use Google App Engine SDK to serve it normally at http://localhost:8080. Easy, no?

Note: I have a weird thing for PEP-8 compatible code. If you use vim, install Syntastic and use flake8 as the python checker. I won't accept code that causes any error/warning in Syntastic.

Run your own site

License

PYtaku's source code is released under the GPLv3. See LICENSE.txt for details.