Is Omelette.Cloud reliable?

Omelette.Cloud is a hobby project for now, and supported by one person.

What third-party services are being used?

Omelette.Cloud uses the following providers:

Alexander Bich, working at Kavykhi, founded in Karaganda, Kazakhstan.

Metadata is always stored in the EU datacenter. At the moment artifact data is also stored in EU datacenter. It is planned to offer a choice to store artifact data in other regions.


What is organization?

Organization should usually correspond to your company or team. Access controls and billing are set up by organization admin. Currently all members of an organization have access to all projects created within it.

How organization is billed?

You can select billing plan per organization. Billing plan defines resource limits available for organization (such as number of projects and storage limits). While the platform is in early access there is only free plan. Paid plans with bigger limits will be introduced in the future.

How many organizations I can create or join?

You can be an admin of at most one organization on a free plan. You can join any number of organizations as a regular member (not admin). You will be able to manage any number of organizations on paid plans when such plans are introduced.


What is project?

Project usually corresponds to a program, game or any other digital package.


What is branch?

Branch is a sequence of versions released for a project. Usually there is a main branch for released versions, plus some number of pre-release branches.

How should I name a branch?

Branch naming is completely up to you. Some usual codenames for release branches are main, release, stable. Non-release branches may be named alpha, beta, unstable.


What is version?

Version represents one specific state of your project at some time.


What is channel?

Channel corresponds to a type of artifacts which can be attached to versions. Users can choose what channels they want to install from the branch they selected. For software project channels often created per-platform, for example windows, linux, macos channels, so users can download only the executables for their target platform.


What is artifact?

What files I should not upload?

Usually you should not upload development files, such as:

  • source code files (*.cpp, *.h, *.py, ...)
  • version control files and folders (.git, .svn, ...)
  • intermediate build artifacts (*.obj, *.lib, ...)
  • hidden system files (Thumbs.db, ...)

Generally it is recommended to automate preparing your software build by creating a script copying only necessary files into a folder outside of your development folder - this way you can make sure you will not be including unnecessary files into your release.

What limitations the web uploader has?

For security purposes browsers limit functionality available for web applications. Additionally, some browsers implement various web standards partially or incorrectly. Due to this, the web uploader has the following limitations:

  • Empty directories are not detected, even when explicitly selected in the file choosing dialog.
  • The executable permission bit is not accessible for files on Linux and macOS. This is not an issue on Windows, because Windows does not use or have executable permissions for files.
  • "Hidden" file attribute on Windows cannot be detected.

The Omelette.Cloud local app does not suffer from these limitations.

Publishing versions

What publishing version means?

Publishing version means making it current for one or more branches. Users with access to those branches can access the version.


What roles are available for users?

Here is the list of user roles, in order from more to less powerful.

  • Maintainer - manager of organization. Only maintainer can:
    • create/delete projects
    • manage members of organization
  • Developer can:
    • create/edit/delete branches, channels, versions
    • upload/delete artifacts
    • publish versions to branches
  • Player can:
    • list branches, channels
    • see version history of all branches
    • download artifacts from any version of any branch

What about owner of organization?

Each organization has exactly one owner. An owner can pass ownership over organization to another user if desired. Only owner can set billing plan and billing method for an organization.

Note that owner of organization is not a role - it is a separate status. When organization is created, owner is automatically added into it with maintainer role, so they can create projects and approve other users from the start. But if the owner is a managerial or financial type of a person and does not participate in actual development, it may make sense to "remove" the owner from the organization (that is, remove their role). Owner who does not have a role in organization is still an owner and sets up billing, but they cannot manage users or projects. Such an owner is not counted as an active user against billing plan's user limit - use it to your advantage. Owner can always reinstate themselves in any role, so they will not lose control over organization.

Is it possible to allow non-authenticated (public) access?

Not at this time. All users must be explicitly authorized to access anything.