Hackaton Info

If you are attending a Hackaton, please read this page before getting started.

Crosser Cloud

During the Hackaton you should use devs.crosser.io at all times. The account to login will be provided to you during the start of the Hackaton. Whenever the documentation mention cloud.crosser.io that is equal to devs.crosser.io during the Hackaton.

EdgeNode Docker Image

When using crosser at a Hackaton you will not have to (and should not) login to the Crosser docker repository. Instead you will be using the public Crosser images from dockerhub. So when you use docker-compose to get the image you should just remove docker.crosser.io/ from the image configuration.

So this image: docker.crosser.io/crosser/edgenode:${EDGENODE_TAG:-latest} becomes image: crosser/edgenode:${EDGENODE_TAG:-latest}

Available Images

We provide both ARM and X64 images for you to use. Besides ARM/X64 options you can also choose between the standard image or the one with Python. The Python image will require more disk, but will allow you to deploy flows using the Python Bridge module

All available images are listed on dockerhub

Publishing Your Nuget Packages

As you will see in the documentation you will create a Nuget package for your module and then register it in the Crosser Cloud. When creating packages for production it is common to use nuget and you are free to do so, but we have created a community repository at myget.org.

Using the community repository have some advantages:

Much faster indexing, this means that you can register you new modules in the Crosser Cloud without a long wait (nuget has slower indexing).
Your modules can be deleted after the Hackaton (you will still have to source code if you want to publish to Nuget later on).

Basic commands for pushing to the community repository

Create Package

dotnet pack -c release

Push Package to Community Repository

dotnet nuget push path/to/package.0.0.1.nupkg -k 72d91cdc-e5f9-4b7a-9dd2-fe314d1b055e -s https://www.myget.org/F/crosser-community/api/v2/package