Skip to content

Phoesion/Glow-Samples

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Phoesion Glow Sample

Introduction

This sample repository for Phoesion Glow, the complete micro-service development solution.

What is Phoesion Glow ?

Phoesion Glow is a set of tools and runtime with which your can create scalable cloud services.

Phoesion Glow is a complete solution for developing and managing your services, from libraries and tools in your IDE up to web servers, service bus and service hosts. All components have been created from scratch with the purpose of creating a uniform experience in both developing and managing your services

Structure

Each folder is a separate sample with an id and a name/description.
For example :

  • 1_REST is a sample that demonstrates the fundamentals and capabilities of writing REST services for your cloud
  • 2_Interop is a sample that demonstrates the fundamentals and capabilities of service-to-service
    (internal operation) within your cloud

Each sample has a readme.md file with quick sample-specific instructions of how to setup/test the sample, and a link to a full tutorial to the documentation site.

How to without Blaze installed (using containers)

  • Build the Sample_{SampleName}_.sln solution in the samples folder
  • Start the Reactor container using
docker run --name reactor -d -p 80:80 -p 443:443 -p 15000-15010:15000-15010 -p 16000:16000 phoesion/phoesion.glow.reactor-dev:1.0.9
  • Run the sample services projects from Visual Studio

How to run with Blaze installed

  • Build the Sample_{SampleName}_.sln solution in the samples folder
  • Run the sample services projects from Visual Studio.

How to test

After you deploy your glow project you can test it using the following paths (assuming local deployment) :

where MyService, MyModule, MyAction in the service/module/action you wish to test