aframevr-userland / aframe-cli Goto Github PK

aframe deploy starts, fails regarding ipfs-daemon and finishes. The console emits an URL but it is not working. See the screenshots attached.

@caseyyee: see this section in the latest Docs on master: https://aframe.io/docs/master/components/light.html#adding-real-time-shadows

It seems that any template alias with "-" in the name doesn't work.

Just using --template model works though. Not sure why?

node index.js new my-3dmodel --template model-viewer
11:00:01 - log: Using template "aframevr-userland/aframe-model-viewer-template …
11:00:01 - log: Cloning git repo "git://github.com/aframevr-userland/aframe-model-viewer-template.git" to "/Users/casey/.brunch/skeletons/6ceaa9508869139f31c6a71eec0a73848ad6c483"...
/Users/casey/Developer/aframe-cli/index.js:3
  throw err;
  ^

Error: Git clone error: Error: Command failed: git clone git://github.com/aframevr-userland/aframe-model-viewer-template.git "/Users/casey/.brunch/skeletons/6ceaa9508869139f31c6a71eec0a73848ad6c483"
Cloning into '/Users/casey/.brunch/skeletons/6ceaa9508869139f31c6a71eec0a73848ad6c483'...
fatal: remote error:
  Repository not found.

    at exec.then.error (/Users/casey/Developer/aframe-cli/node_modules/init-skeleton/lib/index.js:67:13)

see https://gist.github.com/cvan/2cbe499be3b433cf931d02a3a50cddaa

just to be more consistent with where we want to head with this (dev environment)

As part of #17, I tried including the component script into it's own js/components/teleport.js.

The bundler ends up concatenating the html itself. Not sure why.

Currently just creating a new project then working out of the project folder ie 'aframe new my-project' then editing files in 'aframe serve my-project'.

After changes I copy the working files back into the '/templates/default-template'.

Is there a better way to be doing this?

see https://gist.github.com/cvan/2cbe499be3b433cf931d02a3a50cddaa

à la https://twitter.com/fifsilva/status/853308454089445376 🍪 🅰️ looks awesome

see https://gist.github.com/cvan/2cbe499be3b433cf931d02a3a50cddaa

• Description
• Usage
• Examples

@cvan I know you had these mocked up somewhere already. We should find a place for this to live.

à la Now's _src

Kind of throws me in a loop when looking for files. Maybe just in the root folder as per conventional web dev.

aframe cli page should parse readme for docs.

• Later we can add support for IPFS, Neocities, now.sh, etc.
• Surge is quite unreliable, so I wouldn't recommend supporting them.
• Heroku requires a backend server, so I'd also not recommend it for static sites right now - that is, until there are A-Frame scene templates with backend code (e.g., for multi-user services and so forth).

there's code for this in these (unmerged) branches:

• https://github.com/cvan/aframe-cli/tree/aframe-new-git
• https://github.com/cvan/aframe-cli/tree/deploy-github-pages

à la http://fi3d.tumblr.com/image/152656473598

(found on http://fi3d.tumblr.com/)

default scene template:

• add sound
• add model
• grid and axis helper

regardless of whether a local Git repo is created during the aframe new call.

for easy sharing of published aframe content.

this is the current list of glob patterns to ignore:

        ignore: [
          '.git/**',
          'node_modules/**',
          'ipfs/**'
        ]

developers should be able to pass patterns as comma-separated glob patterns to ignore directories from being deployed, like so:

aframe deploy --ignore file1.txt, some_directory/**

to launch with Salvas article.

after installing npm install -g aframe-cli and running, i get this:

aframe new test-project
module.js:472
    throw err;
    ^

Error: Cannot find module '../package.json'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/casey/.nvm/versions/node/v7.4.0/lib/node_modules/aframe-cli/index.js:19:13)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)

aframe-cli projects are built using brunch but this is not indicated. When starting from a template but evolving the project, it could be convenient to hack into the build process. Add a link to the Brunch homepage to explicitly highlight the building technology and provide a point of entry for those developers that want to customise the building process.

aframe new my-360 --template 360-tour
cd my-360
aframe serve

multiple tabs open when livereloading.

https://www.npmjs.com/package/aframe-cli

image preview,
also fb meta.

http://brunch.io/docs/getting-started

see https://gist.github.com/cvan/2cbe499be3b433cf931d02a3a50cddaa

https://github.com/caseyyee/aframe-multiuser-boilerplate

Based off the smasher work.

à la https://github.com/brunch/brunch/blob/3c21b7/lib/utils/config.js#L205-L209

Use https://github.com/cvan/fetch-manifest

would be cool to include as dev environment the retain-camera component:
https://github.com/caseyyee/aframe-dev-components/blob/master/src/retain-camera.js

The component basically retains the position of the camera while the page reloads making it easier to work with content.