Hi all,

I've been analyzing some files and IMHO there are a lot of settings in .travis.yml and .codeclimate.yml that requires more maintenance than it should. And I would like to minimize this. Some ideas (not sure if all of them are feasible):

.travis.yml

• Less (or at least more readable env vars): one per line, or (even better) use python-decouple (already a dependency I guess; or even os.environ) to set those values as defaults in the app it self;
• Do we really need to test for 3.4 and 3.5? We should go for a specific version I guess (and be sure that it passes);
• As I might touch on database configuration for the last item, any pro or con of working with dj-database-url? I like it;
• coverage command requires us to manually add each app, there might be a better way to set this include/exclude argument that requires less maintenance.

.codeclimate.yml

• exclude_paths requires us to manually manage it, there might be a better way to set this that requires less maintenance;
• languages: do we need Ruby, JS and PHP?

I'm willing to tackle this list (if we all agree that they are valid claims) and surely take #21 into account. What do you think?

Maybe a mobile app could even improve the usage rate of the application.

I believe we could use something like Xamarin or React Native?
But I don't know if it's really useful, as the store fee is kinda prohibitive for a nonprofit project.

Ideally this will required some coordination with #18.

Now that #18 is done, maybe it'd be a good idea to add throttling to the API, here.

For now I don't think that we really need some great values, probably 1/minute will be fine.

Create a management command to send email to users after a given amount of months requesting information about the status of their pet.

Something like this, but much more polite:
Was it found/adopted? Please update the status within the app.

Maybe generate using HTML and CSS and convert it to PDF

Seems related:
travis-ci/travis-ci#3251

Hello, I designed several logos for Pets. If you like any of these, I will send you a pr and files.

Also, If there's anything you want, I can design it.

At least for the basic part of the UI (menu, buttons, etc)

Maybe show a counter along with the link (?)

A few projects have a button to deploy to Heroku, OpenShift, etc.
I think it's a nice way for people to take a look at a running instance.
But I need to check the docs to see how much changes would be necessary in the project.

Also I think it'd be easy to have a running demo in @pythonanywhere, I could probably create a scheduled task to recreate everything in a daily basis with an updated version of the next branch.

Example repos:
@quokkaproject's Quokka
@heroku's Template

Docs:
Heroku

Maybe using https://github.com/brutasse/django-password-reset

error when make python3 manage.py compress

{% compress css %}




{% endcompress %}
from base.html

@dirtycoder,

I think that is a good ideia, add some extra information about how to contribute to the project. What do you think about this change in the end of README file?

How to contribute to the project

In order to make development and deploy to production simpler there's two settings module.
'dev' for development and 'prod' for production, both based on the 'base' settings.

Look in the settings modules for environment variables which need to be configured.

Install dependencies and requirements:

#Pillow dependencies
sudo apt-get install python-dev python3.x-dev libjpeg8-dev

#PhantomJS, see the julionc tutorial at https://gist.github.com/julionc/7476620

pip install -r requirements.txt

Sorry man. But I can not to find "requirements/local.txt" file as it described at README file.

The current version is really simplistic.
It could be a lot better.

Maybe after the account creation and after the pet register.

This page could be used to tell the user the next step, like sharing on Facebook, etc.

For now this could be very simple and read-only I believe.
But as I would like it to not be a problem for resource usage in case of usage abuse, I think we need something to control the rate of requests.

The regex for the new URLs are wrong. It's capturing everything (obviously).
Change it for a less hungry expression.

I think it'd be good to have pagination enabled in the lost pets view and adoption pets view.
Maybe the search view too?

i would love to see this in action. Any demo?

Maybe it's a good idea to use the Django's flatpages app.

So pages like the about would be more easily changed on a per-instance basis.

There's some code in the management command that could be extracted to a helpers.py or utils.py module and then be reused here.

Hi!
I am trying to translate this app to Russian.
Almost all is good.
But I do not understand how is it possible to translate kins of pets.