summaryrefslogtreecommitdiff
path: root/app
AgeCommit message (Collapse)Author
2014-05-19store cert fingerprint with main user identityAzul
2014-05-19SmtpCertsController, routes and testsAzul
2014-05-19fix Email so User.new.valid? does not crashAzul
Email.new(nil) now returns an invalid email rather than crashing.
2014-05-19calculate cert fingerprints to store for leap_mxAzul
stelfox.net/blog/2014/04/calculating-rsa-key-fingerprints-in-ruby/
2014-05-15Merge pull request #161 from azul/bugfix/download-button-widerazul
make download button wide enough for helvetica #5039
2014-05-14check for presence of service_levelsAzul
This way the pricing link will not be shown for an empty hash. Which is easier to get into the config file than nil. And we can later verify the configuration to have a hash as the service_levels.
2014-05-14make download button wide enough for helvetica #5039Azul
2014-05-14Merge pull request #157 from azul/bugfix/5664-stop-email-autofillazul
Bugfix/5664 stop email autofill
2014-05-13move User Control Panel heading out of mastheadAzul
the masthead can only handle content of a limited width. Alternatively we could make the masthead title wider and add padding on the left so it still aligns nicely with the mask. However the wider we make it the worse it looks on small width displays. Another option would be to make the masthead contain multiple lines. However vertical aligment to the middle of 1 OR 2 lines of text is a real pain. So I went with a super simple masthead and the Caption goes below.
2014-05-13destinguish user.email from user.email_addressAzul
use the former if you want a working email account or nil, the latter if you want the email address associated with a given user no matter if the user actually has an email account or not.
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-05-09Merge pull request #156 from azul/bugfix/5548-hide-signup-forms-without-js0.5.1-rc2azul
hide srp forms when no js is available
2014-05-08minor fix to default pricing chartelijah
2014-05-06minor: fixing commentAzul
2014-05-06hide srp forms when no js is availableAzul
Hiding them using two mechanisms in case one fails: .hidden class - bootstrap hides them then style='display:none' - so they are hidden even if css load fails
2014-05-06Merge pull request #154 from azul/feature/display-pricingazul
adopt pricing view to current service_level format
2014-04-29adopt pricing view to current service_level formatAzul
2014-04-29remove os specific download buttonsAzul
keeping the platform detection for now.
2014-04-29smaller download button with context on dashAzul
To use bitmask services: Download Bitmask
2014-04-29simplify download buttonAzul
2014-04-25basic password validation without client side gemAzul
The client_side_validations gem is not maintained anymore and the validations were not working lately. So instead of trying to fix it I started working on independent validations for the password as it can't be validated on the server due to SRP. So far these validations are very primitive. They require 8 characters length and a matching confirmation.
2014-04-25ensure buttons are properly loading... and resetAzul
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-24cleanup homepage buttons someAzul
let's devide the partials rather than having super specific parameters (on_user_page)
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-18bringing back empty cert prefixesAzul
if neither limited nor unlimited certs are allowed there will be no prefix. Not sure if this is desired - but it's the way things used to be before the refactoring
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-10bringing back srp jsAzul
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-08moving users: app and test filesAzul
2014-04-08moving all of core into toplevel, tests fail.Azul
2014-02-04applied mcnair's changes to privacy policyelijah
2014-01-27fix js platform detection to match new way we have single link for linux ↵elijah
(not linux32 or linux64).
2014-01-23added a customizable 'bye' page for when a user leaveselijah
2014-01-23move #masthead out of main templates to make the masthead partials more ↵elijah
flexible.
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-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-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-20make sure overview link is active on Users#showAzul
2013-12-20enable billing engine by default, consolidate APP_CONFIG[:payments] and ↵elijah
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree]
2013-12-17Merge branch 'develop' into feature/billing-no-authenticated-paymentsjessib
Conflicts: billing/config/locales/en.yml
2013-12-13refactor: remove Overview controller - we can use Users#showAzul
we were only using Users#show to redirect to the edit action. So I replaced that with the overview and we have no more use for the extra controller. This also simplifies linking to the users in question a lot.