Giter Site home page Giter Site logo

vijayraavi / sitecore.ship Goto Github PK

View Code? Open in Web Editor NEW

This project forked from kevinobee/sitecore.ship

0.0 0.0 0.0 6.03 MB

Ship provides a CI service layer for Sitecore

License: MIT License

API Blueprint 6.38% Batchfile 0.31% C# 91.51% Smalltalk 0.36% HTML 1.44%

sitecore.ship's Introduction

Sitecore.Ship

Join the chat at https://gitter.im/kevinobee/Sitecore.Ship

Sitecore.Ship is a lightweight means to install Sitecore Update packages via HTTP requests.

API Documentation

The Sitecore.Ship documentation can be found on Apiary.io

Instructions for Use

The latest release versions of the Sitecore.Ship packages can be found in the NuGet package gallery

Early releases of the Sitecore.Ship packages can be found on a public feed from MyGet

Installing Sitecore.Ship via NuGet

Ensure that the website project is set to run with .NET Framework 4.5

Ensure that the web.config file for the target project if already existing is included into your project.

Run the following powershell command in the package manager console of the Visual Studio solution for the target website:

PM:> install-package Sitecore.Ship

or

PM:> install-package Sitecore.Ship.AspNet

Installing the package will do the following:

  • Add a new packageInstallation section to your web.config file. You can set configuration options in this section to enable remote access to the installer and to enable the package streaming functionality. These options are safe by default, that is, no remote access and package streaming disabled. Note: the configuration settings are ignored in this branch of Sitecore.Ship.

  • Register a single new HTTP handler section in <system.webserver>. Support for classic mode in IIS has been removed.

  • Add a ship.config Sitecore include file to the App_Config\include folder.

Configuration Options

Shown below is a fully specified configuration section for Sitecore.Ship:

<packageInstallation enabled="true" allowRemote="true" allowPackageStreaming="true" recordInstallationHistory="true">
  <Whitelist>
    <add name="local loopback" IP="127.0.01" />
    <add name="Allowed machine 1" IP="10.20.3.4" />
    <add name="Allowed machine 2" IP="10.40.4.5" />
  </Whitelist>
</packageInstallation>

Default configuration:

  • enabled = false
  • allowRemote = false
  • allowPackageStreaming = false
  • recordInstallationHistory = false
  • IP address whitelisting is disabled if no elements are specified below the <Whitelist> element or if the element is omited.

When recordInstallationHistory has been set to true packages should follow the naming conventions set out below:

Packages should follow the following naming conventions. Id should be an int.

{ID}-DescriptiveName.{Extension}

where:

  • ID should be an integer
  • Extension should be either update or zip

For example:

01-AboutPage.update

02-HomePage.zip

Uninstalling Sitecore.Ship

Run the following commands:

PM:> uninstall-package Sitecore.Ship

Working with the Sitecore.Ship Source Code

  • Clone this repository to your local file system

  • You will need to specify the location of your Sitecore assemblies. This can be down in the build\build.proj file. Set the LibsSrcPath to where your Sitecore assemblies are located.

  • From a command prompt type .\build and press Enter

A successful command line build will generate a NuGet package in the artifacts\Packages\ folder.

Tools

  • POSTMAN is a powerful HTTP client that runs as a Chrome browser extension and greatly helps with testing test REST web services.

References:

Contributing to the Project

If you are interested in contributing to the growth and development of Sitecore.Ship in even a small way, please read the notes below.

The project can be built and tested from the command line by entering:

.\build

Please ensure that there are no compilation or test failures and no code analysis warnings are being reported.

Running the Smoke Tests

The build.proj file contains a set of smoke tests to verify that the Sitecore.Ship features all run successfully when the package has been installed in a Sitecore website.

In order to run these smoke tests you will need to:

  • Have a local install of Sitecore.

  • Set the TestWebsitePath and TestWebsiteUrl in the build\environment.props to reference the local Sitecore website.

  • Ensure that the test website has the Ship package installed by running the following in the Package Manager Console:

    install-package Sitecore.Ship -Source <path to folder containing your sitecore.ship nupkg file>

You can then run the smoke tests by entering:

.\build RunSmokeTests

A series of curl commands fire off HTTP requests to the Sitecore.Ship service routes and the results are printed out to the console. Each of these commands should execute successfully before you send a pull request back to the main project.

Your participation in the project is very much welcomed.

sitecore.ship's People

Contributors

kevinobee avatar leethomascook avatar leecook avatar pveller avatar cturano avatar mikeedwards83 avatar retohugi avatar gitter-badger avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.