476 Commits (6b6586f5d099a9089c8bf9dc7d7406a86c0a48eb)

Author	SHA1	Message	Date
Eugen Rochko	50ce347ef9	Bump version to 2.6.0 (#9149) ... * Bump version to 2.6.0 * Update CHANGELOG.md	6 years ago
Eugen Rochko	66019b0ec4	Bump version to 2.6.0rc4 (#9164) ... * Bump version to 2.6.0rc4 * Update CHANGELOG.md	6 years ago
Eugen Rochko	e84da282f6	Bump version to 2.6.0rc3 (#9142) ... * Bump version to 2.6.0rc3 * Update CHANGELOG.md	6 years ago
Eugen Rochko	6f78500d4f	Do not remove "dead" domains in tootctl accounts cull (#9108) ... Leave `tootctl accounts cull` to simply check removed accounts from live domains, and skip temporarily unavailable domains, while listing them in the final output for further action. Add `tootctl domains purge DOMAIN` to be able to purge a domain from that list manually	7 years ago
Sascha	b9d7021c1b	cli: set exit_on_failure for all CLI classes (#9094)	7 years ago
Eugen Rochko	2f0797bdbd	Bump version to 2.6.0rc2 (#9087) ... * Bump version to 2.6.0rc2 * Update CHANGELOG.md	7 years ago
Eugen Rochko	f5b8bd4392	Fix cull tripping on nil in last_webfingered_at (#9051) ... Fix #8741	7 years ago
Jeong Arm	2e18ad74dc	Fix tootctl cull on dead servers (#9041) ... * Delete first 9 accounts on dead servers * Clean up code by moving dead server culling to the end	7 years ago
Jeong Arm	68f0e4d54e	Handle if username is not found on tootctl feeds build (#9040)	7 years ago
Eugen Rochko	f468bfb830	Bump version to 2.6.0rc1 (#9025) ... * Bump version to 2.6.0rc1 * Update AUTHORS.md * Update CHANGELOG.md	7 years ago
Eugen Rochko	ef43f1d2ca	Bump version to 2.5.2 (#8960)	7 years ago
Eugen Rochko	e6c01171de	Bump version to 2.5.1 (#8953)	7 years ago
ashleyhull-versent	f194857ac9	rubocop issues - Cleaning up (#8912) ... * cleanup pass * undo mistakes * fixed. * revert	7 years ago
Eugen Rochko	186024a058	Add tootctl settings registrations open (#8829)	7 years ago
Eugen Rochko	ac07bfb018	Fix tootctl accounts reattaching not unsuspending deleted account (#8812)	7 years ago
Eugen Rochko	38f5f9cf5b	Add tootctl accounts backup (#8811)	7 years ago
Eugen Rochko	6a3f9b7e53	Move more tasks to tootctl (#8675) ... * Move more tasks to tootctl - tootctl feeds build - tootctl feeds clear - tootctl accounts refresh Clean up exit codes and help messages * Move user modifying to tootctl * Improve user modification through CLI, rename commands add -> create mod -> modify del -> delete To remove ambiguity * Fix code style issues * Fix not being able to unset admin/mod role	7 years ago
luzpaz	40dd19be37	Misc. typos (#8694) ... Found via `codespell -q 3 --skip="./app/javascript/mastodon/locales,./config/locales"`	7 years ago
Eugen Rochko	47ea318479	tootctl accounts [add|del|cull] (#8642) ... * CLI interface for creating/deleting local users - tootctl accounts add USERNAME - tootctl accounts del USERNAME * Add CLI interface for culling remote users that no longer exist - tootctl accounts cull	7 years ago
Eugen Rochko	b65a9b7243	Bump version to 2.5.0	7 years ago
Eugen Rochko	08721170da	Bump version to 2.5.0rc2	7 years ago
mayaeh	18eb565755	Add --verbose and --dry-run option to tootctl media remove (#8519) ... * Add --verbose and --dry-run options to CLI interface for removing remote media. * Fix coding style problem.	7 years ago
mayaeh	cc26fd71ac	Fix CLI interface for removing remote media (#8506) ... * Fix that can't delete media files even if "tootctl media remove" execute when "--background" not attached. * Revert This reverts commit 5aa7e09645. * Change to obtain and pass all columns when "--background" option is false.	7 years ago
Eugen Rochko	cabdbb7f9c	Add CLI task for rotating keys (#8466) ... * If an Update is signed with known key, skip re-following procedure Because it means the remote actor did *not* lose their database * Add CLI method for rotating keys bin/tootctl accounts rotate [USERNAME] Generates a new RSA key per account and sends out an Update activity signed with the old key. * Key rotation: Space out Update fan-outs every 5 minutes per 1000 accounts * Skip suspended accounts in key rotation	7 years ago
Eugen Rochko	b378b4c5c7	Add CLI interface for importing custom emoji (#8437) ... bin/tootctl emoji import PATH_TO_TAR Fix #8435	7 years ago
Eugen Rochko	793eea2982	Add improved CLI interface for removing remote media (#8411) ... ./bin/tootctl media remove --days 7 --background Make the old rake task point to it	7 years ago
Eugen Rochko	23752639b2	Bump version to 2.5.0rc1 (#8356)	7 years ago
Eugen Rochko	bb71538bb5	Redesign public profiles and toots (#8068)	7 years ago
Eugen Rochko	7ac5151b74	Bump version to 2.4.3	7 years ago
Eugen Rochko	89dc0c98ee	Bump version to 2.4.3rc3	7 years ago
Eugen Rochko	451e585b97	Bump version to 2.4.3rc2	7 years ago
Eugen Rochko	cb36ab9a10	Bump version to 2.4.3rc1	7 years ago
Eugen Rochko	d017f240f9	Bump version to 2.4.2	7 years ago
Eugen Rochko	86cce466b6	Bump version to 2.4.2rc3	7 years ago
Eugen Rochko	a04dca36a3	Bump version to 2.4.2rc2	7 years ago
Eugen Rochko	3b8023f9f9	Bump version to 2.4.2rc1	7 years ago
Eugen Rochko	0979d4275a	Bump version to 2.4.1	7 years ago
Eugen Rochko	35ae960122	Bump version to 2.4.1rc4	7 years ago
Eugen Rochko	158cd7ee74	Bump version to 2.4.1rc3	7 years ago
Eugen Rochko	fab65fb7e5	Bump version to 2.4.1rc2	7 years ago
Eugen Rochko	a29f196f95	Bump version to 2.4.1rc1	7 years ago
Eugen Rochko	7745a22ec7	Bump version to 2.4.0	7 years ago
Eugen Rochko	292c987522	Bump version to 2.4.0rc5	7 years ago
Eugen Rochko	bcbb6aa46f	Bump version to 2.4.0rc4	7 years ago
MIYAGI Hikaru	919eef3098	User agent for WebFinger (#7531) ... * User agent for WebFinger * local_domain → web_domain * 'http' is away accidentally...	7 years ago
Eugen Rochko	8756fd1e82	Bump version to 2.4.0rc3	7 years ago
Eugen Rochko	d75b63e4fb	Bump version to 2.4.0rc2	7 years ago
Eugen Rochko	50ed1e83ac	Bump version to 2.4.0rc1 (#7283)	7 years ago
ThibG	a24605961a	Fixes/do not override timestamps (#7336) ... * Revert "Fixes/do not override timestamps (#7331)" This reverts commit 581a5c9d29. * Document Snowflake ID corner-case a bit more Snowflake IDs are used for two purposes: making object identifiers harder to guess and ensuring they are in chronological order. For this reason, they are based on the `created_at` attribute of the object. Unfortunately, inserting items with older snowflakes IDs will break the assumption of consumers of the paging APIs that new items will always have a greater identifier than the last seen one. * Add `override_timestamps` virtual attribute to not correlate snowflake ID with created_at	7 years ago
Eugen Rochko	63553c6b5c	Add support for separate Redis for cache (#7272) ... * Add support for separate Redis for cache CACHE_REDIS_URL to allow using a different Redis server for cache purposes, with cache-specific configuration such as key eviction * Fix code style issues	7 years ago
Yamagishi Kazutoshi	084cf0babf	Add extract_foreign_key_action to Mastodon::MigrationHelpers (#7195)	7 years ago
Eugen Rochko	2a90da1837	Fix UniqueUsernameValidator comparison (#6926) ... Comparison was downcasing only one side, therefore if previously existing account had a non-lowercase spelling, it would be ignored when checking for duplicates. New rake task `mastodon:maintenance:find_duplicate_usernames` will help find constraint violations that might have occured from the presence of this bug. Bump version to 2.3.3	7 years ago
Eugen Rochko	6cc432bbc4	Bump version to 2.3.2	7 years ago
Eugen Rochko	dafae9818d	Bump version to 2.3.2rc5	7 years ago
Eugen Rochko	f64af6473f	Bump version to 2.3.2rc4	7 years ago
Eugen Rochko	74c39fada0	Bump version to 2.3.2rc3	7 years ago
Eugen Rochko	092f1df9d0	Bump version to 2.3.2rc2	7 years ago
Eugen Rochko	cdf8b92fea	Bump version to 2.3.2rc1	7 years ago
Eugen Rochko	2ef1ce1182	Bump version to 2.3.1	7 years ago
Eugen Rochko	79d3a8553f	Bump version to 2.3.1rc3	7 years ago
Eugen Rochko	f89ff65ec7	Bump version to 2.3.1rc2	7 years ago
Eugen Rochko	ab27dccba5	Bump version to 2.3.1rc1	7 years ago
Eugen Rochko	6e309f5e45	Bump version to 2.3.0	7 years ago
Eugen Rochko	bd077ad7d9	Bump version to 2.3.0rc3	7 years ago
Eugen Rochko	4ca60c665e	Bump version to 2.3.0rc2	7 years ago
Eugen Rochko	64f2ada5d4	Bump version to 2.3.0rc1	7 years ago
Eugen Rochko	e14c20582f	Bump version to 2.2.0	7 years ago
Eugen Rochko	97dcfb0f50	ASSET_HOST is wrong env variable. Fix to CDN_HOST (#6372)	7 years ago
Eugen Rochko	e6db3427b7	Bump to 2.2.0rc2	7 years ago
Eugen Rochko	b1daa71da5	Fix #6311: Replace relative URLs in CSS only for Premailer (#6335)	7 years ago
Eugen Rochko	0b7a0d15c7	Bump version to 2.2.0rc1	7 years ago
Eugen Rochko	872a0d5bd8	Improve HTML e-mails based on Litmus tests (#6301) ... * Use PNG images in HTML e-mails * Make webpack use URLs with host so fonts load inside HTML e-mails Convert this back to a relative URL in the premailer CSS loader since local requests are quicker * Improve responsive design * Add missing PNG icon	7 years ago
Eugen Rochko	5276c0a090	HTML e-mails for UserMailer (#6256) ... - premailer gem to turn CSS into inline styles automatically - rework UserMailer templates - reword UserMailer templates	7 years ago
Eugen Rochko	ff6ca8bdc6	Bump version to 2.1.3	7 years ago
Eugen Rochko	e9822a4e4e	Bump version to 2.1.2	7 years ago
Eugen Rochko	7571c37c99	Bump version to 2.1.1 (#6164)	7 years ago
Daigo 3 Dango	a434d9c0cc	Remove period from the version number (#6039) ... 2.1.0. -> 2.1.0	7 years ago
Eugen Rochko	a29432f0cd	Bump version to 2.1.0 🎆	7 years ago
Eugen Rochko	098c7d27fe	Bump version to 2.1.0rc6	7 years ago
Eugen Rochko	7cad926401	Bump version to 2.1.0rc5	7 years ago
Eugen Rochko	57fcc21a86	Bump version to 2.1.0rc4	7 years ago
Eugen Rochko	2526ef10c2	Bump version to 2.1.0rc3	7 years ago
Eugen Rochko	369f40bb9f	Bump version to 2.1.0rc2	7 years ago
Eugen Rochko	f9a0d8f2b9	Bump version to 2.1.0rc1 (#5834)	7 years ago
Yamagishi Kazutoshi	b21db9bbde	Using double splat operator (#5859)	7 years ago
ysksn	9dd5e329ab	Remove empty strings (#5732)	7 years ago
Eugen Rochko	3810d98cd8	Bump version to 2.0.0 🐘	8 years ago
Eugen Rochko	637ea3bb5b	Bump version to 2.0.0rc4	8 years ago
Eugen Rochko	bc89995f65	Bump version to 2.0.0rc3	8 years ago
aschmitz	e5d8166a12	Fix #5329 (#5332) ... This fixes #5329, which occurred when using MigrationHelpers on a table that Postgres estimated to be non-empty when it was actually empty.	8 years ago
Eugen Rochko	7c33da45f0	Bump version to 2.0.0rc2	8 years ago
Eugen Rochko	0aa810f9c8	Bump version to 2.0.0rc1 (#5209)	8 years ago
Eugen Rochko	0717d9b3e6	Set snowflake IDs for backdated statuses (#5260) ... - Rename Mastodon::TimestampIds into Mastodon::Snowflake for clarity - Skip for statuses coming from inbox, aka delivered in real-time - Skip for statuses that claim to be from the future	8 years ago
Eugen Rochko	eb5ac23434	Clean up code style of Mastodon::TimestampId module (#5232) ... * Clean up code style of Mastodon::TimestampId module * Update brakeman config	8 years ago
aschmitz	468523f4ad	Non-Serial ("Snowflake") IDs (#4801) ... * Use non-serial IDs This change makes a number of nontrivial tweaks to the data model in Mastodon: * All IDs are now 8 byte integers (rather than mixed 4- and 8-byte) * IDs are now assigned as: * Top 6 bytes: millisecond-resolution time from epoch * Bottom 2 bytes: serial (within the millisecond) sequence number * See /lib/tasks/db.rake's `define_timestamp_id` for details, but note that the purpose of these changes is to make it difficult to determine the number of objects in a table from the ID of any object. * The Redis sorted set used for the feed will have values used to look up toots, rather than scores. This is almost always the same as the existing behavior, except in the case of boosted toots. This change was made because Redis stores scores as double-precision floats, which cannot store the new ID format exactly. Note that this doesn't cause problems with sorting/pagination, because ZREVRANGEBYSCORE sorts lexicographically when scores are tied. (This will still cause sorting issues when the ID gains a new significant digit, but that's extraordinarily uncommon.) Note a couple of tradeoffs have been made in this commit: * lib/tasks/db.rake is used to enforce many/most column constraints, because this commit seems likely to take a while to bring upstream. Enforcing a post-migrate hook is an easier way to maintain the code in the interim. * Boosted toots will appear in the timeline as many times as they have been boosted. This is a tradeoff due to the way the feed is saved in Redis at the moment, but will be handled by a future commit. This would effectively close Mastodon's #1059, as it is a snowflake-like system of generating IDs. However, given how involved the changes were simply within Mastodon, it may have unexpected interactions with some clients, if they store IDs as doubles (or as 4-byte integers). This was a problem that Twitter ran into with their "snowflake" transition, particularly in JavaScript clients that treated IDs as JS integers, rather than strings. It therefore would be useful to test these changes at least in the web interface and popular clients before pushing them to all users. * Fix JavaScript interface with long IDs Somewhat predictably, the JS interface handled IDs as numbers, which in JS are IEEE double-precision floats. This loses some precision when working with numbers as large as those generated by the new ID scheme, so we instead handle them here as strings. This is relatively simple, and doesn't appear to have caused any problems, but should definitely be tested more thoroughly than the built-in tests. Several days of use appear to support this working properly. BREAKING CHANGE: The major(!) change here is that IDs are now returned as strings by the REST endpoints, rather than as integers. In practice, relatively few changes were required to make the existing JS UI work with this change, but it will likely hit API clients pretty hard: it's an entirely different type to consume. (The one API client I tested, Tusky, handles this with no problems, however.) Twitter ran into this issue when introducing Snowflake IDs, and decided to instead introduce an `id_str` field in JSON responses. I have opted to *not* do that, and instead force all IDs to 64-bit integers represented by strings in one go. (I believe Twitter exacerbated their problem by rolling out the changes three times: once for statuses, once for DMs, and once for user IDs, as well as by leaving an integer ID value in JSON. As they said, "If you’re using the `id` field with JSON in a Javascript-related language, there is a very high likelihood that the integers will be silently munged by Javascript interpreters. In most cases, this will result in behavior such as being unable to load or delete a specific direct message, because the ID you're sending to the API is different than the actual identifier associated with the message." [1]) However, given that this is a significant change for API users, alternatives or a transition time may be appropriate. 1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html * Restructure feed pushes/unpushes This was necessary because the previous behavior used Redis zset scores to identify statuses, but those are IEEE double-precision floats, so we can't actually use them to identify all 64-bit IDs. However, it leaves the code in a much better state for refactoring reblog handling / coalescing. Feed-management code has been consolidated in FeedManager, including: * BatchedRemoveStatusService no longer directly manipulates feed zsets * RemoveStatusService no longer directly manipulates feed zsets * PrecomputeFeedService has moved its logic to FeedManager#populate_feed (PrecomputeFeedService largely made lots of calls to FeedManager, but didn't follow the normal adding-to-feed process.) This has the effect of unifying all of the feed push/unpush logic in FeedManager, making it much more tractable to update it in the future. Due to some additional checks that must be made during, for example, batch status removals, some Redis pipelining has been removed. It does not appear that this should cause significantly increased load, but if necessary, some optimizations are possible in batch cases. These were omitted in the pursuit of simplicity, but a batch_push and batch_unpush would be possible in the future. Tests were added to verify that pushes happen under expected conditions, and to verify reblog behavior (both on pushing and unpushing). In the case of unpushing, this includes testing behavior that currently leads to confusion such as Mastodon's #2817, but this codifies that the behavior is currently expected. * Rubocop fixes I could swear I made these changes already, but I must have lost them somewhere along the line. * Address review comments This addresses the first two comments from review of this feature: https://github.com/tootsuite/mastodon/pull/4801#discussion_r139336735 https://github.com/tootsuite/mastodon/pull/4801#discussion_r139336931 This adds an optional argument to FeedManager#key, the subtype of feed key to generate. It also tests to ensure that FeedManager's settings are such that reblogs won't be tracked forever. * Hardcode IdToBigints migration columns This addresses a comment during review: https://github.com/tootsuite/mastodon/pull/4801#discussion_r139337452 This means we'll need to make sure that all _id columns going forward are bigints, but that should happen automatically in most cases. * Additional fixes for stringified IDs in JSON These should be the last two. These were identified using eslint to try to identify any plain casts to JavaScript numbers. (Some such casts are legitimate, but these were not.) Adding the following to .eslintrc.yml will identify casts to numbers: ~~~ no-restricted-syntax: - warn - selector: UnaryExpression[operator='+'] > :not(Literal) message: Avoid the use of unary + - selector: CallExpression[callee.name='Number'] message: Casting with Number() may coerce string IDs to numbers ~~~ The remaining three casts appear legitimate: two casts to array indices, one in a server to turn an environment variable into a number. * Only implement timestamp IDs for Status IDs Per discussion in #4801, this is only being merged in for Status IDs at this point. We do this in a migration, as there is no longer use for a post-migration hook. We keep the initialization of the timestamp_id function as a Rake task, as it is also needed after db:schema:load (as db/schema.rb doesn't store Postgres functions). * Change internal streaming payloads to stringified IDs as well This is equivalent to 591a9af356 from #5019, with an extra change for the addition to FeedManager#unpush. * Ensure we have a status_id_seq sequence Apparently this is not a given when specifying a custom ID function, so now we ensure it gets created. This uses the generic version of this function to more easily support adding additional tables with timestamp IDs in the future, although it would be possible to cut this down to a less generic version if necessary. It is only run during db:schema:load or the relevant migration, so the overhead is extraordinarily minimal. * Transition reblogs to new Redis format This provides a one-way migration to transition old Redis reblog entries into the new format, with a separate tracking entry for reblogs. It is not invertible because doing so could (if timestamp IDs are used) require a database query for each status in each users' feed, which is likely to be a significant toll on major instances. * Address review comments from @akihikodaki No functional changes. * Additional review changes * Heredoc cleanup * Run db:schema:load hooks for test in development This matches the behavior in Rails' ActiveRecord::Tasks::DatabaseTasks.each_current_configuration, which would otherwise break `rake db:setup` in development. It also moves some functionality out to a library, which will be a good place to put additional related functionality in the near future.	8 years ago
aschmitz	97c02c3389	Make IdsToBigints (mostly!) non-blocking (#5088) ... * Make IdsToBigints (mostly!) non-blocking This pulls in GitLab's MigrationHelpers, which include code to make column changes in ways that Postgres can do without locking. In general, this involves creating a new column, adding an index and any foreign keys as appropriate, adding a trigger to keep it populated alongside the old column, and then progressively copying data over to the new column, before removing the old column and replacing it with the new one. A few changes to GitLab's MigrationHelpers were necessary: * Some changes were made to remove dependencies on other GitLab code. * We explicitly wait for index creation before forging ahead on column replacements. * We use different temporary column names, to avoid running into index name length limits. * We rename the generated indices back to what they "should" be after replacing columns. * We rename the generated foreign keys to use the new column names when we had to create them. (This allows the migration to be rolled back without incident.) # Big Scary Warning There are two things here that may trip up large instances: 1. The change for tables' "id" columns is not concurrent. In particular, the stream_entries table may be big, and does not concurrently migrate its id column. (On the other hand, x_id type columns are all concurrent.) 2. This migration will take a long time to run, *but it should not lock tables during that time* (with the exception of the "id" columns as described above). That means this should probably be run in `screen` or some other session that can be run for a long time. Notably, the migration will take *longer* than it would without these changes, but the website will still be responsive during that time. These changes were tested on a relatively large statuses table (256k entries), and the service remained responsive during the migration. Migrations both forward and backward were tested. * Rubocop fixes * MigrationHelpers: Support ID columns in some cases This doesn't work in cases where the ID column is referred to as a foreign key by another table. * MigrationHelpers: support foreign keys for ID cols Note that this does not yet support foreign keys on non-primary-key columns, but Mastodon also doesn't yet have any that we've needed to migrate. This means we can perform fully "concurrent" migrations to change ID column types, and the IdsToBigints migration can happen with effectively no downtime. (A few operations require a transaction, such as renaming columns or deleting them, but these transactions should not block for noticeable amounts of time.) The algorithm for generating foreign key names has changed with this, and therefore all of those changed in schema.rb. * Provide status, allow for interruptions The MigrationHelpers now allow restarting the rename of a column if it was interrupted, by removing the old "new column" and re-starting the process. Along with this, they now provide status updates on the changes which are happening, as well as indications about when the changes can be safely interrupted (when there are at least 10 seconds estimated to be left before copying data is complete). The IdsToBigints migration now also sorts the columns it migrates by size, starting with the largest tables. This should provide administrators a worst-case scenario estimate for the length of migrations: each successive change will get faster, giving admins a chance to abort early on if they need to run the migration later. The idea is that this does not force them to try to time interruptions between smaller migrations. * Fix column sorting in IdsToBigints Not a significant change, but it impacts the order of columns in the database and db/schema.rb. * Actually pause before IdsToBigints	8 years ago
Eugen Rochko	efec507230	Bump to 1.6.1	8 years ago
abcang	1aad015bbb	Revert unique retry job (#4937) ... * Revert "Enable UniqueRetryJobMiddleware even when called from sidekiq worker (#4836)" This reverts commit 6859d4c028. * Revert "Do not execute the job with the same arguments as the retry job (#4814)" This reverts commit be7ffa2d75.	8 years ago
Eugen Rochko	ab71cf4593	Bump to 1.6.0	8 years ago
Eugen Rochko	4819e2913d	Bump version to 1.6.0rc5	8 years ago
Eugen Rochko	2ff7146b6d	Bump version to 1.6.0rc4	8 years ago
Eugen Rochko	dd5cb5085c	Bump version to 1.6.0rc2	8 years ago
abcang	be7ffa2d75	Do not execute the job with the same arguments as the retry job (#4814)	8 years ago
Eugen Rochko	9dd8dff683	Bump version to 1.6.0rc1 (#4768)	8 years ago
Daigo 3 Dango	696c2c6f2f	Add Mastodon::Source.url (#4643) ... * Add Mastodon::Source.url * Update spec * Refactor Move things frmo Mastodon::Source to Mastodon::Version	8 years ago
Eugen Rochko	41c3389d76	Bump to 1.5.1	8 years ago
Eugen Rochko	559fd08845	Bump to 1.5.0	8 years ago
Eugen Rochko	9b247c3d88	Bump to 1.5.0rc3	8 years ago
Eugen Rochko	fdb65dcbee	Bump to 1.5.0rc2	8 years ago
Eugen Rochko	a549d1ae6b	Bump to 1.5.0rc1 (#4318)	8 years ago
Eugen Rochko	b6a19e7b89	Bump version to 1.4.7	8 years ago
Eugen Rochko	7b13e6efc2	Bump version to 1.4.6	8 years ago
Eugen Rochko	1585b0c6cc	Bump version to 1.4.4	8 years ago
Eugen Rochko	947887f261	Bump version to 1.4.3	8 years ago
Eugen Rochko	380b20eed6	Bump version to 1.4.2	8 years ago
Eugen Rochko	8963f8c3c2	Bump version to 1.4.1	8 years ago
Eugen Rochko	7b23f79d41	Bump version to 1.4.0.6	8 years ago
Eugen Rochko	e0e12b0fee	Bump version to 1.4.0.5	8 years ago
Eugen Rochko	2d97c898f2	Bump version to 1.4.0.4	8 years ago
Eugen Rochko	b51398d0dd	Bump version	8 years ago
Clworld	df92f010ad	Set config.cache_store in environments file. (#3219) ... * Set config.cache_store in application.rb * Set config.cache_store in environments. * fix code format.	8 years ago
Eugen Rochko	756db8103a	Bump version to 1.4.0.2 (#3190)	8 years ago
Eugen Rochko	01e011bc90	Bump version to 1.3.2 (#2623)	8 years ago
Ash Furrow	5eef9dab80	Update version to 1.3.1 (#2571)	8 years ago
Eugen Rochko	b48c9013aa	Bump version, improve how version is stored for better commit history (#2526)	8 years ago
Ash Furrow	a0ed88a99b	Adds version to about/more and API (#2181) ... * Adds version. * Cleans up code. * Removes standalone endpoint and adds version to instance endpoint. * Addresses feedback from #2181.	8 years ago