ホーム > Uncategorized > Public bookmarks 10/05/2013 (a.m.)

Public bookmarks 10/05/2013 (a.m.)


  • tags: aws ssl certificate

    • Submit the CSR to a Certificate Authority

      Your CSR contains information identifying you. To apply for a server certificate, send your  CSR to a certificate authority (CA). The CA might require other credentials or  proofs of identity.

      If the request for a certificate is successful, the CA returns an identity certificate  (and possibly a chain certificate) that is digitally signed.

      AWS does not recommend a specific CA. For a partial listing of available CAs, see Third-Party Certificate  Authorities.

  • tags: aws certificate

      • The decision to go with Bitbucket or Stash really depends on your preferences and needs around a few key points:

         

           
        • Locally hosted vs. Cloud hosted: Stash is installed in-house giving you the ability to control OS, database, etc.. This distinction also allows users to integrate with internal LDAP systems and create custom layers of security around their source. Bitbucket, on the other hand, is hosted by us in the cloud. This takes away the need to manage your server administration or purchase any extra hardware
        •  

        • Workflow Control: Although Bitbucket and Stash provide similar features around workflow and collaboration, Stash takes it to an extra level with its secure pull request functionality. This includes the ability to enforce pull request requirements, i.e. min. number of approvals or passing CI builds, before any code can be merged.
        •  

        • Extensibility: Both Bitbucket and Stash allow users to create custom git hooks, but Stash takes this further providing the ability to create custom add-on functionality. We’ve worked hard to create easy to use REST APIs so that Stash owners can customize the tool whichever way they see fit. To get an idea of the types of add-ons you can create see what’s already available in our Atlassian Marketplace.
        •  

         

        The best way to decide between the two is to give each of them a try. We offer free Bitbucket accounts for 1-5 users and free 30 day evaluation keys for Stash. We’re also here to help with any feature and functionality questions that may arise during your trials, feel free to email us any time at sales@atlassian.com.
      • Stash is still young product, it was publicly release in May 2012. The currently released version of Stash (1.3) compared to what is currently available on Bitbucket share the following notable features:

         

           
        • Code hosting and repository management for Git which includes 
             
          • HTTP smart protocol
          •  

          • SSH protocol
          •  

           

        •  

        • Pull requests within a repository between branches which includes 
             
          • Inline code commenting
          •  

          • General commenting
          •  

          • Approving pull requests
          •  

           

        •  

        • Code browsing via web interface 
             
          • Browser file tree on particular branch or tag
          •  

          • Commit history for repository or file
          •  

          • Viewing a changeset
          •  

           

        •  

        • Permissioning based on user and/or group membership
        •  

         

        There are bound to be more in common but these are the ones which come to mind. Bitbucket and Stash have clear distinct markets which they are targeting, small teams and larger organisations. This leads to many additional features to separate them. Also due to Bitbucket being an older product is does have more features which the Stash team has not yet had the time to implement.

         

        Some notable features unique to Bitbucket:

         

           
        • Graph in commits tab
        •  

        • Search in commits tab
        •  

        • Mercurial support
        •  

        • Deployment keys
        •  

        • Public repositories
        •  

        • Forks
        •  

        • Pull requests between forks
        •  

        • Team accounts
        •  

         

        Some notable features unique to Stash:

         

           
        • Crowd and LDAP integration
        •  

        • Multiple database support (MySQL, Postgres, Oracle and MS SQL)
        •  

        • In-app database migration
        •  

        • Deep extensibility for custom plugins
        •  

        • Notion of a project as a way to structure repositories
        •  

         

        Full disclosure, I’m a developer on the Stash team

    • It’s simply due to time and priorities. Code from Bitbucket cannot be transplanted into Stash as they are very different code bases (built in different languages on a different stack).

       

      It has nothing to do with marketing.

    • 1. What does a new Stash license cost?

       

      We believe the Stash licensing scheme is simple, upfront and equitable. Our software licenses entitle you to perpetual use, and include 12 months of maintenance (updates/support) commencing from the date of purchase. Renewing maintenance is entirely optional.

    • 2. How much is it to renew my Stash software maintenance?

       

      All non-free licenses come with 12 months of software maintenance (support and product updates). Beyond this initial 12 month period, you may renew your software maintenance for a further 12 months* at our discounted renewal prices.

    • Structured Projects

       

      Since Git teams rarely use just a single repository, Stash ties related repositories together into projects. Projects enable you to organize and manage repositories, making managing access to your repositories simple and straightforward.

  • tags: mongodb hosting nosql

  • bitbucket git pre commit hooks

    tags: git hook

      •                                                             

            
         

                   <!– Start restrictions section –>   <!– End restrictions section –>                          Skip to end of metadata 

          

           Go to start of metadata 

                  

           

        Bitbucket integrates with external services (hooks) through a set of brokers that run in response to certain events.  Brokers are Python scripts that receive information about an event and then take one or more actions. For example, there is a broker for sending emails, and another for posting the event to a given URL.  

        The Bitbucket team developed many of our brokers. Third-party vendors also develop brokers.  If a third-party vendor develop a broker, they must submit it to Bitbucket for approval. You can also develop and submit your own broker.

    • When you perform a push you will upload all the commits that the remote repository does not have yet, not necessarily a single commit.
      • It is true that git has a non-negligible learning curve, but with the right planning and access to the right documentation material the transition can be relatively fast and smooth. There are a huge number of resources online nowadays to speed up the knowledge acquisition of the team. Let me name a few that might come in handy:

         

      • Q: At what point in the software development do you delete a branch?

         

           
        • In git, once a feature branch has been merged all the information about that piece of development is preserved into the target branch: the merge commit records when the merge happened and all the individual change-sets of the body of work.

Posted from Diigo. The rest of my favorite links are here.

カテゴリー:Uncategorized
  1. まだコメントはありません。
  1. No trackbacks yet.

コメントを残す

以下に詳細を記入するか、アイコンをクリックしてログインしてください。

WordPress.com ロゴ

WordPress.com アカウントを使ってコメントしています。 ログアウト / 変更 )

Twitter 画像

Twitter アカウントを使ってコメントしています。 ログアウト / 変更 )

Facebook の写真

Facebook アカウントを使ってコメントしています。 ログアウト / 変更 )

Google+ フォト

Google+ アカウントを使ってコメントしています。 ログアウト / 変更 )

%s と連携中

%d人のブロガーが「いいね」をつけました。