Forum App under dev
header Access-Control-Allow-Headers *
header Access-Control-Allow-Origin http://127.0.0.1:5173
# header Access-Control-Allow-Origin *
#!/bin/zsh
host=mnz
rsync -av --delete /f/svelte-forum $host:/srv/ --exclude={"*.db",".env","node_modules/*","build/*",".svelte-kit/*"}
ssh $host chown -R discourse:discourse /srv/svelte-forum
pnpm dev --port 4002
cd /srv/svelte-forum; pnpm i && pnpm run build && pnpm db:push && lsof -i :4002|tail -1|awk '{print $2}'|xargs kill; sleep 1; HOST=127.0.0.1 PORT=4002 node build
rsync -av --delete /f/svelte-5-ui-lib $host:/srv/ --exclude={"*.db",".env","node_modules/*","build/*",".svelte-kit/*"}
ssh $host chown -R discourse:discourse /srv/svelte-5-ui-lib
cd /srv/svelte-5-ui-lib; pnpm i && pnpm build && pnpm package
rsync -av --delete /f/svelte-lexical $host:/srv/ --exclude={"*.db",".env","node_modules/*","build/*",".svelte-kit/*"}
ssh $host chown -R discourse:discourse /srv/svelte-lexical
cd /srv/svelte-lexical; pnpm i; cd packages/svelte-lexical; pnpm build
sv restart unicorn
rails c
UserAuthToken.destroy_all
ApiKey.where(description: "user-api-key").destroy_all
server side sqlite exported as dbs
import { dbs } from '$lib/server/db';
browser side IndexDB exported as dbb, e.g.:
import { dbb } from '$lib/dbb';
import { browser } from '$app/environment';
let topic_posts = $state([]);
if (browser){
topic_posts= dbb.posts.where("topic_id").equals('xxx').toArray();
}
Discourse API docs: https://docs.discourse.org/
offline-first
[x] when user presses submit button, the post is tagged with random string as global ID, marked as not-synced and then sent together with the global ID, when the server returns OK, it is marked as synced. When composing using Discourse, a global ID is generated by the server so that all post has a global ID. Use rake to populate IDs for existing Discourse posts.
TODO: do we need to allow global_id when handling incoming post in discourse check: https://github.com/angusmcleod/discourse-events/commit/33ba86f66e22afaab30dd64eb0e51e45f17860c9#diff-040b0c3e0e3b0c377ccb9da72d51e1a9716135b8958e74aa81f104651972ee23R90 https://docs.discourse.org/#tag/Topics/operation/createTopicPostPM https://meta.discourse.org/t/are-custom-fields-on-posts-topics-available-via-the-api/49455/8
[ ] Draft is saved in browser IndexedDB periodically so that the latest draft can be recovered from browser crash or when user navigates to other page see also: https://svelte.dev/docs/kit/snapshots
[x] categories cached in browser, manual refresh in user settings
todo
[x] Load topic with very long posts, achieve infinite scroll implemented but has minor pitfalls:
when user has previously scrolled to bottom several times (let's say have fetched page 2, 3, 4), after a refresh, when scroll to bottom again, will start by fetching page 2 again.
Loading large amount of posts on homepage can be slow. Maybe we need pagination like a conventional forum and add new routes: /page/{i}
[x] When dark mode is toggled manually, it will cease after a full refresh.
[ ] RichTextComposer doesn't have a dark look
[ ] Preserve scroll positions when navigating back and forth between topic list and topic
- preserve topic position in list
- preserve post position in topic see also: https://svelte.dev/docs/kit/snapshots
[ ] In topic, when click reply button, the composer may be displayed outside of visible area, should scroll down a little bit, and focus on the composer.
[ ] Allow submitting the composer by [Ctrl+Enter]
[ ] use Timeline with topic/post list https://svelte-5-ui-lib.codewithshin.com/components/timeline
[ ] Darkmode toggle: add 'follow-system' option
