Please let me know what you think .. and add me a contributor if you like the work (there is some clean up that needs to be done ... such as: I added an admin for certain testing purposes)

I'm currently working on new UI by vue.js with webpack workflow because I found it hard to rebuild UI while using old styles. The old server-render UI will be removed after new UI worked.

• [x] Backend support for board

• Show:
  • [x] UI: show pins
  • [x] UI: show pins by tag
  • [x] UI: show pins by user
  • [x] UI: Single pin preview
  • [x] UI: show pins by board
  • [x] UI: show boards by user
  • [x] UI: view single pin
• create/update
  • [x] UI: Pin Edit
    • [x] Create pin from uploaded image
    • [x] Create pin from image url
    • [x] Add a pin to a specified board while creating
    • [x] Delete a pin
    • [x] edit a pin
  • [x] UI: Works with Bookmarklet
  • [x] UI: Create board
  • [x] UI: Delete board
  • [x] UI: Edit board name
  • [x] UI: Add pin to specified board (from pin itself)
  • [x] UI: Remove pin from board
  • [x] UI: Add to board while adding a pin.
• other
  • [x] UI: user login
  • [x] UI: logout
  • [x] UI: register

All basic features have done! More jobs required are listed below:

• For end users
  • [ ] docker autobuild
  • [ ] automatic config for new-installation
• CI
  • [x] frontend auto-build in docker
  • [x] migration files for new model
  • [x] nginx config
• Dev
  • [ ] 404 page?
  • [ ] 403 handler?
  • [x] Remove old codes
  • [x] bookmarklet remote test
  • [x] Browser Extension Link and Test(it works well).
• Doc
  • [ ] Dev how to
  • [ ] User's how to and upgrade guide

Hi,

I'd like to add a new way to organize our pins and ideas, for better sharing, better way to show your ideas.

Why

If we want to organize our pins, at first we give it tags, then we can access specified tag to get our previously saved pins.

If we want to share specified set of pins which includes pins about characters, scenes, models, with same style or some shared properties with many different tags (e.g "ideas to make act-game" maybe), it's hard for us to do that. As a result, I'd like to add a set-like concept to organize pins that way.

How

We can just add a "set"(named board or topic, anyway) in our Pinry system, we can add some pins to this "set", then share it to others.

For Django, it's a new model named "Topic" or "Board" which has many2many field targets to Pin.

Other feature Advices

• tag list: Maybe we need a page to show all of the tags and give links to each of them
• search: by tag or name, view by multiple tags (like pinterest)

What do you think about this feature? @overshard

related: #141

I have submit a patch to django's master branch to fix the RuntimeError while saving wepb file for djan

But, the patch will not be applied to Django 1.8, as a result I made a patch to upgrade django to 1.11 LTS.

• Upgrade Django to 1.11 LTS
• Integrates django-images into this project
• Use new permission interface instead of auth-backend (the old one has an issue in new version of tastypie that may cause permision error on Image object)
  • Pin-list is public by default
  • Only the pin owner can change its PinResource
• Upgrade Tastypie to lastest version

Ref: https://www.djangoproject.com/download/#supported-versions

Ref: https://github.com/django/django/pull/10331

Hi

Thanks for making Pinry.

I was hoping to run Pinry on Raspberry Pi but I could not find an ARM image on the docker hub. Do you plan to support ARM? If not, any suggestions for me?

Hi,

I don't know if is only a problem of mine, but when I create a pin from bookmarklet or via addon, I' not able to assign the correct board. I mean I select the board, but is always created "outside" any boards.

I'm using the docker version.

Thank you

The core social video sites for now since they both have easy embeddables. Need to grab a "screenshot" of the video, can be done via the API I think, to put as the pin thumbnail.

I am running the latest codebase as of 20/04/2020 in a docker containe.

According to https://docs.getpinry.com/passwords/ I should be able to navigate to an admin site.

Add watermark function for pinry. Modify the setting file to enble watermark. The default setting is False. Change it to True. You will get a watermarked pin after you upload.

Just curious if someone knows how to do this easily, aka what .css files and so on I'd need to edit for each thing.

• I'd like to remove Gravatar because it requires an account and no one uses it and in its place set a static 50x50px image
• Triple the size of thumbnails/image pins on boards
• Change the background color of the entire board to something much darker or some sort of pattern
• Increase the size of images/pins that have been clicked on to fill as much of the screen as possible (by height) but not have them scroll
• Allow a user to click on an image to view the full size immediately in new window
• Outright remove the Gravatar/"Pinned by user-x" bottom footer on each pin to save space
• Fully remove the Sign Up button so people can't upload stuff to my own server (instead of just disabling registration because currently disabling registration does not provoke any kind of "Registration disabled" message)

Are any of these features planned? It would be nice to have most of them in a user menu.

I have tried myself to find where the corresponding values and variables are for these functions but I cannot find them. I've been able to disable registrations via the settings.py file but not change thumbnail sizes or find where the background color/style setting is.

Any info would be appreciated. If someone can tell me how to change/set these features I'm happy to share/commit my own changes. Just having a hard time figuring out where everything is located.

I created a Pinry-bookmarklet compatible Chrome extension for those (like me) which prefer to hide the bookmark bar and have a simple icon to use. The package contains the "gray P on black background" from Pinry's website so I'm asking you if I can actually use it. Right now the extension is available on Chrome Store but hidden from searches and can only be tried by people who has the direct URL.

I wanted to check out the project after seeing it on https://alternativeto.net/ only to find the demo site https://pin.37soloist.com/ contains a lot of pornographic images uploaded by a user called alluded This isn't a good look!

We should add support for AVIF images (and maybe HEIF too? but I'll prioritize AVIF myself), such as this:

https://libre-software.net/image/avif-test/

I see two problems right now:

1. the bookmarklet doesn't detect it
2. if forced, the server fails on IntegrityError at /api/v2/pins/ NOT NULL constraint failed: django_images_image.height

Bumps decode-uri-component from 0.2.0 to 0.2.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps pillow from 9.1.1 to 9.3.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

When self-hosting multiple applications, you really want to have a single point for user management and authentication. It is annoying to login to each and every app seperately.

A pretty simple way to centralize authentication is achieved by deploying apps behind a reverse proxy, and use proxy auth. The proxy handles authentication in some way and sets http headers containing the username that was successfully logged-in. The apps read the headers and associate incoming requests to that user.

The perfect proxy auth feature for me would work like this:

1. Start the app with additional environment variables:

• containing the name of the initial admin user (e.g. admin=admin_user)
• enabling proxy auth (e.g. proxy_auth=true)
• setting the key of the http header that contains the username (e.g. auth_header=X-Authenticated-User)

2. Configure the reverse proxy to authenticate incoming requests in any way you like.
3. Let the reverse proxy set X-Authenticated-User to the authenticated username on every request.
4. The app treats the requests as if they belong to the appropriate user session.
5. Bonus: if the app does not know the username, it creates a new user with that name.

Other SSO methods like OIDC still require the user to login with each app, even it no credentials are required. It is still an additional step that is unneeded and hurting the user experience.

Additional context: I am using the app for this product. Since this is a single-user platform, users really should see no login screen at all, not even for SSO.