- Scenic Library Repo
- Scenic Documentation
- Scenic.Sensor - A combo PubSub and Data cache that sits between sensors and scenes
scenic new
-mix scenic.new
task for new Scenic apps
- Scenic as a game dev tool - Game development conversation on ElixirForum
Key,Value | |
dc890d15-9560-4a4c-9b7f-a736ec74ec40,full_access_as_app | |
73a45059-f39c-4baf-9182-4954ac0e55cf,TeamsAppInstallation.ReadWriteSelfForChat.All | |
59a6b24b-4225-4393-8165-ebaec5f55d7a,Channel.ReadBasic.All | |
a25ca244-bc95-4be7-bd58-ca9325bd24b2,AzureContainerRegistryRP | |
7b2ebf90-d836-437f-b90d-7b62722c4456,Schedule.Read.All | |
c7283fbe-34b8-4134-a6b4-771e6a87a497, | |
efe4d732-bfbb-4617-8a77-349a9d67c720,app_impersonation | |
66a874a2-b739-43fa-8e1a-176cd8290cf5,Collection.Read.All | |
9125c627-3755-4ad3-8742-4d6b193c4fc2,filteredhierarchy.read.all |
scenic new
- mix scenic.new
task for new Scenic appskind: Pod | |
apiVersion: v1 | |
metadata: | |
name: banana-app | |
labels: | |
app: banana | |
spec: | |
containers: | |
- name: banana-app | |
image: hashicorp/http-echo |
So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
* Off the top of my head * | |
1. Fork their repo on Github | |
2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
git remote add my-fork git@github...my-fork.git |