##// END OF EJS Templates
fix(permissions): added a common way to update private flag via repo model...
fix(permissions): added a common way to update private flag via repo model - this allows to have a one and only one way to control the flag with the business logic shared - added test for that - changed view to use this method instead of DB update and custom permissions flush - fixed a case when update of repo settings didn't flush permissions actually while it should when private flag changed

File last commit:

r5137:f3cd5ebe default
r5551:5b9b5ed2 default
Show More
artifacts.mako
41 lines | 1.2 KiB | application/x-mako | MakoHtmlLexer
<%inherit file="/base/base.mako"/>
<%def name="title()">
${_('Artifacts Admin')}
%if c.rhodecode_name:
&middot; ${h.branding(c.rhodecode_name)}
%endif
</%def>
<%def name="breadcrumbs_links()"></%def>
<%def name="menu_bar_nav()">
${self.menu_items(active='admin')}
</%def>
<%def name="menu_bar_subnav()">
${self.admin_menu(active='artifacts')}
</%def>
<%def name="main()">
<div class="box">
<div class="panel panel-default">
<div class="panel-heading">
<h3 class="panel-title">${_('Artifacts Administration.')}</h3>
</div>
<div class="panel-body">
<h4>${_('This feature is available in RhodeCode EE edition only. Contact {sales_email} to obtain a trial license.').format(sales_email='<a href="mailto:sales@rhodecode.com">sales@rhodecode.com</a>')|n}</h4>
<p>
Artifacts are a binary file storage within RhodeCode that allows asset management next to version control system with fine-grained access control.
This functionality allows release builds or other types of binary asset to be stored and managed by RhodeCode.
</p>
</div>
</div>
</div>
</%def>