summaryrefslogtreecommitdiff
path: root/config
AgeCommit message (Collapse)Author
2014-05-26tickets: structure i18nAzul
2014-05-26Controller#flash_for instead of FlashResponderAzul
FlashResponder added a flash before responding. However at the point of responding objects have already been saved. So there is no way to test if they were changed. Now instead we can call flash_for resource before resource.save and it will add the flash messages only if the resource was actually changed.
2014-05-26FlashResponder will automagically add flash messagesAzul
2014-05-26Merge pull request #165 from azul/feature/cert-fingerprintsazul
Feature/cert fingerprints
2014-05-26change from GET to POST for certsAzul
We create them. let's reflect that in the verb.
2014-05-19SmtpCertsController, routes and testsAzul
2014-05-19little bit of documentationAzul
2014-05-19i18n for error pagesAzul
2014-05-19custom error pages for 404 and 500 errorsAzul
2014-05-13keep empty email field if user removed prefillAzul
We should respect the users choice. We can still get their email from the user id if we really need to.
2014-05-13allow for usernames with dotsAzul
preparing for #5664 with some test improvements i ran into this issue This commit includes a fix and the test improvements. In particular it adds BrowserIntegrationTest#login - so there is no need to go through the signup procedure everytime you want a user to be logged in.
2014-04-25use i18n keys for signup & login buttonsAzul
2014-04-25simple form: add wrapped and loading... buttons #5542Azul
the loading... text on the buttons was not capitalized before. So in order to change this in a (more or less) single place i added new button types to simple_form: button :wrapped - normal button, with loading and an optional cancel button wrapped in the classical bootstrap action div. cancel option contains the url to go to when canceling. button :loading - simple button with loading text capitalized by using i18n (simple_form.buttons.loading) Conflicts: engines/support/app/views/tickets/new.html.haml
2014-04-25Merge pull request #148 from azul/feature/api-quota-supportazul
Feature/api quota support + current_user null pattern
2014-04-25Merge pull request #151 from azul/bugfix/5549-prefer-client-signupazul
Bugfix/5549 prefer client signup
2014-04-24unified wording: destroy accountAzul
2014-04-24add signup and login info on the formsAzul
2014-04-18adopt service_level config to platform settingsAzul
cost -> rate quota -> storage
2014-04-18change service level configuration strategyAzul
The changes to the configuration required some non minor changes to the platform and also added some flexibility we don't require yet - and thus some new possibilities for errors. So instead we still use the allow_..._certs and ..._cert_prefix options. They basically provide the framework in which service levels can operate. The service level configuration will not include the cert prefix anymore. It only states if the service level is rate limited or not. This avoids conflicts between the two configuration options. I also removed the anonymous service level entirely. It was also turning a boolean decision (do we provide anonymous eip or not) into something way more complex. Instead I added the AnonymousServiceLevel class to handle the corner cases for people who are not logged in. Furthermore i renamed the UnauthenticatedUser to AnonymousUser so it matches the Anonymous Service Level nicely. It's also shorter and more intuitive.
2014-04-17make use of the UnauthorizedUserAzul
Null Pattern for current_user - use it to get rid of some conditionals
2014-04-17UnauthenticatedUser as current_userAzul
this still allows us to do current_user.service_level. Have not gone through the rest of the code yet. Only made sure logged_in? now tests for is_a? User instead of !!current_user
2014-04-17initial commit for the service level apiAzul
:api/service will return a hash of the current users service level This is failiing if the user is not logged in. Instead it should return the service description for an anonymous user.
2014-04-10move certs into toplevelAzul
cleaned up all the engine stuff that was never really used. Afterwards there is not that much left that makes it into the toplevel.
2014-04-08move users: config and libAzul
2014-04-08fix requiring core extensions - most tests passAzul
some message tests are failing for me right now.
2014-04-08moving all of core into toplevel, tests fail.Azul
2014-02-06for clarity, keep the empty folders for config/provider and ↵elijah
config/customizations in repo.
2014-01-23added a customizable 'bye' page for when a user leaveselijah
2014-01-23added a default footer with links to privacy policy, tos, pricing, about us, ↵elijah
contact.
2014-01-23added default pricing, privacy policy and tos pages.elijah
2014-01-19Redefine constant in a way that does not print out "warning: already ↵elijah
initialized constant VERIFY_PEER"
2014-01-16switch to using dl.bitmask.netelijah
2013-12-29Return 'provider.json' via a controller, to better be able to control the ↵elijah
response headers (in particular, 'X-Minimum-Client-Version'). It must now be placed in config/provider/provider.json
2013-12-24ensure permissions are preserved when copying customization files. closes #4623elijah
2013-12-22locale prefix support:elijah
* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path
2013-12-20fixed billing tests (added dummy billing hash to config, include required ↵elijah
testing gem phantomjs-binaries)
2013-12-20enable billing engine by default, consolidate APP_CONFIG[:payments] and ↵elijah
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree]
2013-12-16Merge pull request #122 from azul/bugfix/4703-disable-unsupported-settingsjessib
Bugfix/4703 disable unsupported settings
2013-12-13make the possible actions for users and admins configurableAzul
with tests
2013-12-13proceed even if the couch is unreachableAzul
* in case the user has a session id, keep it but proceed without a session * in case we can't initialize the models proceed * if APP_CONFIG[:reraise_errors] is set we'll crash instead in the latter case default to reraise errors in dev and test environments.
2013-12-05We won't want service levels in production mode, and have it so this initial ↵jessib
service level code won't break anything if it isn't set in the config.
2013-11-18Start of service level code, which will be tweakedjessib
* stores desired & effective service level * whenever desired level is changed, effective level will be updated * allows user to set their desired service level * allow admin to update desired & effective service level
2013-11-15fix problem with custom scss files and precompiling assets in production mode.elijah
2013-11-14ensure that we only copy files when running restarting the app, not every ↵elijah
time a rake task is run (especially since some rake tasks get run as root!)
2013-11-14added support for easier customizations via "config/customization" directoryelijah
2013-10-28Merge branch 'feature/4109-https-sources' into developAzul
2013-10-21use osx not mac as an identifier for the os.Azul
2013-10-21fix download urls for mac, android and windowsAzul
They did not point directly to the download.
2013-10-18use https sources in Gemfiles and also in the documentation (#4109)Azul
2013-10-18Make download links configurableAzul
This way we won't have to redeploy once the new links to the windows and the android version are there. Also this obviously offers more flexibility for providers.