A selfhosted image and video uploading platform that uses Next.js and PocketBase. An open-source alternative to Imgur.
More screenshots can be found in the screenshots directory.
Share Me can be deployed to your own infrastructure with Docker. For more information see Deployment.
Once the initial setup is complete, head to the URL of your Share Me instance. You will be redirected to /login if you aren't logged in yet. Alternatively, you can create an account under /sign-up.
To create posts simply go back to the homepage after logging in, and
Use the sample docker-compose.yml
to deploy your Share Me instance. This will deploy a PocketBase server at port :8080
and the Next.js frontend to :3000
.
You can set the PocketBase server URL with host:port
in the POCKETBASE_URL
environment variable or a hostname if deployed with a reverse proxy.
If you have a reverse proxy such as Traefik or Apache, you can expose the application under /
and the PocketBase API under /api/
as well as the admin UI under /_/
. This will be the optimal setup for production. The POCKETBASE_URL
should be set to https://shareme.example.com
.
Share Me supports Umami tracking scripts, in case you want analytics for your Share Me instance.
To add the tracking script, set the two following environment variables:
UMAMI_WEBSITE_ID=<umami-website-id>
UMAMI_JS=<umami-js>
S3 can be configured in PocketBase under Settings > Files storage. You can enable S3 and provide AWS S3 configurations or an S3-compatible API such as MinIO or DigitalOcean Spaces.
SMTP is used by Share Me for email verification (WIP). To configure a mail server head to Settings > Mail settings and configure your SMTP server.
The default file size limit is about 5MB and can be changed in the PocketBase UI. Head to Collections > files > Settings (cog icon) and edit the file
column settings. Set the Max file size to whatever you want.
Share Me loads the configured PocketBase authentication providers. Head to your PocketBase admin dashboard, go to Settings > Auth providers and configure the ones you want to use.
To disable username/password and email/password login if you only want to allow access via SSO, go to Collections > users > Settings (cog icon) > Options and disable/enable the methods you want.
If you only want to disable sign-up, remove the "create" API rules to only allow admins to create new users. You can set the SIGNUP_ENABLED
environment variable in the frontend to disable the sign-up page and remove links to it.
🚧 WIP
This project is licensed under MIT.