02 May, 2016

1 commit


08 Apr, 2016

1 commit


06 Apr, 2016

1 commit


04 Apr, 2016

1 commit


29 Mar, 2016

1 commit


21 Mar, 2016

1 commit


15 Mar, 2016

1 commit


23 Feb, 2016

3 commits

  • Also rewriting the file visualization to work consistently with every
    file type. Here is the overall basic behavior now:
    
      * If the request is passed with view=true, content is displayed
        as an article content.
        * If the file has an inline visualization (like images) it's already
          displayed.
        * If not, a download link is displayed.
      * If the request is passed with view=false, the file is provided
        straight, without any noosfero layout being loaded.
    
      * If the file is private:
        * And the user accesses its public filesystem path, apache (this is
          done by noosfero-apache) will redirect the request to rails
          path so that the rails server will provide it considering
          appropriate permissions.
        * And the user accesses its rails path, rails server will provide as
          well.
      * If the file is public:
        * And the user accesses its public filesystem path, apache will
          provide the file.
        * And the user accesses its rails path, rails server will redirect
          to its public filesystem path so that apache provides the file.
    Rodrigo Souto
     
  • Rodrigo Souto
     
  • Rodrigo Souto
     

18 Feb, 2016

1 commit


28 Jan, 2016

1 commit


26 Jan, 2016

1 commit


21 Jan, 2016

1 commit


19 Jan, 2016

1 commit


18 Jan, 2016

6 commits


27 Nov, 2015

1 commit

  • Instead of stopping the service, running migrations etc (those take
    time), and then starting again, let's only restart the service after the
    uprada has already happened. Now that we are using unicorn, which
    supports restarting with dropping connections, with this we should have
    0 downtime upgrades.
    
    Also removed some unecessary buts deom debian/noosfero.prerm:
    
    - remove restarting of memcached, which is broken behavior as it could
      affect other services using memcached. Just set a namespace for our
      cache keys, and all caches will be automatically invalidated when the
      application is restarted after an upgrade with a new version number
    
    - remove removal of cache/*, since script/production already does that.
    
    NOTE: since this behavior change depends on changes to the prerm
    script, this won't take effect until the next upgrade _after_ the
    upgrade to first version including this change.
    Antonio Terceiro
     

16 Nov, 2015

1 commit


09 Nov, 2015

1 commit


06 Nov, 2015

1 commit


05 Nov, 2015

1 commit


04 Nov, 2015

1 commit


03 Nov, 2015

3 commits


30 Oct, 2015

1 commit


29 Oct, 2015

2 commits


09 Oct, 2015

1 commit


11 Sep, 2015

3 commits


09 Sep, 2015

1 commit


04 Sep, 2015

1 commit


07 Aug, 2015

1 commit