SQL to migrate the DB. Create migrations, migrate
`DELETE FROM django_content_type WHERE app_label='thoughts';`
`UPDATE django_content_type SET app_label='thoughts' WHERE app_label='main';`
`DROP TABLE thoughts_thought;`
`ALTER TABLE main_thought RENAME TO thoughts_thought;`
`DELETE FROM django_migrations WHERE app='main';`
Hopefully that's right, I'm not going to double check it or anything.
* Remove bleach and Markdown which were used for server-side markdown
* Update README with hypothetical self-hosting steps
* Remove install_xapian from version control (since I can't license it)
* Okay so we're not doing HTTP Basic Auth, that was an awful experience with those pop-ups.
* But we set the cookie with Django on the server-side, instead of needing JS
* So this should improve browser compatibility. No promises.
Maybe I should step away and keep my frustration inside and try to be a better person, a more reliable person. But I just. How do I fix this? What is the issue?
* Created a README
* Included instructions on how to apply the Inkscape patch, so that we can actually handle Thoughts of length
* Restyled the search results page
* Drastically decreased the line width
* Add vertical margin above the time stamp
* Change the Permalink button to Link
* Move the link button to the right of the timestamp
*
* I use it behind a reverse proxy. I would be suprised if *this* was the
only Gemini server someone was running. 1973 is the first prime after
1965.
* Remove unused important
* Add Secure Cookie option, in-line with Django recommendations
* Just removes the plaintext password from the source code, instead
reading it from an enviroment file. No password hashing here. No-JS
login is still on the timeline
- Titles on pages
- Time display is no longer awful
- Add favicon and apple-touch-icon
- Remove default django installed apps
- Make sure static directory is version controlled
Matthias Portzel
MatthiasSaihttam