##// END OF EJS Templates
repositories: allow updating repository settings for users without store-in-root permissions...
repositories: allow updating repository settings for users without store-in-root permissions in case repository name didn't change. - when an user owns repository in root location, and isn't allow to create repositories in root before we failed to allow this user to update such repository settings due to this validation. We'll now check if name didn't change and in this case allow to update since this doesn't store any new data in root location.

File last commit:

r4330:d9a14621 default
r4415:fc1f6c1b default
Show More
repo_add_base.mako
169 lines | 6.8 KiB | application/x-mako | MakoHtmlLexer
templating: use .mako as extensions for template files.
r1282 ## -*- coding: utf-8 -*-
forms: unified usage of h.secure_form. Make sure we ALWAYS pass in...
r2105 ${h.secure_form(h.route_path('repo_create'), request=request)}
templating: use .mako as extensions for template files.
r1282 <div class="form">
<!-- fields -->
<div class="fields">
<div class="field">
<div class="label">
templates: UX, moved repo group select next to the name as it's very relavant to each other.
r3380 <label for="repo_name">${_('Repository name')}:</label>
templating: use .mako as extensions for template files.
r1282 </div>
<div class="input">
${h.text('repo_name', class_="medium")}
<div class="info-block">
dan
ui: fixed some missed icons during redesign phase
r3798 <a id="remote_clone_toggle" href="#">${_('Import Existing Repository ?')}</a>
templating: use .mako as extensions for template files.
r1282 </div>
%if not c.rhodecode_user.is_admin:
${h.hidden('user_created',True)}
%endif
</div>
</div>
<div id="remote_clone" class="field" style="display: none;">
<div class="label">
<label for="clone_uri">${_('Clone from')}:</label>
</div>
<div class="input">
${h.text('clone_uri', class_="medium")}
repository: added better instructions for importing repositories
r1598 <span class="help-block">
<pre>
- The repository must be accessible over http:// or https://
- For Git projects it's recommended appending .git to the end of clone url.
- Make sure to select proper repository type from the below selector before importing it.
- If your HTTP[S] repository is not publicly accessible,
add authentication information to the URL: https://username:password@server.company.com/repo-name.
- The Git LFS/Mercurial Largefiles objects will not be imported.
- For very large repositories, it's recommended to manually copy them into the
admin: ported settings controller to pyramid....
r2333 RhodeCode <a href="${h.route_path('admin_settings_vcs', _anchor='vcs-storage-options')}">storage location</a> and run <a href="${h.route_path('admin_settings_mapping')}">Remap and Rescan</a>.
repository: added better instructions for importing repositories
r1598 </pre>
</span>
templating: use .mako as extensions for template files.
r1282 </div>
</div>
<div class="field">
<div class="label">
templates: UX, moved repo group select next to the name as it's very relavant to each other.
r3380 <label for="repo_group">${_('Repository group')}:</label>
templating: use .mako as extensions for template files.
r1282 </div>
<div class="select">
${h.select('repo_group',request.GET.get('parent_group'),c.repo_groups,class_="medium")}
% if c.personal_repo_group:
<a class="btn" href="#" id="select_my_group" data-personal-group-id="${c.personal_repo_group.group_id}">
${_('Select my personal group (%(repo_group_name)s)') % {'repo_group_name': c.personal_repo_group.group_name}}
</a>
% endif
<span class="help-block">${_('Optionally select a group to put this repository into.')}</span>
</div>
</div>
repositories: preserve order of defined backends, and switched repo type selector to radios.
r4321
dan
repo: re-order creation/fork forms for better UX and consistency.
r2972 <div class="field">
<div class="label">
landing-rev: fixes #4102, use branches instead of landing tip refs by default....
r3881 <label for="repo_type">${_('Type')}:</label>
</div>
repositories: preserve order of defined backends, and switched repo type selector to radios.
r4321 <div class="fields repo-type-radio">
% for backend in c.backends:
% if loop.index == 0:
<input id="repo_type_${backend}" name="repo_type" type="radio" value="${backend}" checked="checked"/>
% else:
<input id="repo_type_${backend}" name="repo_type" type="radio" value="${backend}" />
% endif
<label for="repo_type_${backend}">
<i class="icon-${backend}" style="font-size: 16px"></i>
${backend.upper()}
</label>
% endfor
landing-rev: fixes #4102, use branches instead of landing tip refs by default....
r3881 <span class="help-block">${_('Set the type of repository to create.')}</span>
</div>
</div>
<div class="field">
<div class="label">
templates: UX, moved repo group select next to the name as it's very relavant to each other.
r3380 <label for="repo_description">${_('Description')}:</label>
</div>
<div class="textarea editor">
${h.textarea('repo_description',cols=23,rows=5,class_="medium")}
<% metatags_url = h.literal('''<a href="#metatagsShow" onclick="$('#meta-tags-desc').toggle();return false">meta-tags</a>''') %>
descriptions: show mention of metatags only if they are enabled.
r4241 <span class="help-block">
% if c.visual.stylify_metatags:
${_('Plain text format with {metatags} support.').format(metatags=metatags_url)|n}
% else:
${_('Plain text format.')}
% endif
${_('Add a README file for longer descriptions')}
</span>
templates: UX, moved repo group select next to the name as it's very relavant to each other.
r3380 <span id="meta-tags-desc" style="display: none">
<%namespace name="dt" file="/data_table/_dt_elements.mako"/>
${dt.metatags_help()}
</span>
</div>
</div>
templating: use .mako as extensions for template files.
r1282 <div id="copy_perms" class="field">
<div class="label label-checkbox">
<label for="repo_copy_permissions">${_('Copy Parent Group Permissions')}:</label>
</div>
<div class="checkboxes">
${h.checkbox('repo_copy_permissions', value="True", checked="checked")}
permissions: show user group count in permissions summary, and unified some text labels.
r3385 <span class="help-block">${_('Copy permissions from parent repository group.')}</span>
templating: use .mako as extensions for template files.
r1282 </div>
</div>
<div class="field">
<div class="label label-checkbox">
<label for="repo_private">${_('Private Repository')}:</label>
</div>
<div class="checkboxes">
${h.checkbox('repo_private',value="True")}
<span class="help-block">${_('Private repositories are only visible to people explicitly added as collaborators.')}</span>
</div>
</div>
<div class="buttons">
dan
templates: use explicit named actions like "create user" instead of generic "save" which is bad UX.
r4118 ${h.submit('save',_('Create Repository'),class_="btn")}
templating: use .mako as extensions for template files.
r1282 </div>
</div>
</div>
<script>
$(document).ready(function(){
var setCopyPermsOption = function(group_val){
if(group_val != "-1"){
$('#copy_perms').show()
}
else{
$('#copy_perms').hide();
}
};
$('#remote_clone_toggle').on('click', function(e){
$('#remote_clone').show();
e.preventDefault();
});
if($('#remote_clone input').hasClass('error')){
$('#remote_clone').show();
}
if($('#remote_clone input').val()){
$('#remote_clone').show();
}
$("#repo_group").select2({
'containerCssClass': "drop-menu",
'dropdownCssClass': "drop-menu-dropdown",
'dropdownAutoWidth': true,
'width': "resolve"
});
setCopyPermsOption($('#repo_group').val());
$("#repo_group").on("change", function(e) {
setCopyPermsOption(e.val)
});
$('#repo_name').focus();
$('#select_my_group').on('click', function(e){
e.preventDefault();
$("#repo_group").val($(this).data('personalGroupId')).trigger("change");
})
})
</script>
${h.end_form()}