CoastalCommits/CoastalCommitsPastes
CoastalCommits/CoastalCommitsPastes
2
1
Fork 0
forked from CoastalCommitsArchival/github.com-MaxLeiter-drift
Code Pull requests Activity Actions
CoastalCommits Pastes is a fork of Drift, a self-hostable Gist and paste service. Built with Next.js 13 and React Server Components. https://pastes.coastalcommits.com
69 commits 24 branches 0 tags 26 MiB
TypeScript 88.2%
CSS 9.2%
JavaScript 1.4%
Shell 0.8%
Dockerfile 0.4%
Find a file
Max Leiter 10c8b02397
Merge pull request #28 from boringContributor/auth-form 
refactor: improve the auth component
2022-03-13 17:40:10 -07:00
.github/ISSUE_TEMPLATE Add issue templates 2022-03-12 15:07:07 -08:00
client enhance auth workflow by adding a better error message and by validating the auth payload on server side 2022-03-13 20:57:55 +01:00
server enhance auth workflow by adding a better error message and by validating the auth payload on server side 2022-03-13 20:57:55 +01:00
CONTRIBUTING.md Create CONTRIBUTING.md 2022-03-12 19:45:25 -08:00
LICENSE Create LICENSE 2022-03-12 15:03:17 -08:00
README.md README: fix typo 2022-03-12 23:39:19 -08:00

README.md

Drift

Drift is a self-hostable Gist clone. It's also a major work-in-progress, but is (almost, no database yet) completely functional.

You can try a demo at https://drift.maxleiter.com. The demo is built on master but has no database, so files and accounts can be wiped at any time.

If you want to contribute, need support, or want to stay updated, you can join the IRC channel at #drift on irc.libera.chat or reach me on twitter. If you don't have an IRC client yet, you can use a webclient here.

Setup

Development

In both server and client, run yarn (if you need yarn, you can download it here.) You can run yarn dev in either / both folders to start the server and client with file watching / live reloading.

Production

Note: Drift is not yet ready for production usage and should not be used seriously until the database has been setup, which I'll get to when the server API is semi stable.

yarn build in both client/ and server/ will produce production code for the client and server respectively. The client and server each also have Dockerfiles which you can use with a docker-compose (an example compose will be provided in the near future).

If you're deploying the front-end to something like Vercel, you'll need to set the root folder to client/.

Current status

Drift is a major work in progress. Below is a (rough) list of completed and envisioned features. If you want to help address any of them, please let me know regardless of your experience and I'll be happy to assist.

  • creating and sharing private, public, unlisted posts
    • syntax highlighting (detected by file extension)
    • multiple files per post
    • uploading files via drag-and-drop
  • responsive UI
  • user auth
    • SSO via HTTP header (Issue: #11)
  • downloading files (individually and entire posts)
  • password protected posts
  • sqlite database (should be very easy to set-up; the ORM is just currently set to memory for ease of development)
  • non-node backend
  • administrator account / settings
  • docker-compose (PR: #13)
    • publish docker builds
  • user settings
  • works enough with JavaScript disabled
  • documentation
  • customizable homepage, so the demo can exist as-is but other instances can be built from the same source. Environment variable for the file contents?