| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Update Administration-guide.md
|
|
Update Heroku-guide.md
|
|
Add HackerNewsBot
|
|
I have created a bot that will post Hacker News stories with 100+ points. Adding it to the list.
|
|
the syntax for running the rake task wasn't correct.
|
|
Email service options :P
|
|
Fix npm/yarn cache cleaning
|
|
Cleaning up the heroku admin command bit to match the form used in Administration-guide.md and clarify the wording a bit.
|
|
Removing some of the confusion around what format S3 bucket names and regions should be entered as well as providing an example of an S3 policy that follows best security practices for this sort of thing.
|
|
change suggested cipher for nginx
|
|
|
|
Update heroku instructions
|
|
Add specs for PostStatusService
|
|
DRY up reblog vs original status check
|
|
typo
|
|
Implement pending specs on Status
|
|
Implement the two pending specs on `Status`: `reblogs_count` and
`favourites_count`.
|
|
|
|
|
|
These are currently user facing errors, but are not localized. This adds the
ability for these messages to be localized.
|
|
This implements all pending specs, and adds additional coverage for the
following functionality:
* Normal status creation
* Creating a reply status
* Creating a sensitive status
* Creating a status with spoiler text
* A status with no spoiler text gets an empty string for spoiler text
* Creating a status with custom visibility
* Creating a status for an application
* Processing mentions
* Processing Hashtags
* Pinging PuSH hubs
* Crawling links
* Attaching media
|
|
Checking reblog vs original status was happening in multiple places
across the app. For views, this logic was encapsulated in a helper
method named `proper_status` but in the other layers of the app, the
logic was duplicated.
Because the logic is used at all layers of the app, we extracted it into
a `Status#proper` method on the model and changed all uses of the logic
to use this method. There is now a single source of truth for this
condition.
We added test coverage to untested methods that got refactored.
|
|
There are currently not specs for the two media validations that are performed
by `PostStatusService`. This adds specs for the validations that ensure that you
cannot attach more than four files, and that a status cannot have both image and
video attachments.
|
|
|
|
|
|
Fix nil#object_type error
|
|
Allow setting of default language through config
|
|
|
|
|
|
|
|
|
|
Setting of locale in controller extracted to Localized concern,
the doorkeeper authorized applications controller moved under
custom namespace with inclusion of Localized, which resolves the
"it sometimes appears in a different random language" bug
|
|
|
|
|
|
(#1124)
* Rewrite Atom generation from stream entries to use Ox instead of Nokogiri::Builder
StreamEntry is now limited to only statuses, which allows some optimization. Removed
extra queries on AccountsController#show. AtomSerializer instead of AtomBuilderHelper
used in AccountsController#show, StreamEntriesController#show, StreamEntryRenderer
and PubSubHubbub::DistributionWorker
PubSubHubbub::DistributionWorker moves n+1 DomainBlock query to PubSubHubbub::DeliveryWorker
instead.
All Salmon slaps that aren't based on StreamEntry still use AtomBuilderHelper and Nokogiri
* All Salmon slaps now use Ox instead of Nokogiri. No touch from status on account
|
|
Small addition in case people want email service options, sparkpost.com gives you 100k/mo free
|
|
|
|
Reduce size of background-photo.jpeg
|
|
Add a couple of network performance tweaks to Vagrantfile.
|
|
|
|
Reduced by running through `guetzli` image optimizer.
|
|
Add metadata to Dockerfile
|
|
|
|
|
|
Optimize Dockerfile
|
|
Cosmetic changes to the scalingo deployment
|
|
Updates slugignore
|
|
Linux users must enable NFS for Vagrant
|
|
|
