Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.

před 12 roky
před 12 roky
před 12 roky
před 12 roky
před 12 roky
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123
  1. # ![Pinry](https://github.com/overshard/pinry/raw/master/logo.png)
  2. Pinry is a private, self-hosted, [Pinterest][0] inspired by [Wookmark][1] and
  3. built on top of Django.
  4. ![Pinry Screenshot](https://github.com/overshard/pinry/raw/master/screenshot.png)
  5. ## Why?
  6. Mostly because I don't like sharing, I use pinup boards for personal inspiration
  7. boards. Also if I use a public platform like Pinterest or Wookmark then my pins
  8. run the risk of getting a DMCA take down notice. I might not even be able to
  9. pin something at all with websites now blocking tools like this. I rather
  10. bypass all these risks and just host it myself.
  11. ## Getting Started
  12. Pinry has three different customizable configurations:
  13. ### Development
  14. Have virtualenv and pip installed. You may also need to have the build
  15. dependencies for PIL installed.
  16. $ git clone git://github.com/overshard/pinry.git
  17. $ cd pinry
  18. $ virtualenv .
  19. $ bin/pip install -r requirements/development.txt
  20. $ bin/python manage.py syncdb
  21. $ bin/python manage.py migrate
  22. $ bin/python manage.py runserver
  23. Note: If you are on Ubuntu 12.04 there is a bug in PIL that causes it to not
  24. build in JPG and PNG support. You'll need to follow all the steps above except
  25. before `virtualenv .` run `sudo apt-get install python-imaging` and instead of
  26. `virtualenv .` run `virtualenv --system-site-packages .`. On older versions of
  27. Ubuntu and older Linux distributions you'll need to install PIL dependencies.
  28. On Ubuntu this can be done with `sudo apt-get build-dep python-imaging`.
  29. ### Jenkins
  30. If you want to use Pinry with your own Jenkins server I've already setup all of
  31. the settings on Pinry, just follow the instructions starting at section 3 on the
  32. official [Django Jenkins Tutorial][4].
  33. A quick tip, when you get to the `Add build step -> Execute shell` step instead
  34. of using his example use:
  35. virtualenv --system-site-packages .
  36. bin/pip install -r requirements/jenkins.txt
  37. bin/python manage.py jenkins --settings=pinry.settings.jenkins
  38. As noted in development be sure you have PIL installed or it's build
  39. dependencies.
  40. ### Production
  41. If you want a production server [Google around][2] for more information on
  42. running Django in a production environment and create a
  43. `pinry/settings/production.py` file. I don't cover this because there are
  44. hundreds of different ways to deploy a Django project and everyone has their own
  45. preference.
  46. ## Build Status
  47. For build information on the latest commit head over to my [Jenkins server][3].
  48. You'll get useful information on if all my tests are passing, my test coverage,
  49. and if I'm conforming with pylint and pep8 standards.
  50. ## Roadmap
  51. + Non-image URL pinning
  52. + Bookmarklet
  53. + Tagging, groups, multiple and/or user boards
  54. + Statistics/analytics with pretty graphs
  55. ## As Seen On
  56. + [USA Today](http://www.usatoday.com/tech/products/story/2012-04-27/pinterest-pinry-private-pinning/54584308/1)
  57. + [Hacker News](http://news.ycombinator.com/item?id=3895618)
  58. + [The Next Web](http://thenextweb.com/apps/2012/04/27/pinry-is-a-self-hosted-version-of-pinterest-that-gives-you-full-control-of-your-pins/)
  59. + [Python Weekly](http://us2.campaign-archive2.com/?u=e2e180baf855ac797ef407fc7&id=1f8c766c90&e=292d864a00)
  60. + [Pycoder's Weekly](http://us4.campaign-archive1.com/?u=9735795484d2e4c204da82a29&id=4f9b37c501)
  61. ## License (Simplified BSD)
  62. Copyright (c) Isaac Bythewood
  63. All rights reserved.
  64. Redistribution and use in source and binary forms, with or without
  65. modification, are permitted provided that the following conditions are met:
  66. 1. Redistributions of source code must retain the above copyright notice,
  67. this list of conditions and the following disclaimer.
  68. 2. Redistributions in binary form must reproduce the above copyright notice,
  69. this list of conditions and the following disclaimer in the documentation
  70. and/or other materials provided with the distribution.
  71. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
  72. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
  73. WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
  74. DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
  75. ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
  76. (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  77. LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
  78. ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  79. (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
  80. SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  81. [0]: http://pinterest.com/
  82. [1]: http://www.wookmark.com/
  83. [2]: https://www.google.com/search?q=deploy+django+production
  84. [3]: http://jenkins.bythewood.me/job/pinry/
  85. [4]: https://sites.google.com/site/kmmbvnr/home/django-jenkins-tutorial