cloud-computer / cloud-computer Goto Github PK

Description

This is a #hacktoberfest challenge. Submit 4 PRs with your work and get a hacktoberfest t-shirt!

Currently the cloud computer supports 3 remote application delivery technologies: native web apps, VNC, and GTK broadway.

Adding support for greenfield would allow any Linux application to be remotely served as an HTML5 native application.

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Tested on MacOS 10.14.4 running zsh 5.6.2 (x86_64-apple-darwin17.7.0).

Encountered the following problems:

1. MacOS's readlink behaves differently from GNU's: https://stackoverflow.com/questions/1055671/how-can-i-get-the-behavior-of-gnus-readlink-f-on-a-mac (easily solvable with conditional alias readlink=greadlink)

2. MacOS often has yarn installed at /usr/local/bin/yarn (because of homebrew), this goes in conflict with link-global.sh (easily solvable: a different SYSTEM_YARN for MacOS)

3. running yarn create:cloud-computer gives semantic error as shown in screenshot (perhaps there is a different behaviour with yarn + zsh on mac vs on GNU; errors seem to be thrown because sh is running instead of zsh; more investigation needed)

Description

This is a #hacktoberfest challenge. Submit 4 PRs with your work and get a hacktoberfest t-shirt!

Currently the cloud computer supports 19 remote applications:

• Blender
• Chrome
• Cloudstorage
• Darktable
• Dispatch
• Evernote
• Filerun
• Gnumeric
• Kicad
• Krita
• Notion
• OnlyOffice Documents
• OnlyOffice Spreadsheets
• OnlyOffice Presentations
• Postman
• Skype
• Slack
• Spotify
• VS Code
• Your application!

Submit a PR with a new application based using an existing Dockerfile as a starting point.

Description

This is a #hacktoberfest challenge. Submit 4 PRs with your work and get a hacktoberfest t-shirt!

Currently the cloud computer only deploys to Google Cloud Platform. By adding support for other cloud providers the cloud computer will become accessible to many more users.

Providers To Support

Pick your preferred cloud provider to add support for:

• AWS
• Azure
• cloudscale.ch
• DigitalOcean
• Linode
• OpenStack
• Packet
• Scaleway
• VMware
• 1&1

Criteria

Packer

Each cloud provider requires a machine image to be pre-built containing the dependencies required by the cloud computer docker stack (e.g. docker, nvidia docker drivers, cached cloud computer docker containers).

Add a new packer build config in infrastructure/packer/providers, for example infrastructure/packer/providers/aws.json.

Terraform

Each cloud provider requires a terraform file for creating the cloud computer's network and compute resources.

Add a new folder in infrastructure/terraform/providers with name of the cloud provider. Create a cloud-computer.tf file under the cloud provider folder, for example infrastructure/terraform/providers/aws/cloud-computer.tf.

Description

Adding support for Electron applications via browserd makes 580+ electron applications runnable on the cloud computer.

Submit a PR with an electron application packaged using browserd using an existing Dockerfile as a starting point.