Jump to content

SWSBB

Members
  • Content Count

    38
  • Joined

  • Last visited

  • Days Won

    1

SWSBB last won the day on December 19 2012

SWSBB had the most liked content!

Community Reputation

1 Neutral

About SWSBB

  • Rank
    Advanced Member

Recent Profile Visitors

2,558 profile views
  1. @gweronimo totaly agree πŸ˜ƒ
  2. Ok. I just had another go on this and managed to get it running πŸ˜ƒ Make sure you have IIS10 + AAR + Url Rewrite 1. Make sure you disable "Reverse rewrite host in respose headers" in "Application Request Routing Cache" -> "Server Proxy Settings..." (Server setting!!) 2. Create a new WebSite (if not already done) 3. Add a new application to the site (in my case the application is called 'plastic') 4. copy the attached web.config to the root folder of the web application 5. change all rules to the servernames and ports you are using [PLASTICSERVER] is the name of the server that runs plastic scm. [WEBSERVER] is the name of the web server. Can be the same, but don't have to. DONE ❀️ web.config
  3. I'm sorry. I'm in Japan right now with a lot of time difference and no stable internet connection. But please go ahead and discuss this with the other guys
  4. Same problem here. I added rules for redirect and stuff but still can't get it to load the AJAX content after the login. Maybe Codice could supply an official doc for IIS setup like this one for nginx: http://blog.plasticscm.com/2018/09/nginx-to-add-ssl-to-webadmin-and-webui.html
  5. @psantosl I'm fine with a custom branch weight attribute. We use a lot attributes already to filter the branches and stuff. We can also implement our own rules this way, as they are all the same for everybody. But I think there will be users that have different needs. Then fix branch weights might not be good enough. I thought of 'conditional weights'. Just like conditional colors. Maybe add a multiplyer for branch hierachy level and a reference for the parent branch weight. Then allow it to be a formular like: ([ParentWeight]*10)+1. Make sure that the basic operators (+-*/%) are supported. (I know this is tricky, as the parent branch doesn't have to be in the diagramm, but you still would need to calculate the weight for it. Maybe use promises, to only calculate it when needed?) This should open the door for any custom layout. I also like the bounding boxes suggested by @gweronimo. But in our case this will not work. As I descriped in the user voice linked above: We order the branches in the branch explorer to mirror the release pipeline. So at the top are hotfix-branches, then releases and the release-candidate, then main (Trunk in our case) and then all the issues and features. This is our main repo. But there are other repos, where the bounding boxes would make a lot more sense. You already moved the branch explorer config to the workspace. So the boxing sould be a layout option and then it's fineπŸ˜ƒ I think you wouldn't even need an extra boxing algorithm if there was one more reference for the conditional weight formular: IndexOfChildBranch. Then a formular like this would handle the boxing: ([ParentWeight]*100)+[IndexOfChildBranch]. The newest child branch should have the Index 1 and older branches get a heigher index. Then the boxing would be handled by just that What do you think?
  6. This is good news πŸ˜ƒ Made my day. Thanks
  7. I really appreciate that you work on this! 😁 Does the manual relayout still work with the dynamic branch layouting? Because I really like to have a ordered structure on my branch explorer. This and branch colors help me to find the correct branch really fast! I'll try the new dynamic branch layout. But I think it will still be too 'unorganized' for me. I posted this user voice some time ago, suggesting a custom rule set for branch weights: https://plasticscm.uservoice.com/forums/15467-general/suggestions/18561949-add-a-branch-weight-for-layouting-in-branch-explor You could integrate the dynamic layout into this system as well ;) Just add rules for hierarchy level, recent activity and live span.
×
×
  • Create New...